Archive for March, 2010
You may see this issue if you plug in a removable device (such as a flash drive or external hard drive) and:
- Windows recognizes the device and installs necessary drivers
- Windows reports the device is ready to use
- Windows does NOT show an icon for the device in “My Computer”
- The device works fine in another computer
Assuming that device drivers are not the issue (see #1 above), you may have a situation where Windows is not assigning a drive letter because the previous drive letter is in use by something else (such as a mapped network drive, etc) or not automatically assigned / configured. In this case, you have to manually assign the device an unused drive letter.
- Click Start > Control Panel
- Double-Click Administrative Tools
- Double-Click Computer Management
- On the left pane, expand Storage if not already, and select Disk Management
- On the top pane, under the Volume column, locate the device with no drive letter assigned to it and right-click in the space where the drive letter should appear.
- Select Change Drive Letter & Paths
- Click Add then Assign the following drive letter (select a drive letter) and Ok
Once the device has been assigned a drive letter it should resume normal operation.
Mounting an extra internal hard drive typically requires manual effort by the superuser, but there is a way to configure it to be done (rather easily) at boot time through a handy utility called pysdm.
The first thing you want to do is install pysdm from either synaptic or the command line. The command-line way is:
sudo apt-get install pysdm
Now that pysdm is installed, you’ll find it under System > Administration > Storage Device Manager
Starting it, you’ll see your list of drives on the left pane. Select the drive and partition you want (this assumes you know how to do that already) and click Assistant.
In assistant choose at least The file system is mounted at boot time along with any other options you might want.
Apply and reboot to verify it’s working.
On the computer that will be sharing the desktop, go to System > Preferences > Remote Desktop
If you want others to just see your desktop, but not be able to make changes, enable Allow other users to view your desktop only. If they should be able to change settings (e.g. repair your system if there are problems), enable Allow other users to control your desktop as well.
If someone connects to your desktop and you want to be prompted to block or allow that connection, enable Ask you for confirmation. This makes sense only if someone is actually sitting in front of the system. If you want to connect to your office desktop or any other system that only you have access to, then don’t enable this option
However, with Ask you for confirmation off, what you certainly want to do is set a password for your remote desktop (without a password anyone who happens to find out your system’s address – e.g. by scanning the network – can access your desktop)
If you’re behind a router or firewall, you may need to allow or forward port 5900 to that computer.
Sourced from http://www.howtoforge.com/configure-remote-access-to-your-ubuntu-desktop March 28th 2010
Originally retrieved from this thread March 27th 2010.
Gnome stores your “recent documents” in a file called
.recently-used.xbel. To disable the menu, we simply delete the file and then create a directory with the same name, effectively breaking Gnome’s ability to store anything in the file.
The fix is performed by executing the following commands at a terminal:
rm ~/.recently-used.xbel mkdir ~/.recently-used.xbel
Then go to Places > Recent Documents and select Clear Recent Documents.
The menu item should now grey out.
Some Seagate Barracuda drives have been found to have buggy firmware which causes the drve to hang or become unresponsive after a power-cycle event (such as the computer going to sleep or standby) and the drive need a full power-cycle (power off then back on) event to become operable again.
Please note that you may not experience this issue when running the drive with the latest drivers in Windows, but may experience it in Linux-based OSes, such as Ubuntu Linux. This is because the issue is covered up by Windows drivers. If you experience the issue in Linux, then you likely have a drive with faulty firmware. Note that this is supplied from Seagate to Dell, so the fault lies in the firmware developed by Seagate, not by Dell.
Users of Ubuntu and Firefox may notice after installing some applications that fonts no longer appear correctly in Firefox (though they may appear correctly in some Java, etc, apps). Such issues include:
- No bold
- No other styles (italics, etc)
- Wrong font / size
This seems to happen when the packages ttf-symbol-replacement and ttf-tahoma-replacement are installed. Simply uninstalling these two packages should resolve the issue.
CrashPlan on Linux depends on the inotify kernel module to know when files update in real-time.
Inotify was merged into the 2.6.13 Linux kernel, so if you’re running a kernel equal to or newer than this, it’s already installed. If not, you’ll have to install it yourself. If inotify is installed, you may need to increase the number of watches that can be created.
The inotify module is govered by a property called max_user_watches. If you attempt to exceed the max number you’ll get the following error in the engine_error.log (but the process lives on).
inotify_add_watch: No space left on device
Any file not covered by a watch does not have real-time backup protection.
The default on my Ubuntu 11.04 box is 524288, which seems plenty sufficient for me. I have not experienced any issues, but if you find that you are, you may want to increase the watch value.
Updating the Watch Value
You can temporarily update the value with:
echo 1048576 > /proc/sys/fs/inotify/max_user_watches
You can update the value permanently by putting the following value in /etc/sysctl.conf and restarting:
For more information, see CrashPlan’s Forums.
Fedora (and Ubuntu) Linux users looking for more screensavers should install the package xscreensaver-gl-extra via their favorite package manager:
Use yumex, or via command line:
sudo yum install xscreensaver-gl-extra
Use Synaptic, or via command line:
sudo apt-get install xscreensaver-gl-extra
Here’s the package description:
This package contains the rest of the 3D (OpenGL) screen saver
modules from the xscreensaver collection. This package is used
by both xscreensaver and gnome-screensaver.
This is the set of GL screensavers not shipped by default with
xscreensaver-gl: antinspect, gleidescope, glknots, atunnel, blinkbox,
bubble3d, circuit, cubestorm, glsnake, jigglypuff, lavalite, lockward,
mirrorblog, moebius, boebiusgears, molecule, morph3d, pipes, polyhedra,
polytopes, pulsar, queens, sierpinski3d, spheremonics, stonerview,
superquadrics, topblock, voronoi endgame, engine, flipflop, flipscreen3d,
flurry, flyingtoasters, gears, gflux, antmaze, atlantis, blocktube, boing,
bouncingcow, boxed, cage, carousel, crackberg, cube21, cubenetic, dangerball,
extrusion, fliptext, glforestfire, glhanoi, glplanet, juggler3d, klein, lament,
menger, noof, pinion, providence, rubik, sballs, sproingies, staris, starwars,
You can quickly and easily remove Windows and BlackBerry thumbnail index files using a few simple terminal commands.
find /path/to/directory -name "Thumbs.db" -delete find /path/to/directory -name "desktop.ini" -delete find /path/to/directory -name "AlbumArt*" -delete find /path/to/directory -name "BBThumbs.dat" -delete
You can expand on this to remove any file name or mask.
Reposted from the original bug report at launchpad (Retrieved March 15th 2010)
Once in a while, a process called “ld-linux.so.2” starts consuming all my system resources, with CPU usage between 90-100%, my 2GB main memory AND my complete swap partition used up completely, making the system unresponsive to a degree that even single keystrokes need up to a minute to get interpreted by the system.
A forum post indicates that Adobe Reader 8 is the source of the problem. It claims that installing the “lsb” package will solve the problem. I can now confirm this does not fix the problem. Instead, the acroread process itself will now turn out to be the resource hog (no ld-linux.so.2 process is listed anymore by ‘top’ though).
Two known workarounds:
1) uninstall package acroread
2) when slowdown starts, either
killall -KILL ld-linux.so.2 (package lsb not installed) or
killall -KILL acroread (package lsb installed).