Some Display Blocks are corrupted in Google Satellite Maps

[Art Du Rea]

Linux Mint 13 is based on Ubuntu 12.04.

Esteemed Ubuntu/Linux Mint Developers and Gurus:
=========================================
LM13 Mate 32 bit LiveDVD running from LOCKED SD card (NO HARD DRIVE)
Browser: Firefox 12.0 for Linux Mint (mint - 1.0)

I'm having some subtle display problems with the new Mint 13 (Mate 32 bit) LiveDVD (Read-Only) system I am trying to use. Note that these problems do NOT occur in Mint 8 or Mint 10 (both Gnome 32 bit), which are the only other Mint systems that I use.

My System:
=================
HP/(Compaq) dx2400
Intel Core 2 Duo
2 GB memory
Graphics
 Integrated Intel Graphics Media Accelerator 3100
    Resolution: 1920 x 1080
    Refresh: 60 Hz
    Normal Widescreen

Memory with Google Maps running approx 3/4 screen, with corrupted blocks:
mint@mint ~ $ free
             total used free shared buffers cached
Mem: 2052312 1400716 651596 0 138888 955796
-/+ buffers/cache: 306032 1746280
Swap: 0 0 0

I have noticed the intermittent problem repeatedly in Google Satellite Maps, which I use extremely often. I believe that Google Maps writes windows of 'picture blocks' of underlying satellite pictures, and overlay picture blocks of map labels. Frequently, one or a few blocks are corrupted(?) or scrambled(?). Once a block is corrupted it tends to stay corrupted even if I drag it out of view of the window and then drag it back in; or if I change the resolution up or down and then change it back to the previous setting. Occasionally the corrupted block gets 'repaired', but I can't seem to do that consistently, and occasionally MORE blocks get corrupted. I have had as many as 4 blocks get corrupted, with three of them adjacent blocks and 1 non-adjacent. I have noticed the problem in BOTH layers, but most often in the satellite pictures layer. I have attached screen dumps showing good images and corrupted images in both layers.

I have not tested this anomaly in any other applications ... as I said, I am deciding whether or not to use Mint 13, and as much as I like some of the new features of 13, this problem is a deal-breaker.

Thank you for any and all comments, suggestions, and assistance.
Blessings in abundance, all the best, & ENJOY!
Art in Carlisle, PA USA

[Art Du Rea (my-junk)]

I burned an Ubuntu system on a CD-ROM:

ubuntu-12.04-desktop-i386.iso

It has the same problem ... see the 5th attachment ...

Regards,
Art in Carlisle PA USA

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Chris Coulson (chrisccoulson)]

Thanks, but please have a read of the bug reporting guidelines before reporting bugs (https://wiki.ubuntu.com/MozillaTeam/Bugs - a link is provided on the submission form). In particular, using Apport to report Firefox bugs is mandatory. Also, it requests that you try it in another browser, which would have shown that this issue also occurs in Chrome (which means that it's most likely not a Firefox bug)

[Art Du Rea (my-junk)]

Thank you Chris ... I will definitely look at the reporting guidelines
before I report any more bugs. With respect to the browser, I plainly
stated that I'm strictly running a ROM LiveCD system and there is no
other browser to try ... As far as I know, Mint 13 Mate only has Firefox
installed. Also, I did not report this as a Firefox bug ... I only
noted that Firefox was the browser I was using when I found the problem.
  I am only slightly experienced with Mint/Ubuntu Linux and I had no
idea where the problem lurks ... I just know that what I saw was not
correct and I did a lengthy search to see if it was already reported. I
didn't find any other reports and so I thought I should report it.

Thank you for all the work you folks are doing to create a great OS. I
will try very hard to keep from complicating your work ... I know what a
pain it must be.

Blessings in abundance, all the best, & ENJOY!
Art in Carlisle, PA USA

Chris Coulson wrote:
> Thanks, but please have a read of the bug reporting guidelines before
> reporting bugs (https://wiki.ubuntu.com/MozillaTeam/Bugs - a link is
> provided on the submission form). In particular, using Apport to report
> Firefox bugs is mandatory. Also, it requests that you try it in another
> browser, which would have shown that this issue also occurs in Chrome
> (which means that it's most likely not a Firefox bug)
>
> ** Changed in: firefox (Ubuntu)
> Status: Confirmed => Invalid
>