Lei Zhang, the patch is both attached to this bug [1] and in the upstream bug I linked to this one [2].
I understand that x-www-browser is a Debianism. It was not my decision to include it in xdg-settings. I think the x-www-browser issue is a separate issue from this bug, and one that I doubt will be changed.
As for sorting this issue out with xdg-utils upstream, that's what I'm doing, no? My concern is only that xdg-settings (upstream and chromium both) is improperly using the full path when in GNOME. GNOME does not use full path values in its gconf keys. That is what I'm trying to solve.
Lei Zhang, the patch is both attached to this bug [1] and in the upstream bug I linked to this one [2].
I understand that x-www-browser is a Debianism. It was not my decision to include it in xdg-settings. I think the x-www-browser issue is a separate issue from this bug, and one that I doubt will be changed.
As for sorting this issue out with xdg-utils upstream, that's what I'm doing, no? My concern is only that xdg-settings (upstream and chromium both) is improperly using the full path when in GNOME. GNOME does not use full path values in its gconf keys. That is what I'm trying to solve.
[1] http:// launchpadlibrar ian.net/ 38457518/ gnome_browser_ basename. patch /bugs.freedeskt op.org/ show_bug. cgi?id= 26300
[2] https:/