bug

Ubuntu Bugs in Release Candidate – Hating

There are several posts going around about a bug in the Ubuntu Karmic release candidate. One post details the lack of the 64 bit installer being able to detect multiple sata hard drives.

“The 9.10RC Karmic Koala ubiquity disk partitioning steps (#4, #5 in the installation screens) seem to have regressions when booting the AMD64 ubuntu live desktop CD on systems with multiple disks.

This is a shame of a bug to be exploited by haters. Once Ubuntu is up and running it cannot be compared to Windows. It is much more stable, will run for months without needing to be shutdown. There is no worry of viruses, and spyware, and 99% of applications have a version that will run. The only two applications, that I can think of, that will not run on Linux is iTunes, and Quicken. THERE ARE ALTERNATIVES THOUGH, and always a way to do what you want to do.

The only reason Windows is liked more than Linux is because the majority of humanity is NOT TECH SAVVY. If a problem is encountered in Linux, Google is your friend. There is always a solution! It is worthwhile to find the solution, to get Ubuntu working, because of the benifits.

Virus

1) No more viruses or spyware. There are very few bad things that can happen when using Linux.

2) Stability, and no need to defragment. Your machine will run for months or years without needing to reboot.

One of the only reason to use Windows is for games. Drivers for top end video cards, and the games themselves, are generally only supported on Windows.

Compiz and VNC Fullscreen Bug Workaround

The best and most versatile vnc client for linux is xtightvncviewer. Its easy to install and gives a variety of options. When using it with compiz the fullscreen option, most annoyingly, takes up all the viewports. To clarify compiz take a single workspace and expands it in x and y dimensions. Therefore for viewport 2, the second face of the cube to the right, beings with your desktop resolution +1. My desktop is 1920 x 1080 therefore my viewport 2 starts at 1921. Though not entirely relevant it is important when trying to place different windows automatically on different sides of the cube. While searching for a solution or an alternative to xtightvncviewer I tried many different clients. In the end I didn’t like anything other than xtightvncviewer. Many don’t have x cursors locally, and others dont allow defining the compression type or level. Ultimately I found a ubuntuforums post dealing with placing an xtightvncviewer entirely in a workspace. I see how this is useful using metacity along with the workspace switcher, but very comveniently it is also applicable as a bug workaround! Here is the link to the forum post, but since the availability of internet content is always in question I will make a local link to the perl script, and abbreviate the procedure. http://ubuntuforums.org/showpost.php?p=3465085&postcount=1 First install some files: sudo aptitude install wmctrl xtightvncviewer zenity perl The forum post provides a link to xtightvncpasswd a renamed passwd file that is compiled for a specific kernel, I think 32 bit which is why it didnt work on my machine. There I recommend to simply compile it yourself. Install build essential and your headers if you dont have then installed. sudo apt-get install build-essential linux-headers-$(uname -r) Then the remaining build dependencies: sudo apt-get build-dep xtightvncviewer Download the source code from http://www.tightvnc.com/download.html: Here is a direct link to the source, but the version will eventuall change which is why the main page is linked to above: http://downloads.sourceforge.net/vnc-tight/tightvnc-1.3.10_winsrc.tar.bz2 Unzip it on your desktop. cd to the directory in a terminal. Then compile with: xmkmf make World Copy the passwd file to /usr/local/bin and rename it to xtightvncpasswd so the script will work right. sudo cp ~/Desktio/vnc_unixsrc/vncpasswd/vncpasswd /usr/bin/xtightvncpasswd sudo chmod 755 /usr/bin/xtightvncpasswd Download the perl script that user Felson so awesomly wrote! vnc_ws Copy it to the /usr/local/bin directory: sudo cp ~/Desktopvnc_ws /usr/local/bin sudo chmod 755 /usr/local/bin/vnc_ws Now your probably going to want it to open the vnc fullscreen on a viewport other than your main. You have two options. The compiz plugin Place Windows, which works fine for this type of window, or a manual wmctrl. I describe use of wmctrl in my previous post. http://www.bgevolution.com/blog/compiz-auto-move-a-window-to-another-desktop-viewport/ Simply configure the compiz plugin Place WIndows to move the vnc fullscreen window to viewport 2, or any viewport that you want. My start vnc quicklaunch button looks as such: vnc_ws -h 192.168.0.102 -p 5900 -P password -w 1 -e zlib -o '-x11cursor' The scripts takes a variety of parameters. Use vnc_ws –help for all options. -h is the ip of the host machine. -P is the password to automate the login process; please note that this is not secure at all and if security is an issue only use this script on a local network behind a fiewall or a properly configured router. -w defines the workspace, this should be one because your compiz cube is in workspace 1. You can use multiple workspace(desktops) but this will just make your headspin unnecessarily. -e is the compression type. -o passes options directly the xtightvncviewer. I use the x11cursor option to render the cursor locally for performance purposes. Fire it up, and fill a viewport with a fullscreen vnc connection. I use this script because I want my headless mac as a viewport. Heres a post with a screenie! http://www.bgevolution.com/blog/ubuntu-mac-tiger-windows-xp-and-mythtv-on-the-same-desktop/

Ubuntu Sendmail Boot Bug

There are two bugs that I currently aware of regarding the sendmail boot process. The first and simplest deals with your hostname. In Ubuntu, the default configuration of sendmail and apache required a fully qualified domain name. You can adjust your FQDN manually in the /etc/hostname file. The proper format is: name.domain.com Save the file, and you will not get any errors on an apache or sendmail reboot. Also there is sometimes an issue when sendmail tries to reconfigure its cf file during boot. I don’t experience this issues, but its worth mentioning due to its simple workaround. Just delete the two following files, and sendmail will not re-configure on boot (you will have to do it manually if you change its settings): /etc/network/if-down.d/sendmail /etc/network/if-up.d/sendmail

WordPress MU (Multi-User) Plugin Menu Enable/Disable Bug Workaround

As reported in my previous post, WordPress MU has a bug where if you enable the Plugin menu, then disable it, you will not be able to re-enable it. To re-enable the Plugin menu, go into your PHPMyAdmin interface, open the database for your WordPress MU site, open the wp_sitemeta table. Switch to the browser tab, rather than the structure tab. Locate the menu_items meta key. It should have an empty meta value, based on what I have observed, and what others are saying. Delete this meta key by hitting the red x. Now you will be able to re-enable your Plugins menu. Note that if you re-disable the Plugin menu option, you will have to re-delete the menu_items meta key in order to re-enable it :) A quick and dirty solution to one headache of a simple problem. I expect this bug to be resolved in the next version of WordPress MU.

WordPress MU Plugin Menu Enable/Disable Bug

As of August 25, 2007 there is a bug in WordPress MU where if you turn on the Plugin menu option, and then disable it, you will loose the ability to reactivate it. This bug is currently being discussed at the official WordPress MU forums, and I believe a resolution will present itself soon. http://mu.wordpress.org/forums/topic.php?id=5917&page#post-35846

Clean Install Fedora Bug

If you just installed Fedora Core 6, or Fedora 7, and when you boot the system the GDM (Gnome Display Manager) does not load, and your stuck at the command prompt, I recommend reinstalling the OS. You can try and start the GDM by logging in and typing: sudo service gdm start But most likely the simplest course of action is to do a clean install. It will work eventually, I promise :) Also make especially sure that you have selected the installation of a Desktop Environment, ie. KDE, Gnome, XFCE, ect…..