Debian Bug report logs - #568908
uses iceweasel for urls despite gconf being configured to use chromium

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Joey Hess <joeyh@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: uses iceweasel for urls despite gconf being configured to use chromium

Date: Mon, 8 Feb 2010 13:16:20 -0500

[Message part 1 (text/plain, inline)]

Package: gnome-terminal
Version: 2.28.2-1
Severity: normal

I have configured gnome to use chromium-browser as my web browser, and
that worked for opening urls in gnome-terminal, until today. Now for
reasons that escape me, it is always running iceweasel.

None of the far-too-many possible ways to configure a browser point to
iceweasel:

joey@gnu:~>gconftool --dump / |grep iceweasel
joey@gnu:~>gconftool --get /desktop/gnome/url-handlers/http/command
chromium-browser %s
joey@gnu:~>gconftool --get /desktop/gnome/applications/browser/exec
chromium-browser
joey@gnu:~>echo $BROWSER
w3m
joey@gnu:~>dir /etc/alternatives/gnome-www-browser
lrwxrwxrwx 1 root root 25 Sep 29 21:50 /etc/alternatives/gnome-www-browser -> /usr/bin/epiphany-browser*
joey@gnu:~>dir /etc/alternatives/x-www-browser 
lrwxrwxrwx 1 root root 18 Jul 18  2009 /etc/alternatives/x-www-browser -> /usr/bin/konqueror*
joey@gnu:~>dir /etc/alternatives/www-browser
lrwxrwxrwx 1 root root 12 Dec 16  2008 /etc/alternatives/www-browser -> /usr/bin/w3m*

I made a ~/bin/iceweasel that just runs chromium-browser, which works
around the problem, but I do not understand why the gconf setting is
being ignored.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.31-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gnome-terminal depends on:
ii  gnome-terminal-data        2.28.2-1      Data files for the GNOME terminal 
ii  libatk1.0-0                1.28.0-1      The ATK accessibility toolkit
ii  libc6                      2.10.2-5      Embedded GNU C Library: Shared lib
ii  libdbus-glib-1-2           0.84-1        simple interprocess messaging syst
ii  libgconf2-4                2.28.0-1      GNOME configuration database syste
ii  libglib2.0-0               2.22.4-1      The GLib library of C routines
ii  libgtk2.0-0                2.18.6-1      The GTK+ graphical user interface 
ii  libice6                    2:1.0.6-1     X11 Inter-Client Exchange library
ii  libpango1.0-0              1.26.2-1      Layout and rendering of internatio
ii  libsm6                     2:1.1.1-1     X11 Session Management library
ii  libstartup-notification0   0.10-1        library for program launch feedbac
ii  libvte9                    1:0.22.5-1+b1 Terminal emulator widget for GTK+ 
ii  libx11-6                   2:1.3.3-1     X11 client-side library

Versions of packages gnome-terminal recommends:
ii  gvfs                     1.4.3-1         userspace virtual filesystem - ser
ii  yelp                     2.28.0+webkit-2 Help browser for GNOME

gnome-terminal suggests no packages.

-- debconf-show failed

-- 
see shy jo

[signature.asc (application/pgp-signature, inline)]

Message #10 received at 568908@bugs.debian.org (full text, mbox, reply):

From: Josselin Mouette <joss@debian.org>

To: Joey Hess <joeyh@debian.org>, 568908@bugs.debian.org

Subject: Re: Bug#568908: uses iceweasel for urls despite gconf being configured to use chromium

Date: Mon, 08 Feb 2010 23:40:17 +0100

[Message part 1 (text/plain, inline)]

Le lundi 08 février 2010 à 13:16 -0500, Joey Hess a écrit : 
> I have configured gnome to use chromium-browser as my web browser, and
> that worked for opening urls in gnome-terminal, until today. Now for
> reasons that escape me, it is always running iceweasel.

Maybe it is the default handler for text/html files.

I have no idea why gvfs would use this setting instead of the URL
handler, though. The logic of the GConf module still evades any kind of
rational thought.

-- 
 .''`.      Josselin Mouette
: :' :
`. `'   “I recommend you to learn English in hope that you in
  `-     future understand things”  -- Jörg Schilling

[signature.asc (application/pgp-signature, inline)]

Message #15 received at 568908@bugs.debian.org (full text, mbox, reply):

From: Joey Hess <joeyh@debian.org>

To: 568908@bugs.debian.org

Subject: Re: Bug#568908: uses iceweasel for urls despite gconf being configured to use chromium

Date: Mon, 8 Feb 2010 20:08:50 -0500

[Message part 1 (text/plain, inline)]

Josselin Mouette wrote:
> Maybe it is the default handler for text/html files.

It's looking at desktop files. I removed iceweasel (and chromium was
used as configured for urls). Then I put this in
/usr/share/applications/xmessage.desktop and ran
update-desktop-database, and gnome-terminal used it for urls.

[Desktop Entry]
Exec=xmessage %u
Type=Application
MimeType=text/html

The Type=Application seems to be crucial.

-- 
see shy jo

[signature.asc (application/pgp-signature, inline)]

Message #20 received at 568908@bugs.debian.org (full text, mbox, reply):

From: Joey Hess <joeyh@debian.org>

To: 568908@bugs.debian.org

Subject: Re: Bug#568908: uses iceweasel for urls despite gconf being configured to use chromium

Date: Mon, 8 Feb 2010 20:41:57 -0500

[Message part 1 (text/plain, inline)]

