Bug#501540: iceweasel: changing app name broke addon search

2008-10-12 Thread Sven Hartge
Hi.


The purely cosmetic fix for #428836 causes so much usability fall-out 
(this bug here and #501304), I begin to wonder if it wouldn't be best to 
just revert this fix, being quite close to the release of Lenny.

No one knows what other bugs or subtle changes in behavior have been 
introduced by the change in the application ID.

Firefox/Iceweasel is an application very visible to most users, shipping 
it with severe defects like a broken addon search utility would do Debian 
more harm than a fully rebranded version of it (IMO).

Grüße,
Sven.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#501540: iceweasel: changing app name broke addon search

2008-10-12 Thread Sven Hartge
Um 14:02 Uhr am 12.10.08 schrieb Sven Hartge:

 Firefox/Iceweasel is an application very visible to most users, shipping 
 it with severe defects like a broken addon search utility would do 
 Debian more harm than a fully rebranded version of it (IMO).

hrm ... than a fully rebranded version of it will do good. (IMO)

Grüße,
Sven.




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#501540: iceweasel: changing app name broke addon search

2008-10-08 Thread Pier Luigi Pau
Package: iceweasel
Version: 3.0.3-1
Severity: normal

Since version 3.0.3-1, application name was changed in iceweasel to
fix #428836. Apparently because of this, searching for addons
(extensions) from the Tools/Addons menu no longer works. Additionally,
clicking on the link to show all addons on that window redirects to
https://addons.mozilla.org/it/firefox/iceweasel (broken link). I think
the change in browser/app/application.ini may be responsible of this
behaviour.

I haven't been able to test 3.0.3-2 (not in mirrors yet for i386) but
I suspect it's still broken, because I recompiled 3.0.3-1 with the
debdiff attached for bug #501304 [1] to no avail.

However, search functionality is restored by going to about:config and
manually changing a few instances of %APP% to firefox, e.g. in
extensions.getAddons.search.browseURL,
extensions.getAddons.search.url; I haven't been able to restore the
link so far.

browser/app/profile/firefox.js in the sources seems to hold the
default values for the aforementioned configuration.

If possible, it would be nice to restore functionality for the default
configuration.

Please let me know if you need more details or assistance.

Best regards,
Pier Luigi Pau

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501304


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

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages iceweasel depends on:
ii  debianutils   2.30   Miscellaneous utilities specific t
ii  fontconfig2.6.0-1generic font configuration library
ii  libc6 2.7-13 GNU C Library: Shared libraries
ii  libgcc1   1:4.3.2-1  GCC support library
ii  libglib2.0-0  2.16.5-1   The GLib library of C routines
ii  libgtk2.0-0   2.12.11-3  The GTK+ graphical user interface
ii  libnspr4-0d   4.7.1-4NetScape Portable Runtime Library
ii  libstdc++64.3.2-1The GNU Standard C++ Library v3
ii  procps1:3.2.7-8  /proc file system utilities
ii  psmisc22.6-1 Utilities that use the proc filesy
ii  xulrunner-1.9 1.9.0.3-1  XUL + XPCOM application runner

iceweasel recommends no packages.

Versions of packages iceweasel suggests:
pn  latex-xft-fonts   none (no description available)
ii  libkrb53  1.6.dfsg.4~beta1-4 MIT Kerberos runtime libraries
pn  mozpluggernone (no description available)
pn  ttf-mathematica4.1none (no description available)
pn  xfonts-mathml none (no description available)
pn  xprintnone (no description available)
pn  xulrunner-1.9-gnome-s none (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]