Feeds:
Posts
Comments

Ubuntu has moved on to “Unity“, and Gnome has evolved to version 3‘s “Gnome Shell“, but many people (like myself) still prefer to use the old “Classic” desktop – be it the old Gnome 2 version, or the “Fallback Mode” of Gnome 3 (users of 11.10 upwards have no choice but to use the Gnome 3 version).

While the 2 versions of the “Classic” interface do have some differences – no “System” menu in Gnome 3 (read this if this is your only concern), and having to hold Alt while right-clicking it to access options – both have panels that are much more customisable (and infinitely more useful) than what “Unity” and “Gnome Shell” currently offer.

But things can go awry, like after doing some tweaking, or installing a program, or having to do a hard reboot, and you can find your panel altered (particularly minus the menus), or even completely missing. So we’ll look at a few different scenarios, and how to rectify them, including how to force Gnome to reset your menus back to their defaults (which is probably the quickest and easiest method). Also, because I’ve seen a lot of newbies in forums say “My Applications menu is missing!” when they should be saying “My top panel has totally vanished!”, we’ll look at how to get your panel back as well.

Finally, because some will need to take a harder approach (or just prefer an easier one), we’ll look at how to totally reset your panels back to their defaults. This is by far the most drastic measure, but it’s quick and easy, and for most people there are no customisations to worry about losing. Besides, if your panel has totally died or vanished, and nothing else you’ve tried has worked, then it’s the only option left.

Try A Quick Panel Restart:

First off, it might be enough to simply refresh the panel by forcing it to close then re-open, which can be done by a reboot, or logging out, or simply entering the following command into the terminal or via Alt+F2:

killall gnome-panel

It pays to do that first, in case that’s all that’s really needed, but chances are you’ve already tried logging out or rebooting, so check out the following tips.

Restore Missing Menus to Panel:

If just your main menu (the “Applications” and “Places” menus, and the “System” menu in Gnome 2) is missing, then perhaps all you need to do is add the menu back to your panel. Right-click an empty area of your panel (holding Alt in Gnome 3) and choose “Add to Panel…“, then scroll down till you find “Menu Bar” (ignore “Main Menu“, as that is a small icon version), and drag it to the left area of your panel.

If it’s conceivable that you perhaps accidentally right-clicked the menu and hit “Remove From Panel“, then it might pay to do this, especially if you have panel customisations you don’t want to lose.

Force Reset of Main Menus:

