issue in natty narwhal using chromium

i tried to link this to my previous question, but appear to have linked it to a bug!

i want to link it to question #154730 but am unsure how!

Could try the daily ppa, may help with a later version

?? lol, maybe its because i'm still a noob, but i have no idea what that answer means!

any other suggestions?

Instead of saying "I'm a nob" why don't you try researching some, you might learn something. You would have easily found this:

https://launchpad.net/~chromium-daily/+archive/ppa

lol, i said "i'm a noob" not a nob, and it would have been just as easy for you to post the link and suggest i look there.

i have looked at that link, and it leaves me none the wiser, as i dont understand what a ppa is, or how it can help me.

having googled ppa, i find that they are "Personal Package Archives (PPA) allow you to upload Ubuntu source packages to be built and published as an apt repository by Launchpad"
which i still dont understand!

i accept that many users of linux are experienced programmers, and are happy to write code, and test ideas, but i am not one of those people, i am one of the rapidly growing number of people who are turning to linux as an alternative to microsoft.

as my problem with chromium seems to be a very specific one which relates to a specific user account on my machine, i was not really expecting to find an answer immediately, and was more interested in bringing the issue to the attention of the wider community in the hope that someone who had also just upgraded from 10 10 to 11 04 had experienced the same issue and found a solution.

i am interested in learning things, and am trying to do so by my interaction with this community.

i apologise if i upset you by re-clicking the "i still need an answer button" but i do feel that your answers have not helped me in the slightest.

sorry, was meant to be noob, bit of a typo.

If you run (in a terminal)

sudo add-apt-repository ppa:chromium-daily/ppa; sudo apt-get update; sudo apt-get -y upgrade

It may help

@actionparsnip
As this question's description states, this issue only affects one user account--it does not occur with another user account on the same machine. Therefore, there is almost certainly a solution to be found that doesn't require using daily builds. This Chromium problem arose as a tangential issue while working on a Firefox problem (which is now fixed) in https://answers.launchpad.net/ubuntu/+source/firefox/+question/154730. Once I found that the Chromium problem didn't admit to a trivially simple solution, I advised Matthew to post a new question about it. Therefore, him having done so is not a result of any unwillingness on his part to do proper research, but because I suggested it.

@matthew cooper
The solution proposed by actionparsnip--to upgrade to using daily builds--may well fix this problem, though you would be exposed to other bugs as a result of using a very unstable version of Chromium. Using daily builds of Chromium is a way to contribute to the project, in that you get to experience bleeding-edge bugs firsthand and report them--you might consider this an advantage. But if you don't want to use daily builds, or you try using the daily build and the problem persists, then please post a reply reopening this question and indicating that you still need help.

@ actionparsnip
thankyou for your suggestion, however i was going to come back to you and ask what this code would do, having done a bit of reading round the subject, and being reticent to run what seemed to be an unstable version of chromium. Eliah Kagan has already answered my question in the above post, and i have decided not to go with that solution as i am not a confident enough user and my computer is also used by my partner and kids, who would not appreciate using a version of chromium that is liable to have repeated issues.

@eliahkagan
thankyou for your clarification of daily builds, as you can see from above i have chosen not to try this solution.
i would be happy to work through any other potential solutions with yourself or anyone else who can suggest a fix.

The code adds the daily build ppa then installs the daily build version of Chromium.

@actionparsnip
please read my previous comment, this will explain why i have re opened this question.

OK--so far, you have found that the problem does not occur on the same website(s) when running Chromium as a different user. However, our initial attempt to clear out Chromium's configuration files did not fix the problem. So let's look harder for files in your user's home folder that Chromium may be using, and which may be associated with this problem. Please open a Terminal window and run the command:

find ~ -iname \*chrom\*

That command may return a very large number of hits, or maybe very few. If you have files of your own (e.g., documents) that include "chrom" in their name, those files may appear. Therefore, you should look over the output of that command before posting it here, because it may contain confidential or otherwise sensitive information. (For example, if you are a doctor and one of your patients names is John Chromie, confidential information might be revealed by the name of documents relating to his care.)

Once you have made sure it's OK to post the results of that search, please select all the text in the Terminal (Edit > Select All), copy them to the clipboard (Edit > Copy), and paste them here.

In addition to providing that information, please provide a link/links to the specific web page or pages where you are experiencing this problem. That may provide a clue as to its cause.

the following is a link to a specific ebay page, when clicking to enlarge the picture, the result opens in a "supersized" window (cant think of a better way to describe it!)

http://cgi.ebay.co.uk/LG-42LF2500-42IN-FULL-HD-DIGITAL-LCD-TV-NEW-DEAL-/330558032172?_trksid=p5197.m7&_trkparms=algo%3DLVI%26itu%3DUCI%26otn%3D2%26po%3DLVI%26ps%3D63%26clkid%3D8866313009476676210#ht_2604wt_962

this is the address of the enlarged picture
http://cgi.ebay.co.uk/ws/eBayISAPI.dll?VISuperSize&item=330558032172

having spent a while playing with ebay (i am beginning to think that this issue is particular to ebay) it seems that it is only when certain paths in ebay are followed that the "supersized" window occurs.

if i open a new chromium window, and click on one of the featured items, on the front page, then click to enlarge the picture, we go "supersize" if i choose to search for a specific item, and then click to enlarge it, everything is normal!

i am beginning to think that this issue may be the equivalent of taking a car to the mechanic and complaining that " there's a funny rattle when i drive down a certain road at a certain speed, on a wednesday if its raining" ! to which the obvious answer is "dont drive down that road a that speed then"!!!

however, i am one of those people who find that these little niggly things are really annoying and would like to find a solution, and do appreciate the time and effort you are putting in on my behalf :)

that said, i have also run the code you asked, and this is the output:-

