[Pkg-chromium-maint] Bug#582705: chromium-browser: ..sees no net, hears no net like mob witnesses in movies, only liborbit2, all other browsers works fine.
Arnt Karlsen
arnt at c2i.net
Tue May 25 01:30:31 UTC 2010
On Sun, 23 May 2010 15:41:43 -0500, Jonathan wrote in message
<20100523204143.GA15733 at progeny.tock>:
> Arnt Karlsen wrote:
>
> > I was expecting a little more than this, now, I'm able to surf
> > the web with chromium-browser 8o)
>
> Hmm.
>
> > but get "No stack" from gdb,
>
> When you start a program with gdb, it will not actually start until
> you type "run".
..doh, knew it something this stupid simple. :oD
> See http://wiki.debian.org/Chromium/Debugging for hints.
>
> > While trying to retrieve the URL: http://127.0.0.1/
> > The following error was encountered:
> >
> > Access Denied.
> >
> > Access control configuration prevents your request from being
> > allowed at this time. Please contact your service provider if you
> > feel this is incorrect.
> >
> > Your cache administrator is jap at inf.tu-dresden.de.
> > Generated Sun, 23 May 2010 19:43:29 GMT by anon.inf.tu-dresden.de
> > (squid/2.7.STABLE8-20100219)"
>
> Looks like a server-side problem. What does "wget -S
> http://127.0.0.1/" say?
..this (with and without http_proxy):
arnt at a45:~/Documents/pdfer $ wget -S http://127.0.0.1/
Error parsing proxy URL http://localhost:4001 : Bad port number.
arnt at a45:~/Documents/pdfer $ unset http_proxy
arnt at a45:~/Documents/pdfer $ wget -S http://127.0.0.1/
--2010-05-25 03:21:31-- http://127.0.0.1/
Connecting to 127.0.0.1:80... connected.
HTTP request sent, awaiting response...
HTTP/1.1 200 OK
Date: Tue, 25 May 2010 01:21:31 GMT
Server: Apache/2.2.15 (Debian)
Last-Modified: Fri, 27 Mar 2009 18:54:47 GMT
ETag: "104f0c-1a5f-4661e4440ebc0"
Accept-Ranges: bytes
Content-Length: 6751
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html
Length: 6751 (6.6K) [text/html]
Saving to: `index.html'
100%[===========================>] 6,751 --.-K/s in 0s
2010-05-25 03:21:32 (152 MB/s) - `index.html' saved [6751/6751]
> > ..gdb mentions it was configured as "i486-linux-gnu"
>
> This is intentional. That triplet represents the machine type gdb was
> built for, which is i486 because Debian still supports old machines.
>
> > (exe:6782): Gdk-WARNING **: XID collision, trouble ahead
> > (exe:7143): Gdk-WARNING **: XID collision, trouble ahead
>
> Reminiscent of <http://bugs.debian.org/574725>. Do these messages
> appear only when viewing pages with flash?
..I get that impression, yes, see /tmp/gdb-chromium.txt:
arnt at a45:~/Documents/pdfer $ ll /tmp/gdb-chromium.txt \
&& md5sum /tmp/gdb-chromium.txt
-rw-r--r-- 1 arnt arnt 6202 2010-05-25 03:09 /tmp/gdb-chromium.txt
750a411f9c7d6283a0e0efa55e2912a5 /tmp/gdb-chromium.txt
arnt at a45:~/Documents/pdfer $
..this is with today's updated 5.0.375.55~r47796-1, the old
one's errors looked the same, AFAIR.
> Jonathan
>
--
..med vennlig hilsen = with Kind Regards from Arnt... ;o)
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gdb-chromium.txt
Type: text/x-microdvd
Size: 6202 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-chromium-maint/attachments/20100525/eb605d3f/attachment.bin>
More information about the Pkg-chromium-maint
mailing list