TideLog Archive for the “Software Bugs” Category

Recently, using ReactOS Build Environment, I started to get weird errors when trying to update my ROS source. It would say weird things like, “RosBE is outdated. Installed version: 2.1.3 Recent version: .” and also upon running the ssvn update command, I’d get, “The selected branch does not exist or the Internet Connection is down.

It appears that the servers moved to HTTPS, and there’s a bug in the batch files that control the wget commands. Kana suggested to change all the wget command lines in the sSVN.cmd file, adding “–no-check-certificate” to the ends, this fixes the problem!

 

Comments No Comments »

A big bug in the Linux version of Pinta has stopped me from using it as my Photoshop replacement. Here’s my situation: I have an image of one of our Superwoman models, for example, that is quite large, but Superwoman herself is quite tiny, in the middle of the background. I select the whole image, and copy it to the clipboard as-is. I don’t want to use the select or crop tool. I create a new canvas that is smaller than the source image in either height or width, and then paste in my image to the new canvas, so I can move it around and position it just right without having to guess using the select tool on the original.

Make sense? Hopefully! Anyhow, Pinta in its default state, SQUASHES the image to fit the canvas, if you tell it not to resize the canvas, and it looks completely wrong, it literally squashes the image from top down, you know what that looks like without a screenshot, right? I’ve fixed it in my own sourcecode copy and Pinta now behaves as I want it to. I’m not sure the devs would want my changes, but I’ll ask anyhow.

1. Grab a copy of the source, by whatever means by using Terminal (install Git first using “sudo apt-get install git”).

2. Then clone the repo with: “git clone git://github.com/PintaProject/Pinta.git”.

3. Now your source tree is ready, it will be in your Home folder under a folder called ‘pinta’. Install MonoDevelop, and open the Pinta.sln solution file using it.

4. Once open, find the Pinta.Core/Classes/Document.cs file, and after line 806, find:

            // If the pasted image would fall off bottom- or right-
// side of image, adjust paste position
x = Math.Max (0, Math.Min (x, canvas_size.Width – cbImage.Width));
y = Math.Max (0, Math.Min (y, canvas_size.Height – cbImage.Height));

Simply change it so it looks like this:

             // Modified by Tidosho. Image would be stretched/squashed if canvas was smaller and user chooses not to resize it.
//
// If the pasted image would fall off bottom- or right-
// side of image, adjust paste position
//x = Math.Max (0, Math.Min (x, canvas_size.Width – cbImage.Width));
//y = Math.Max (0, Math.Min (y, canvas_size.Height – cbImage.Height));

It’s a bit of a dirty hack, as it simply comments the procedure out, but it works. A possible fulltime modification could be a controllable scale type operation like in Photoshop where you control the scale using handles round the image, but I don’t think Pinta has a scale API.

UPDATE: It isn’t as serious as I first thought, but still annoying. The reason the image is squashed when pasted is because Pinta uses squashed thumbnails for use in the open documents list, and the History. As soon as you drag the layer pasted in, it corrects itself, but then you have to drag it back into position.

 

Comments No Comments »

I’ve been using a heavily customized version of Mandigo as TideLog’s flagship theme for a while, and it’s been perfect, bar a slight layout issue with the footer. However, I upgraded to WordPress 3.0 a while back, but when attempting to block a new page from showing in the navigation bar via the theme’s Theme Options screen I receive an error complaining about permissions. I had to check to see if I had modified anything recently that could have caused these permissions but was unable to come up with anything. I did install a plugin that allowed me to change the default username from admin, but that wasn’t the cause.

Turns out in the changelog that I keep for Kana and myself in the theme itself, the item that made the most sense was the upgrades from WordPress 2.X to WordPress 3.X. Below I describe the error in more detail followed by how to resolve the issue as it’ll likely affect others. Here’s what the error looks like:

you-do-not-have-sufficient-permissions-to-access-this-page

After visiting the internal WP site that Rikku uses for Matsuki Transport, which is still running WordPress 2.x and has the Mandigo theme installed, I noticed the difference was in the URL used to access the Theme Options page. The URL of the site running WP 2.X was “/wp-admin/themes.php?page=Theme%20Options” but in the updated WordPress 3.X the URL was attempting to access “/wp-admin/themes.php?page=ThemeOptions”. Since I knew that I had not upgraded Mandigo the problem must be with the WordPress upgrade as thought previously but instead of modifying WP it made more sense to update Mandigo to resolve the issue as noted below by modifying the theme_options.php file located at the below path.