milly@milly-EQUIUM-A200:~$ find ~ -iname \*chrom\*
/home/milly/.config/chromium
/home/milly/.config/chromium/Default/Local Storage/chrome-devtools_devtools_0.localstorage
/home/milly/.config/chromium/Default/Local Storage/chrome-extension_eemcgdkfndhakfknompkggombfjjjeno_0.localstorage
/home/milly/.config/chromium/Default/Local Storage/chrome-extension_ajgmnekpakhkbnhehnpkminifbpmkghg_0.localstorage
/home/milly/.gnome2/gnome-art/thumbnails/GTK2-Blue-Chrome-Th.png
/home/milly/.wine/drive_c/windows/system32/gecko/1.0.0/wine_gecko/defaults/profile/US/chrome
/home/milly/.wine/drive_c/windows/system32/gecko/1.0.0/wine_gecko/defaults/profile/US/chrome/userChrome-example.css
/home/milly/.wine/drive_c/windows/system32/gecko/1.0.0/wine_gecko/defaults/profile/chrome
/home/milly/.wine/drive_c/windows/system32/gecko/1.0.0/wine_gecko/defaults/profile/chrome/userChrome-example.css
/home/milly/.wine/drive_c/windows/system32/gecko/1.0.0/wine_gecko/chrome
/home/milly/.mozilla/firefox/ovoxparu.default/chromeappsstore.sqlite
/home/milly/.PlayOnLinux/configurations/icones/Google Chrome
/home/milly/.PlayOnLinux/wineprefix/everest/drive_c/windows/system32/gecko/1.0.0/wine_gecko/defaults/profile/US/chrome
/home/milly/.PlayOnLinux/wineprefix/everest/drive_c/windows/system32/gecko/1.0.0/wine_gecko/defaults/profile/US/chrome/userChrome-example.css
/home/milly/.PlayOnLinux/wineprefix/everest/drive_c/windows/system32/gecko/1.0.0/wine_gecko/defaults/profile/chrome
/home/milly/.PlayOnLinux/wineprefix/everest/drive_c/windows/system32/gecko/1.0.0/wine_gecko/defaults/profile/chrome/userChrome-example.css
/home/milly/.PlayOnLinux/wineprefix/everest/drive_c/windows/system32/gecko/1.0.0/wine_gecko/chrome
/home/milly/.mozilla.old/firefox/vw0d3oe4.default/chromeappsstore.sqlite
/home/milly/.mozilla.old/firefox/vw0d3oe4.default/chrome
/home/milly/.mozilla.old/firefox/vw0d3oe4.default/chrome/userChrome-example.css
/home/milly/Documents/Milly/Milly/AppData/Roaming/Microsoft/Internet Explorer/Quick Launch/Google Chrome.lnk
/home/milly/Documents/Milly/Milly/AppData/Roaming/Mozilla/Firefox/extensions/{E9A1DEE0-C623-4439-8932-001E7D17607D}/chrome.manifest
/home/milly/Documents/Milly/Milly/AppData/Roaming/Mozilla/Firefox/extensions/{E9A1DEE0-C623-4439-8932-001E7D17607D}/chrome.manifest.dev
/home/milly/Documents/Milly/Milly/AppData/Roaming/Mozilla/Firefox/extensions/{E9A1DEE0-C623-4439-8932-001E7D17607D}/chrome
/home/milly/Documents/Milly/Milly/AppData/Local/Microsoft/Windows/Temporary Internet Files/Low/Content.IE5/9IRQK369/uk_chrome[1].gif
/home/milly/Documents/Milly/Milly/AppData/Local/Google/Chrome
/home/milly/Documents/Milly/Milly/AppData/Local/Temp/chrome_shutdown_ms.txt
/home/milly/Documents/Milly/Milly/AppData/Local/Temp/chrome_installer.log
/home/milly/.cache/chromium
milly@milly-EQUIUM-A200:~$

i didnt find anything which could embarrass me or anyone else, so the output is complete.

hope this helps!

And you can confirm that following those exact steps does *not* produce the problem, when running Chromium on a different user account on the same machine?

yes, using the same item in ebay :-
http://cgi.ebay.co.uk/Mens-Nike-Sleeveless-Hooded-Vest-Top-Grey-/150597938749?pt=UK_Men_s_Hoodies_Sweats&var=&hash=item68c7864af3#ht_1130wt_1004
and following the same path:- open ebay; choose an item from the main (front) page; enlarge the item
this was done in 3 clicks from the google result for "ebay"
 in the main (milly) account this led to the "supersize" result, and a normal result in the daughters account

OK, try quitting Chromium and running this command, which you've run before:

rm -r ~/.config/chromium ~/.cache/chromium

Immediately followed by these (one after the other), which you have not:

cd /home/milly/Documents/Milly/Milly/AppData/Local/Google
mv Chrome Chrome.old

Then open Chromium again and see if the problem has gone away. If it has, great--you can mark this question as Solved (and delete /home/milly/Documents/Milly/Milly/AppData/Local/Google/Chrome.old, if you like). Otherwise, please click on the wrench icon in Chromium (to the immediate right of the address bar) and click About Chromium, then take a screenshot, make sure that the whole About Chromium window is visible in the screenshot, then post it on the web and post a link to it here.

ok, i ran the code, then ran chromium again, to no avail! still the same result, still using the same nike sweat top, to maintain consistency
below is a link to the screenshot

http://postimage.org/image/323t95pxg/

success!:)
very happy to report that after installing version 11.0.xxxx ebay seems to work ok!

can i just say a big thankyou for your time and effort, and patience, in helping me sort out these two problems!

Elaih, you are a credit to the ubuntu community

many thanks

Matt

Thanks Eliah Kagan, that solved my question.