[LAST CHANGE 3/21/10 @ 4:16 AM CST: Added xsplash & WINE menu entries.]
This thread will discuss the fixes for some common Ubuntu annoyances. Right now, it doesn't have much since I am the only source. As a Ubuntu user, sometimes finding a few of the lesser-known fixes for those common annoyances, idiosyncrasies, and 'features' is really hard. The purpose of this thread is to hopefully archive these obscure fixes and allow LQ users and the Google bots to access what will hopefully be a comprehensive list of problems and the answers to them. Please feel free to post any fix you have found and I will add them to this 'ongoing' thread. When you post your fix, make sure you tell us what version of Ubuntu you have. I will give all credit to you, unless you note otherwise. If a particular fix does not work for you, please post it and I will look into it. As you can see, I will also post the last change I made to the thread at the top, so people will know if a fix has been put in since the last time they checked. Any feedback or suggestions are welcome. As this thread matures, the need for this lengthy paragraph will subside and I will make it much shorter. Thanks, on to the fixes!

------------------------------------------------------------------------


Table of Contents

1. Root application themes are the default instead of the user one
2. Root gnome-terminal does not show any customizations
3. Enable root user
4. GRUB2 resources, HOW-TO links, fall back to GRUB legacy
5. Customize the GDM login
6. Unlock the default keyring automatically for Network-Manager, for all users
7. Customize the xsplash (brown one with loading bar)
8. Remove orphaned WINE GNOME menu entries (this will also allow you to regenerate them when you reinstall WINE)

------------------------------------------------------------------------

1.) Root application themes are the default instead of the user one.

- {Tested on Karmic} By: leopard

The problem: When you run any application as the root user, it uses the default theme instead of the one you have set.

The fix: Open a Terminal. Applications => Accessories => Terminal. Type in:-
press [ENTER], enter your password, then press [ENTER] once again. Your theme will now stay consistent when running as root.

2.) Root gnome-terminal does not show any customizations.

- {Tested on Karmic} By: leopard

The problem: The root gnome-terminal does not show any customizations that the user put on it, instead it shows the ugly default theme.

The fix: Open a Terminal, and type:-
to bring up a root Terminal. Then edit the default profile to your liking. (Settings changed here do not affect the regular user terminal)

3.) Enable root user

- {Tested on Karmic} By: leopard

The problem: By default Ubuntu does not have the root user and login enabled. (NOTE: Only do this if you 'know what you are doing' and know what you are trying to achieve. If you are new to Ubuntu, please consult this link.) This can decrease overall security if not used correctly.

The fix: Open a Terminal and make a root password:-
You should now be able to log in as root with the password you assigned to it.

4.) GRUB2 resources, HOW-TO links, fall back to GRUB legacy:

This guide has everything:
http://ubuntuforums.org/showthread.php?t=1195275
(Fall back to legacy GRUB is #12)

Official GRUB2 wiki:
http://grub.enbug.org/

Customize the splash and font:
http://www.webupd8.org/2009/11/custo...ntu-linux.html

Tips & tricks from Canonical Ltd.:
https://help.ubuntu.com/community/Grub2

Some extra configuration documentation:
http://linuxers.org/howto/how-config...ub2-ubuntu-910

5.) Customize the GDM login screen

- {Tested on Karmic} By: leopard

The problem: The developers forgot that we like to customize or PC.

The fix: Open a Terminal. Applications => Accessories => Terminal. Type in:-
press [ENTER], type in your password, then press [ENTER] once again. You can edit it exactly like you would normally with your desktop theme, except this is just for the GDM login.

Also, someone made a script, see here:-
http://ubuntuforums.org/showthread.php?t=1358026

6.) Unlock the default keyring automatically for Network-Manager, for all users

- {Tested on Karmic} By: leopard

The problem: That annoying default keyring always asks for your password on every log-in just to use your network.

The fix: Scroll up to the network-manager tray icon, right-click it, and select 'Edit Connections...'. Browse to the desired connection in which to unlock, select it, and press Edit. Enter your password, and press "Allow Once" if a keyring dialog pops up. In the lower left, check the box "Available to all users". (NOTE: This will make it so none of the users on your PC have to enter a password to use the network.) Restart, and enjoy one less annoyance!

7.) Customize the xsplash (brown one with loading bar)

- {Tested on Karmic} By: leopard; EricTRA gave me some links

The problem: You want to change the xsplash boot splash theme.