So, when gnome-terminal asks gvfs to handle an url for it, gvfs goes off
and *downloads* the head of the url, so it can run magic on it. The
preferred application settings are entirely ignored AFAICS. If the file
is a tarball, it opens file-roller. If it's a file, it opens gedit. Etc.

If the file is a cgi script that contains sleep 120, gnome-terminal just
hangs for 2 minutes. That means *all* your terminals hang if you open
this url. Sweet.  http://kitenet.net/~joey/tmp/himom.cgi

See also: #561272 Now I think that in that bug, it's trying
to mount the ftp site so that it can download the file, in order to
determine what to run.

-- 
see shy jo

[signature.asc (application/pgp-signature, inline)]

Message #25 received at 568908@bugs.debian.org (full text, mbox, reply):

From: Joey Hess <joeyh@debian.org>

To: 568908@bugs.debian.org

Cc: gnome-vfs@packages.debian.org

Subject: Re: Bug#568908: uses iceweasel for urls despite gconf being configured to use chromium

Date: Mon, 8 Feb 2010 21:09:30 -0500

[Message part 1 (text/plain, inline)]

I downgraded libgnomevfs2-0 and libgnomevfs2-common fro
1:2.24.2-2 to 1:2.24.2-1, and this bug went away. 

I see nothing in the changelog that could explain this behavior,
so I assume the bug was introduced by this:

  * Refresh all patches so they apply cleanly. This fixes FTBFS with the new
    source format 3.0 (quilt). Closes: #538622

-- 
see shy jo

[signature.asc (application/pgp-signature, inline)]

Message #30 received at 568908@bugs.debian.org (full text, mbox, reply):

From: Josselin Mouette <joss@debian.org>

To: Joey Hess <joeyh@debian.org>, 568908@bugs.debian.org

Subject: Re: Bug#568908: uses iceweasel for urls despite gconf being configured to use chromium

Date: Thu, 11 Feb 2010 20:26:40 +0100

[Message part 1 (text/plain, inline)]

Le lundi 08 février 2010 à 21:09 -0500, Joey Hess a écrit : 
> I downgraded libgnomevfs2-0 and libgnomevfs2-common fro
> 1:2.24.2-2 to 1:2.24.2-1, and this bug went away. 
> 
> I see nothing in the changelog that could explain this behavior,
> so I assume the bug was introduced by this:
> 
>   * Refresh all patches so they apply cleanly. This fixes FTBFS with the new
>     source format 3.0 (quilt). Closes: #538622

The only thing that could explain the change would be, as in one of your
previous reports, broken GConf schema/defaults installation.

Could this also be related to your btrfs issue?

Cheers,
-- 
 .''`.      Josselin Mouette
: :' :
`. `'   “I recommend you to learn English in hope that you in
  `-     future understand things”  -- Jörg Schilling

[signature.asc (application/pgp-signature, inline)]

Message #35 received at 568908@bugs.debian.org (full text, mbox, reply):

From: Joey Hess <joeyh@debian.org>

To: 568908@bugs.debian.org

Subject: Re: Bug#568908: uses iceweasel for urls despite gconf being configured to use chromium

Date: Tue, 9 Mar 2010 13:44:13 -0500

[Message part 1 (text/plain, inline)]

I don't know if this is somehow related to btrfs.
I was not able to find a file that is somehow mangled or missing
that caused the problem. After re-upgrading the packages, I no
longer see the problem.

-- 
see shy jo

[signature.asc (application/pgp-signature, inline)]

Message #40 received at 568908@bugs.debian.org (full text, mbox, reply):

From: Joey Hess <joeyh@debian.org>

To: 568908@bugs.debian.org

Subject: FWD: Re: btrfs issues

Date: Tue, 6 Apr 2010 15:20:17 -0400

[Message part 1 (text/plain, inline)]

----- Forwarded message from cwillu <cwillu@cwillu.com> -----

Date: Tue, 6 Apr 2010 12:42:15 -0600
From: cwillu <cwillu@cwillu.com>
To: Joey Hess <joey@kitenet.net>
Subject: Re: btrfs issues

On Tue, Apr 6, 2010 at 12:38 PM, cwillu <cwillu@cwillu.com> wrote:
> On Tue, Apr 6, 2010 at 12:33 PM, Joey Hess <joey@kitenet.net> wrote:
>> cwillu wrote:
>>> New information on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575891
>>>
>>> Turns out to have been an unsafe assumption on dpkg's part with
>>> apparently astronomic odds of being triggered on most filesystems.
>>>
>>> Putting /var/lib/dpkg on an ext3 mount (I used a bind mount from my
>>> /boot) works around it until the problem can be fixed in dpkg.
>>
>> Cwillu, thanks for following up.
>>
>> That does seem to explain #569058, closing that bug.
>>
>> At the moment, my other two problems, #567135 and #568908, do not
>> seem likely to be caused by the dpkg bug.
>
> #567135 is definitely caused by triggers and postinst scripts going
> missing from /var/lib/dpkg/info, that's the behaviour that got me
> looking at dpkg in the first place. I wouldn't be surprised if #568908
> also had similar roots.
>

And having looked into that, gconf schema corruption is another issue
I've run into which can be traced back to a failure to run the
postinst script which registers it;
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568908#30 refers to
such corruption as a likely cause.

----- End forwarded message -----

-- 
see shy jo

[signature.asc (application/pgp-signature, inline)]

Send a report that this bug log contains spam.