If you can’t add the menus back to your panel, for example you can’t invoke ”Add to Panel…” with a right-click, it’s time to reset the menus to their defaults, which is done by deleting some configuration files. Actually, technically you’re not deleting anything, as the 2 files in question are simply renamed with .bak extensions [so they're still there if you really need them later], forcing Gnome to recreate those files with default values.

To force Gnome to rewrite its panel menus with default values, enter the following command into a terminal:

mv ~/.config/menus/applications.menu ~/.config/menus/applications.menu.bak && mv ~/.config/menus/settings.menu ~/.config/menus/settings.menu.bak

(That should work with either Gnome 2 or 3, though the settings menu part of it probably won’t do anything in Gnome 3).

All you have to do now is log out, then once you log back in again, your panel should be back with all its menus. Or you can simply enter killall gnome-panel into the terminal and it should successfully refresh your panels without having to log out.

Make a New Top Panel if Missing:

If your panel is absent, you could have even accidentally deleted it yourself, if you unwittingly right-clicked the panel and chose “Delete This Panel” (in Gnome 2 – in Gnome 3 that is harder to do, since you need to be holding Alt while right-clicking the panel). But don’t immediately blame yourself, as all sorts of mishaps can result in a missing panel.

Whatever the case, you should be able to recreate your top panel simply by right-clicking the bottom panel (while holding Alt in Gnome 3) and choosing “New Panel“. You’d then move it to the top, then right-click it (holding Alt in Gnome 3) and choose “Add to Panel…” to add back all the various bits and pieces you had before (the “default” panel is actually a blank panel with a bunch of plugins added).

Obviously, this would be the most time-consuming method, but if you plan to customise your panel anyway, you may as well start from scratch. However, the easiest method would be to totally reset your panels, so keep reading.

Force A Complete Panel Reset:

When all else fails, it’s time to force Gnome to completely reset your panels, which is done by deleting the configuration files. That might sound drastic, and in reality this really is the last resort, but if your panel is totally messed up, chances are your old settings are useless anyway, or rather that having to stick some launchers back on a clean panel will be a welcome alternative to having no panel, or one that is buggy, or missing the “Applications” menu or whatever.

To force Gnome to recreate its panels with default values, enter the following commands into a terminal:

gconftool --recursive-unset /apps/panel (This wipes the panel’s settings)

rm -rf ~/.gconf/apps/panel (This deletes the panel’s folders and files)

killall gnome-panel (This forces the panel to close and restart)

Your panel should now be back with all its menus (but of course minus any customisations). If for some reason they don’t appear immediately, a reboot should fix it.

Alternative Commands for Panel Reset:

ΔΔΔ Some guides have gconftool-2 --shutdown as the first command (this shuts down the current user’s gconfd), though gconftool --recursive-unset /apps/panel should work perfectly fine without it. However, if you aren’t having success, then run it first.

ΔΔΔ If you’re running the commands via the Alt+F2 Run Application box, chances are it won’t like the tilde (~) in the second command, so use rm -rf $HOME/.gconf/apps/panel instead.

ΔΔΔ Instead of killall gnome-panel, you can use pkill gnome-panel (which is basically the same thing), or nohup gnome-panel --replace &, or nohup gnome-panel --replace </dev/null &>/dev/null & (note that nohup specifies the command not halt when the terminal is closed, so is not needed if using Alt+F2).

ΔΔΔ If you’d rather make a backup of the panel’s files before deleting them, run mv ~/.gconf/apps/panel ~/Settings/PanelBackup (note the second path can be whatever you want; in this case, it’s a folder called PanelBackup inside a Settings folder within my home folder I have for storing various config files and settings backup). It actually moves the whole folder to a new location, which is basically the same as deleting it, so you shouldn’t need to run the second command (since there is nothing left there to delete, anyway).

If you’ve attached an external hard drive to your system, then decided to use your partitioner to format it to EXT4 for greater efficiency (or just to match your Ubuntu system), you may have been shocked to find that your empty drive seemed to be missing a few gigabytes when mounted afterwards. And this has nothing to do with the good old binary (base-8) vs decimal (base-10) situation which would see your “750Gb” drive be more like 700Gb (in Windows and earlier versions of Ubuntu – now Mac OS X and Ubuntu have followed hardware manufacturers and use decimal, so that’s more like 738Gb).

This is because Ubuntu (and other Linux distributions) reserve typically around 5% of the space for the root user and system services, so should you run out of hard drive space, the administrator can still log in, and system services continue to run.

However, this is only really needed for your Ubuntu partition, so if you have an external EXT4 drive, or have an EXT4 partition on your internal drive (other than the one your system is on), you are needlessly wasting space (40Gb of the drive in the example). But you can free up that disk space quite easily, without having to re-partition the drive or anything. All it takes is a couple of commands pasted into the terminal.

In the following example, an external hard-drive will have the reserve set to 0 (zero), since this is what most people will need this for. First, we have to determine the device name, as using its mounted name – /media/700Gb Ext4 – won’t suffice. To do so, enter the following into the terminal:

mount|grep ^'/dev'

Look for the line containing your device:

/dev/sdc1 on /media/700Gb Ext4 type ext4 (rw,nosuid,nodev,uhelper=udisks)

… and you can see what it is named (/dev/sdc1 in this case). To free up reserved space, enter the following (replacing /dev/sdc1 with whatever the appropriate device name is, if need be – just make sure you don’t do it to your main drive!):

sudo tune2fs -m 0 /dev/sdc1

You should then be presented with the following message:

Setting reserved blocks percentage to 0% (0 blocks)

To confirm all has gone well, you can right-click an empty area of the folder window for the device and choose Properties, then compare the free space from before and after, or run the following command (once again replacing the device name with the correct one in your case):

sudo tune2fs -l /dev/sdc1 | grep 'Reserved block count'

You should be greeted with the following:

Reserved block count:     0

That’s it – you now have all of your drive to use.

ΘΘΘΘΘΘΘΘΘΘΘΘΘΘΘΘΘΘΘΘΘΘΘΘΘΘΘΘΘ

Note: if you receive the following error message:

tune2fs: Bad magic number in super-block while trying to open /dev/sdb1
Couldn’t find valid filesystem superblock.

… then the filesystem likely isn’t EXT4 – chances are the drive is actually formatted as NTFS or FAT for use on Windows systems (which would be the case if you’ve bought an external drive, and never did anything other than copy files to it). You would have needed to partition/format the drive to EXT4, so if you didn’t, then you actually don’t need this guide.

If you find yourself trying to figure out which package contains a certain command, or any other file for that matter, apt-file is a command that will make this easy. It probably won’t be installed by default, so do so with this command:

sudo apt-get install apt-file

You will then be presented with the message:

The system-wide cache is empty. You may want to run ‘apt-file update’ as root to update the cache. You can also run ‘apt-file update’ as  normal user to use a cache in the user’s home directory.

It’s probably best to run the former option (that is, as superuser), so enter the following:

sudo apt-file update

Let it update the cache, then you can search for the command or package or file. Simply use apt-file search followed by whatever it is you’re looking for. For example, we’ll search for the command ccsm, which is what runs the Compiz-Config Settings Manager, as there is no actual package of that name:

apt-file search ccsm

You might find the list presented is quite long, so it may pay to set your terminal to unlimited scrolling beforehand. In the case of the example, the line we’re looking for:

compizconfig-settings-manager: /usr/bin/ccsm

is not visible, since it is right near the top, which is beyond scrolling. If this happens to you, edit your terminal settings and run the command again.

Generally speaking, if it’s a command/program, then the line that has /usr/bin/ followed by the command (like ccsm) will be the correct one. The actual package that contains it will be listed at the beginning, in this case being compizconfig-settings-manager.

Remember, this can work with other types of files too, so if you’re looking for a specific config file or icon or whatever, just specify that at the end of the command. Eg:

apt-file search ccsm.desktop

Hopefully this is all you need to find that elusive file, or the package that installs a program you’re after.

At times when using the terminal, the output from a command can be so long, you simply can’t scroll to the beginning, as it is no longer in view. But you can actually set the terminal to display as many lines as you like, or even set it to unlimited scrolling.

In the terminal, go to Edit > Profile Preferences, and in the Scrolling tab you will see there is a default amount of lines to be displayed (probably something like 512). If you have an older computer and are worried about memory, you can up the amount to 2000 or thereabouts, as that should suffice, otherwise the best option is to place no limit on the amount of lines displayed. Under that, you will see “Unlimited“, so check that, and from the next command onwards you won’t have that limitation any more.

Various terminals available might differ as to where to change that setting (like a Settings menu, or Edit > Preferences or Tools > Settings), but they all should have it, and you should find it easy enough.

If you’ve upgraded your Ubuntu system to 11.10, or have a fresh install, you might find that when you right-click a USB drive and choose “Safely Remove Drive” in the left pane in Nautilus, the system hangs. This appears to affect some users of the Linux kernel 3.0.0-12, which at this early stage would be what most users have, so if this applies to you, it should be easy enough to fix.

Go to http://people.canonical.com/~ogasawara/lp844957/ and into the folder for your architecture (i386 or amd64). Install the 3 .debs located therein (I did so with GDebi, but should be the same in Ubuntu Software Centre, just slower), and reboot. You should now be able to successfully remove the drive without issue the next time you connect it.

NOTE: What you’re actually doing here is replacing the 3 main kernel packages, but for me and a bunch of others affected, there were no issues, with kernel 3.0.0-13 replacing the old one in GRUB, booting into Ubuntu just fine, and resolving the freezing issue when trying to remove USB drives.

Do not use this if your kernel is a later version (i.e. higher than 3.0.0-13). It probably wouldn’t kill your system, but reverting to an earlier kernel is extreme measures, so try find a more current and applicable solution (this fix appeared within days, so it does pay to spend a few minutes looking around the web, especially the Ubuntu Forums).

If you’re new to Ubuntu using 11.10 upwards, you might be scratching your head when you see people mention they’re using Gnome Shell instead of Unity, or even the “Classic Desktop“. Or if you’ve been using Ubuntu but decided to do a fresh install, you’ll find there is not only no “Ubuntu Classic” option at login, but no Gnome at all.

This is because the decision was made to drop Gnome as it moved from the familiar 2.x to Gnome 3, since Ubuntu and Unity are built on it anyway. The logic is that should people need a less resource-hungry environment  for slower computers, they can log into Unity 2D instead. But while Unity is gaining fans, and most certainly will gain many more as development continues and we see a flood of plugins and customisation apps, some of us want to play with the new and shiny Gnome Shell, or just to get our old Gnome Classic desktop back.

Now, it’s actually easy to get either or both, but while I’ve seen in forums that installing Gnome Shell will also install the legacy “Classic” desktop, this isn’t true (though it makes sense people might assume that). That’s because while the meta-package gnome is installed, gnome-shell isn’t part of it, but a separate package. Likewise the “Classic” desktop doesn’t come in either gnome or gnome shell, but as exists as the package gnome-session-fallback (which also installs a 2D version).

So, you can pick either, or have both, and it’s as simple as pasting a command or two in the terminal. If planning to have both, you may as well install Gnome Shell first, though it shouldn’t really matter.

To install Gnome Shell: sudo apt-get install gnome-shell

To install Gnome Classic: sudo apt-get install gnome-session-fallback

Once installed, you should be able to just log out and log back in to one of your new desktops, but if not, then do a reboot. Then you can log into Gnome Shell at the login screen by choosing “GNOME“, or the more familiar legacy desktop by choosing “GNOME Classic” (or “GNOME Classic (No Effects)” for less powerful computers or graphics card issues).

If you can’t find where to log into other environments, it’s always a hidden menu you need to access, previously by the word Options at the bottom of the screen, but in 11.10 is a gear icon near the user name; in following versions, that will no doubt change, but just look for something to click on and you’ll find it. Obviously, if you’ve set your login option to be automatic, meaning you never see the login screen but end up straight at the desktop, then you’ll need to change that in order to be able to change between the different window managers.

±±±±±±±±±±±±±±±±±±±±±±±±±±±±±

Related Tip: How to Log Into Ubuntu Classic Desktop or Gnome Shell Instead of Unity

If you’ve upgraded to Ubuntu 11.10, you may have noticed your movie files not looking as they should in the default Movie Player (Totem), and probably others like SMPlayer and MPlayer. For me, the clips actually looked fine first off, but only in Totem, as SMPlayer kept crashing. Then, after getting some updates, Totem started displaying the colours all mixed up (as did SMPlayer, which wasn’t crashing any more). I tested GNOME MPlayer, and that was fine, but all my other players were affected.

From the looks of comments I’ve seen around, updating/installing Medibuntu is a likely suspect, but whatever the cause, it should actually be quite easy to fix. Simply go to Edit > Preferences > Display in Totem, and adjust the Hue from the default 50% mark all the way up to 100%. If yours is all the way down at 0%, as some have reported, then you definitely need to do the same. You may need to do this with each player, but in my case changing the setting in Totem immediately rectified the problem in SMPlayer. If it doesn’t for you, however, then you know how to fix this easily.

Lastly, don’t be surprised if later on you go to play a vid and your colours are all mucked up again. This time, you’ll probably find the Hue is still at 100%, so you’ll need to drop it back to the default of 50%. It might be a bit of a hassle, but this should be fixed up at the development end soon enough, and at least it only takes a few seconds to get your movies looking as they should.

If you upgraded your Ubuntu system to 11.10 and are in the Classic desktop, you’d be wondering where a whole bunch of useful settings launchers got to. If you avoided Unity in 11.04 in favour of your old familiar Gnome desktop (2.x), you would have noticed the new Gnome Shell (3.2) is quite different, and that the System menu in the top panel is no longer there. You can access System Settings by clicking your name in the top-right, but many useful apps are missing.

But those launchers that used to reside in Preferences and Administration still exist (at least most of them), but you can be forgiven if you didn’t see them in your Applications menu. Rather than do the obvious thing and stick them in System Tools, or even Accessories, they now exist in Other.

If you can’t see that sub-menu, right-click Applications, choose Edit Menus, and unhide Other.

Are you looking for a missing Applications menu? This tip is for those with a working panel who want to find the System menu after upgrading their Classic desktop to Gnome 3. If something is amiss with your panel, you should check out this article on how to repair your Classic panel.

Older Posts »

Follow

Get every new post delivered to your Inbox.

Join 69 other followers