Closed Bug 955440 Opened 10 years ago Closed 10 years ago

Opening links fails when Firefox is used as handler.

Categories

(Instantbird Graveyard :: Other, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 955310

People

(Reporter: atuljangra, Unassigned)

References

Details

*** Original post on bio 2004 at 2013-06-13 13:38:00 UTC ***

STR
Click on any link in conversation. Make sure that your handler is set to be Firefox

Expected Output
Link should open in Firefox

Actual Output
Nothing happens. There is the following error in the Error Console
Timestamp: 06/13/2013 06:51:50 PM
Error: NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIExternalProtocolService.loadUrl]
Source File: chrome://chat/content/convbrowser.xml
Line: 1168
*** Original post on bio 2004 at 2013-06-13 13:39:27 UTC ***

My OS configuration:
Ubuntu 12.04 

Will be happy to provide any info whenever needed.
*** Original post on bio 2004 at 2013-06-13 13:42:32 UTC ***

I can't reproduce this on Linux, so it must be distro- or configuration-dependent. If clicking links works in TB, the first step would be to compare where things differ. (Start with the network prefs in case there is something "obvious" there.)
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** Original post on bio 2004 at 2013-06-13 13:44:17 UTC ***

(In reply to comment #1)
> My OS configuration:
> Ubuntu 12.04 

I'm fairly sure if this was a general problem on Ubuntu 12.04, we would have had many more complaints by now.

Which window manager do you use?
*** Original post on bio 2004 at 2013-06-13 13:45:29 UTC ***

Also, if you change from "Use firefox" to "Use other..." or "Always ask" and generate a *new* entry for FX, does that then work?
*** Original post on bio 2004 at 2013-06-13 14:00:20 UTC ***

I also have this problem from time to time using Kubuntu 13.04 amd64. I compile my own Ib to have it using amd64 too.

It's not very consistent.

I also think I crossed this once on Windows but I'm not certain anymore though I'm pretty sure.
*** Original post on bio 2004 at 2013-06-13 14:14:57 UTC ***

(In reply to comment #3)
> (In reply to comment #1)
> > My OS configuration:
> > Ubuntu 12.04 
> 
> I'm fairly sure if this was a general problem on Ubuntu 12.04, we would have
> had many more complaints by now.
> 
> Which window manager do you use?

I'm using Gnome with gnome-wm = Compiz 0.9.7.12
*** Original post on bio 2004 at 2013-06-13 14:16:44 UTC ***

(In reply to comment #4)
> Also, if you change from "Use firefox" to "Use other..." or "Always ask" and
> generate a *new* entry for FX, does that then work?

Tried doing this, I changes the entry from "Use Firefox: to "Always ask" And then in "Always ask" window I chose Firefox, following error was encountered in error console: 
Timestamp: 06/13/2013 07:45:47 PM
Error: NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIHandlerInfo.launchWithURI]
Source File: chrome://mozapps/content/handling/dialog.js
Line: 215

Also, just for the record, all other browsers are working fine.
*** Original post on bio 2004 at 2013-06-14 09:18:18 UTC ***

(In reply to comment #7)
> (In reply to comment #4)
> > Also, if you change from "Use firefox" to "Use other..." or "Always ask" and
> > generate a *new* entry for FX, does that then work?
> 
> Tried doing this, I changes the entry from "Use Firefox: to "Always ask" And
> then in "Always ask" window I chose Firefox, following error was encountered in
> error console: 

What I meant was: create a *new* handler pointing at Firefox (by pretending you want to add another browser but then selecting /usr/bin/firefox) and see if that works.
*** Original post on bio 2004 at 2013-06-15 16:14:03 UTC ***

Apparently this bug is not seen in the latest build that I build from source code. I today updated my repo by |python client.py checkout|. After updating and building, the links work perfectly, even with the default firefox handler.

But the error still persists in the tarball that I installed from http://ftp.instantbird.com/instantbird/nightly/latest-trunk/. I tried creating a new handler, and it works fine.
*** Original post on bio 2004 at 2013-06-17 11:29:13 UTC ***

(In reply to comment #9)

If it works fine in your local build but fails with our nightlies, I suspect the cause is 
ac_add_options --disable-gio
at http://lxr.instantbird.org/instantbird/source/tools/buildbot-configs/linux/mozconfig#27
*** Original post on bio 2004 at 2013-06-19 08:49:29 UTC ***

(In reply to comment #10)
> (In reply to comment #9)
> 
> If it works fine in your local build but fails with our nightlies, I suspect
> the cause is 
> ac_add_options --disable-gio
> at
> http://lxr.instantbird.org/instantbird/source/tools/buildbot-configs/linux/mozconfig#27

Oh right, that could be it! See bug 955310 (bio 1877).

Atul can you confirm this flag causes the issue? If so, we can resolve this as a dupe of that bug.
*** Original post on bio 2004 at 2013-06-19 20:24:09 UTC ***

Actually I'm not able to reproduce the problem.
Recently I wiped out my Instantbird profile and after that I'm not getting this problem.
I added the |ac_add_options --disable-gio| options to my mozconfig, but still I'm not able to generate the error.

Following is my mozconfig for details:

ac_add_options --enable-application=instantbird
mk_add_options MOZ_MAKE_FLAGS=-j4
ac_add_options --disable-gio
if [ "$DEBUG" ]; then
  mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../obj-instantbird-dbg
  ac_add_options --enable-extensions=inspector
  ac_add_options --enable-debug --disable-optimize --disable-jemalloc --enable-valgrind
else
  mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../obj-instantbird
  ac_add_options --disable-debug --enable-optimize
fi
*** Original post on bio 2004 at 2013-06-20 09:16:39 UTC ***

(In reply to comment #12)
> Actually I'm not able to reproduce the problem.
> Recently I wiped out my Instantbird profile and after that I'm not getting this
> problem.
> I added the |ac_add_options --disable-gio| options to my mozconfig, but still
> I'm not able to generate the error.

If you take your build with |ac_add_options --disable-gio| and create a new profile, can you reproduce? (I would not be surprised if once a profile had its about:config populated correctly there would no longer be a problem.)
*** Original post on bio 2004 at 2013-06-24 10:12:43 UTC ***

Ah, finally able to reproduce this with |ac_add_options --disable-gio|
Aleth, I guess this confirms that the issue is caused by this flag only
Depends on: 955310
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.