[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
Sun May 23 20:46:37 UTC 2010


Hi,

..I just found out "chromium-browser --no-proxy-server &" 
does exactly what I want it to, use my proxy servers blindly
instead of trying to smart-ass itself around them. ;o)


On Sun, 23 May 2010 22:15:34 +0200, Arnt wrote in message 
<20100523221534.51e5c4dc at a45.fmb.no>:

> On Sun, 23 May 2010 12:24:18 -0500, Jonathan wrote in message 
> <20100523172417.GA14246 at progeny.tock>:
> 
> > Hi,
> > 
> > Arnt Karlsen wrote:
> > > On Sat, 22 May 2010 21:58:33 -0500, Jonathan wrote in message 
> > > <20100523025832.GA18572 at progeny.tock>:
> > 
> > >> Error message?
> > > 
> > > ..nothing, only the no-dns style "timed out" whine
> > 
> > Thanks.
> > 
> > > ..any dpkg etc path stunt or rebuild ideas that I can 
> > > use to put it into roomy /usr/local or /tmp instead?
> > 
> > Sure, you can use a symlink to put the symbols elsewhere:
> > 
> >   # mkdir /usr/local/debugging-symbols
> >   # mv -it /usr/local/debugging-symbols/ /usr/lib/debug
> >   # ln -st /usr/lib/ /usr/local/debugging-symbols/debug
> > 
> > and then download the chromium-browser-dbg package and install
> > it with dpkg as usual.
> > 
> > You can see whether this worked without waiting for a crash by
> > running chromium-browser --debug.  It mentions where it is reading
> > the symbols from.
> > 
> > Regards,
> > Jonathan
> > 
> 
> ..I cheated, I instead went for a wee genocide on installed docs ;o)
> but I was expecting a little more than this, now, I'm able to surf 
> the web with chromium-browser 8o) but get "No stack" from gdb, 
> makes no sense to me, but then again I'm a gdb newbie.  Hints?
> 
> ..further, I find I'm able to surf the web if I start chromium-browser
> at google.de, and navigate from there, I still can't surf my lan
> boxes, trying localhost surfing, returns this prompt message:"
> ERROR
> 
> The requested URL could not be retrieved
> 
> 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)"
> 
> ..gdb mentions it was configured as "i486-linux-gnu", way back in
> Woody Sid time when AMD's K6-2's were hot enough to warrant their own
> kernels, I then 3 years back the moved the disk into a P4 box, should
> gdb now be "i686-linux-gnu"??? 
> arnt at a45:/tmp $ chromium-browser --debug
> # Env:
> #     LD_LIBRARY_PATH=/usr/lib/chromium-browser
> #
> PATH=/usr/lib/chromium-browser:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
> #            GTK_PATH= # CHROMIUM_USER_FLAGS=
> #      CHROMIUM_FLAGS=
> /usr/bin/gdb /usr/lib/chromium-browser/chromium-browser
> -x /tmp/chromiumargs.fKwTS9 GNU gdb (GDB) 7.1-debian
> Copyright (C) 2010 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html> This is free software: you are free
> to change and redistribute it. There is NO WARRANTY, to the extent
> permitted by law.  Type "show copying" and "show warranty" for
> details. This GDB was configured as "i486-linux-gnu".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols
> from /usr/lib/chromium-browser/chromium-browser...Reading symbols
> from /usr/lib/debug/usr/lib/chromium-browser/chromium-browser...done.
> done. 
> (gdb) quit 
> arnt at a45:/tmp $ chromium-browser
> 
> (exe:6782): Gdk-WARNING **: XID collision, trouble ahead
> 
> (exe:6782): Gdk-WARNING **: XID collision, trouble ahead
> 
> (exe:6782): Gdk-WARNING **: XID collision, trouble ahead
> 
> (exe:6782): Gdk-WARNING **: XID collision, trouble ahead
> 
> (exe:6782): Gdk-WARNING **: XID collision, trouble ahead
> 
> (exe:6782): Gdk-WARNING **: XID collision, trouble ahead
> 
> (exe:6782): Gdk-WARNING **: XID collision, trouble ahead
> 
> (exe:6782): Gdk-WARNING **: XID collision, trouble ahead
> 
> (exe:6782): Gdk-WARNING **: XID collision, trouble ahead
>                                                                                                                                                                                     
> (exe:6782): Gdk-WARNING **: XID collision, trouble
> ahead 
> (exe:6782): Gdk-WARNING **: XID collision, trouble
> ahead 
> (exe:7143): Gdk-WARNING **: XID collision, trouble
> ahead 
> (exe:7143): Gdk-WARNING **: XID collision, trouble
> ahead 
> (exe:7143): Gdk-WARNING **: XID collision, trouble
> ahead 
> (exe:7143): Gdk-WARNING **: XID collision, trouble
> ahead 
> (exe:7143): Gdk-WARNING **: XID collision, trouble
> ahead 
> (exe:7143): Gdk-WARNING **: XID collision, trouble
> ahead arnt at a45:/tmp $     
> 
> ..trying chromium-browser --debug again and bt in gdb: 
> arnt at a45:/tmp $ chromium-browser --debug
> # Env:
> #     LD_LIBRARY_PATH=/usr/lib/chromium-browser
> #
> PATH=/usr/lib/chromium-browser:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
> #            GTK_PATH= # CHROMIUM_USER_FLAGS=
> #      CHROMIUM_FLAGS=
> /usr/bin/gdb /usr/lib/chromium-browser/chromium-browser
> -x /tmp/chromiumargs.01STaa GNU gdb (GDB) 7.1-debian
> Copyright (C) 2010 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html> This is free software: you are free
> to change and redistribute it. There is NO WARRANTY, to the extent
> permitted by law.  Type "show copying" and "show warranty" for
> details. This GDB was configured as "i486-linux-gnu".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols
> from /usr/lib/chromium-browser/chromium-browser...Reading symbols
> from /usr/lib/debug/usr/lib/chromium-browser/chromium-browser...done.
> done. 
> (gdb) bt 
> No stack.
> (gdb) 
> 
> ..firing off: "chromium-browser &"
> does nearly what it should do:
> arnt at a45:/tmp $ chromium-browser &
> [1] 8076
> arnt at a45:/tmp $ 
> (exe:8177): Gdk-WARNING **: XID collision, trouble ahead
> 
> (exe:8751): Gdk-WARNING **: XID collision, trouble ahead
> 
> (exe:8751): Gdk-WARNING **: XID collision, trouble ahead
> 
> (exe:8751): Gdk-WARNING **: XID collision, trouble ahead
> 
> (exe:8751): Gdk-WARNING **: XID collision, trouble ahead
> 
> (exe:8751): Gdk-WARNING **: XID collision, trouble ahead
> 
> [1]+  Done                    chromium-browser
> arnt at a45:/tmp $ 
> arnt at a45:/tmp $ 
> 


-- 
..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.





More information about the Pkg-chromium-maint mailing list