← Back to team overview

birdie-team team mailing list archive

[Bug 1196029] [NEW] "Segmentation fault" just after starting Birdie, WHEN PROXY RULES USED (.pac file)

 

Public bug reported:

1. Make sure no Birdie process remains, using:
ps -e | grep birdie

2. In your Desktop Environment (Cinnamon in my case), go to All Settings > Network > Network proxy
and set Method: Automatic, Configuration URL: /the/path/to/myproxyrules.pac

3. Start Birdie.

What happens (only useful lines listed)?
[_LEVEL_INFO 15:01:07.400886] Birdie.vala:175: Birdie version: 0.2.1+trunk
[_LEVEL_INFO 15:01:07.400972] Birdie.vala:177: Kernel version: 3.5.0-18-generic
Cannot make call: Cannot resolve proxy hostname ()
Segmentation fault (core dumped)

What should happen?
Birdie start normally. As all my other programs that use Internet too (Google Chrome, Firefox, etc.).

[Additional information]
This is my .pac proxy rules file, a basic one in fact:
function regExpMatch(url, pattern) {
	try { return new RegExp(pattern).test(url); } catch(ex) { return false; }
}

function FindProxyForURL(url, host) {
	if (shExpMatch(url, "http*://SOMEURL.tld/*")) return 'SOCKS5 myserverhere.lan:theporthere';
	if (regExpMatch(url, "regex-url-here")) return 'SOCKS5 myserverhere.lan:theporthere';
	[repeated line for other rules]
	return 'DIRECT';
}

=> shExpMatch (built-in function) is for wildcard rules.
=> regExpMatch (added function) is for regex rules.
All programs work correctly (and as set, when starting a browser and visiting some URL, the websites I set* use correctly the proxy I set, and the default rule for the rest is a direct connection).
Only Birdie quit unexpectedly at startup with the error listed above: "Cannot make call: Cannot resolve proxy hostname ()"

* Which are some domain names that Birdie will never try anyway, as very specific.
And else, it should be OK too anyway, just that it'll not be a direct connection, but it should also work even if Birdie was using one of these URL. As the proxy used in my rules is totally up.

** Affects: birdie
     Importance: Undecided
         Status: New


** Tags: bug fault general global network proxy segmentation startup

-- 
You received this bug notification because you are a member of Birdie
Developers, which is subscribed to Birdie.
Matching subscriptions: Birdie
https://bugs.launchpad.net/bugs/1196029

Title:
  "Segmentation fault" just after starting Birdie, WHEN PROXY RULES USED
  (.pac file)

Status in Birdie:
  New

Bug description:
  1. Make sure no Birdie process remains, using:
  ps -e | grep birdie

  2. In your Desktop Environment (Cinnamon in my case), go to All Settings > Network > Network proxy
  and set Method: Automatic, Configuration URL: /the/path/to/myproxyrules.pac

  3. Start Birdie.

  What happens (only useful lines listed)?
  [_LEVEL_INFO 15:01:07.400886] Birdie.vala:175: Birdie version: 0.2.1+trunk
  [_LEVEL_INFO 15:01:07.400972] Birdie.vala:177: Kernel version: 3.5.0-18-generic
  Cannot make call: Cannot resolve proxy hostname ()
  Segmentation fault (core dumped)

  What should happen?
  Birdie start normally. As all my other programs that use Internet too (Google Chrome, Firefox, etc.).

  [Additional information]
  This is my .pac proxy rules file, a basic one in fact:
  function regExpMatch(url, pattern) {
  	try { return new RegExp(pattern).test(url); } catch(ex) { return false; }
  }

  function FindProxyForURL(url, host) {
  	if (shExpMatch(url, "http*://SOMEURL.tld/*")) return 'SOCKS5 myserverhere.lan:theporthere';
  	if (regExpMatch(url, "regex-url-here")) return 'SOCKS5 myserverhere.lan:theporthere';
  	[repeated line for other rules]
  	return 'DIRECT';
  }

  => shExpMatch (built-in function) is for wildcard rules.
  => regExpMatch (added function) is for regex rules.
  All programs work correctly (and as set, when starting a browser and visiting some URL, the websites I set* use correctly the proxy I set, and the default rule for the rest is a direct connection).
  Only Birdie quit unexpectedly at startup with the error listed above: "Cannot make call: Cannot resolve proxy hostname ()"

  * Which are some domain names that Birdie will never try anyway, as very specific.
  And else, it should be OK too anyway, just that it'll not be a direct connection, but it should also work even if Birdie was using one of these URL. As the proxy used in my rules is totally up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/birdie/+bug/1196029/+subscriptions


Follow ups

References