The fix: The xsplash images are located at /usr/share/images/xsplash. Make a backup of these images somewhere on your drive before deleting the ones in /usr/share/images/xsplash. This step is important. Then, get your new xsplash theme/image (http://gnome-look.org), and place the image(s) in /usr/share/images/xsplash. That's it with the theme, but follow the next step to ensure it works properly. Now test your new xsplash before you reboot by opening a Terminal (Applications => Accessories => Terminal). Type into the Terminal:-
, press [ENTER], type in your password, and press [ENTER] once more. (Use [ESC] to quit the xsplash) If you're new xsplash image shows up correctly, you may now feel safe to reboot and experience your new theme.

Some links (by EricTRA):
http://www.howtogeek.com/howto/7939/...n-ubuntu-9.10/
http://www.makeuseof.com/tag/customi...en-logo-linux/
http://www.webupd8.org/2010/01/xspla...ts-easier.html
http://elwoodicious.com/2009/10/29/i...slacker-style/


8.) Remove orphaned WINE GNOME menu entries (this will also allow you to regenerate them when you reinstall WINE)

The problem: I uninstalled WINE and menu entries are left there, or I want to reinstall WINE and the menu never shows up.

The fix: Notice: make sure the entered commands are correct before proceeding. there is danger for loss of data! Proceed with caution.
The following links will provide the information needed.
http://forums.fedoraforum.org/showthread.php?t=151425 {post #4}
http://guide.ubuntuforums.org/showthread.php?t=1255193 {post #7}
http://forum.winehq.org/viewtopic.ph...0bf1fb4a15516f
http://ubuntuforums.org/showthread.php?t=815333 {post #7}

-----------------------------------------------------------------------

That's all I could think of for now. If you have a fix, please post it, and I will, as fast as I can, add it to this thread. Thanks and hope this idea flourishes!

Linking files between accounts is a bad thing, let alone linking between unprivileged users and root. You shouldn't need to run X11/Xorg as root anyway so the point is moot.


While breaking things yourself on your own machine is your own problem, offering such a "solution", and without warning, as if it's the ultimate solution may eventually break things for others in ways they can not fathom. There's a reason they locked up the root account and while you may not like it you have the freedom to choose any other distribution if its a show stopper for you. For the most authoritative explanation I know see http://ubuntuforums.org/showthread.php?t=716201.

A lot of users 'don't like it' and this is a method of changing that effectively.

I can insert a disclaimer if you like; but notice they say tested. By that I mean I am using it now and the system works normally, and the fix itself is effective. My system runs like it did out of the box. These are also fixes that I have (mostly through relentless searching, for hours on end sometimes) found, that worked for the person who posted them up and the person who originally asked the question.

Would you like a disclaimer? I can do that if it becomes a problem. I just want to convey and further document the fixes that I found and that worked for me

Also, we could change the thread title to "Ubuntu: Possible solutions to those common Ubuntu annoyances"

And you didn't state a fact why that link is 'wrong.'

Sorry unSpawn if anything I just said offends you in any way. If either the disclaimer or thread title needs changing, I will edit it to your specification.

I also felt, in my opinion, that your post came across as rude. Sorry if I misunderstood it.

If it works like it's supposed to (which they do), and they don't ruin, break, or bring about a new problem, what's wrong? Whatever happened to "whatever floats your boat?" These are fixes people want and look for. If there is a problem with the fix, test it or prove it, let me know, and I'll change it! And lastly, I will note if there is a known side-effect to the fix.

Thanks for your reply, sorry if I come across as rude, and I truly hope you have a nice day!

Added Network-Manager keyring automatic unlock on log-in for all users entry.

Added unSpawn's rationale and link as a note to "enable root user" fix.

Moved to Ubuntu as it would be more relevant to there.

A lot of users don't like anything that has to do with security, when it presents even the most minor of inconveniences to them, so you do have to be careful with the warnings.

@unSpawn
Up to a point, Lord Copper. If you break things on your own machine, where will you go for help/support? At the very least, if it is to a well-known linuxquestions site, you should always remember to mention that you have done this, as it may reduce the frustration for others who try to help you towards a solution, and you should, of course, bear in mind that it may reduce your chances of finding someone who has expertise on your exact problem.


So, no pen testing, then. I'm afraid had you not clarified, I would have probably read that as thoroughly tested, which would have been something else.

I'm sorry to have sounded negative, particularly with a well-intentioned attempt to do the right thing and help users at the without increasing the number of 'junk' questions, but edging something like this with appropriate warnings is actually quite necessary.

Added some information on orphaned WINE menu entries, and an xsplash theme howto. {Links were by EricTRA).

re tip No 1

Hi

It would seem to me that any application being run as root SHOULD look different. To have it looking as if it was in user mode could be very misleading and create a possible weakening of the safety aspect of the whole notion of root v user.

Lou