Mandigo theme_options.php Location:

/wp-root/wp-content/themes/mandigo/backend/theme_options.php

My code snip below shows the original section that we will change in the second code snip below.

Original theme_options.php add_theme_page PHP Function:

// the functions that load the theme options page
        function add_mandigo_options_page() {
                global $dirs;
                add_theme_page(
                        'Theme Options',
                        '<img src="'. $dirs['www']['backend'] .'images/attention_catcher.png" alt="" /> Theme Options',
                        'edit_themes',
                        'Theme Options',
                        'mandigo_options_page'
                );

        }

Updated theme_options.php add_mandigo_options_page PHP Function:

// the functions that load the theme options page
        function add_mandigo_options_page() {
                global $dirs;
                add_theme_page(
                        'ThemeOptions',
                        '<img src="'. $dirs['www']['backend'] .'images/attention_catcher.png" alt="" /> ThemeOptions',
                        'edit_themes',
                        'ThemeOptions',
                        'mandigo_options_page'
                );

        }

Once you replace the original snip of code with my updated one, save the file, refresh your blog, the issue should be gone! 🙂

Comments 2 Comments »

As it is when shipped retail, this drive is terrible. The drive constantly tries to park its heads, lagging the system, even during copy and move operations. With it being a top end 7200RPM drive, this is unacceptable, especially if like my Clevo, it is installed in a gaming machine. It is the power saving “features” of the firmware that cause it. The drive also exhibits “beeping” symptoms where the voice coils of the arm recieve a high current to wake it up and seek track, the high current effectively turns the coil into a speaker, and it makes a beeping sound. The drive constantly seems to miss beats because of the parking issue, causing the arm to miss and have to be shocked back into place by the controller.

Using tools like HDDScan to disable the APM (Advanced Power Management) and AAM (Advanced Acoustics Management) features aren’t permanent, once the drives are power cycled the issue starts all over again. The drive refuses any permanent disable ATA control commands.

There is a Dell firmware that will get rid of the issue, and take the firmware up to 05SDM1. My Clevo’s laptop’s drive started out with 2SDM1 firmware. The new FW makes the drive visibly quicker. The auto flasher doesn’t work, instead we need to manually force it, I’ll show you how.

1. Download the Seagate Update Utility ISO image, hosted on TideLog, this very blog, by clicking HERE. Extract the ZIP file, you’ll find an ISO file called Seagate Utility.iso.

2. Burn the extracted ISO to a CD-RW or DVD-RW, and restart your computer. When your computer restarts, enter your BIOS and make sure the computer is set to boot from CD.

3. The updater will start on its own, but it will actually fail even though a green screen is shown, you will need to manually force it. It will dump you back at a command prompt, so type:

FDLH -m HOLLIDAY -f 0005SDM1.LOD -i ST9500420AS -b -v

Essentially this line forces the detection of Seagate ST9500420AS drives, and force flashes it, even if the BIOS doesn’t have the Dell asset tag embedded.

4. This works on any machine, including Dell Studio, Asus, my Clevo M571TU, and the M570. Any machine with a Seagate ST9500420AS drive should work fine. Any drives with “GAS” on the end are the same drive but with G-Shock protection.

Comments No Comments »

If, like me you’ve changed your internet facing server’s Remote Desktop port to stop Haxors hammering your standard 3389 port, you’ll need to specify it from any client you connect to it from. Microsoft don’t make it obvious on their own client, but many 3rd party ones will have a Port box. The Mocha RDP client I use on my iPhone has such a box.

To do it in Microsoft’s own client, you need to specify your domain or IP as usual, then add a semicolon, then the port number, for example mydomain.com:1234. This works in both Windows XP, Vista and 7. There was no option in the connection options anywhere, so I started experimenting. A lot of services on my company server require specific semicolon and port dances after the URL, so it was the first thing I tried.

Microsoft, PLEASE put a Port box in the per-connection options. It would be easier for multiple connections and saved RDP files. Put a little text reminder in the connection box UI too 😉 It’s fine for home users the way it is default, but corporate users like me who need to change ports to stop server port attacks, and who has several servers all listening on different ports, we need an obvious easy way to set it 🙂

NOTE: Remote Desktop for Mac DOES NOT support custom ports, thanks to my lil lady Kana for that tidbit 😉

Comments No Comments »