search

gcarq / inox-patchset

Inox patchset tries to provide a minimal Chromium based browser with focus on privacy by disabling data transmission to Google.
BSD 2-Clause "Simplified" License
364 stars 25 forks source link

Inox crashes and refuses to start again if Google is made default search engine #126

Open Tank-Missile opened 6 years ago

Tank-Missile commented 6 years ago

I was trying to add my own custom search engine entry and make it default to remedy issue #118, when suddenly the browser crashed. From then on, the browser would not start until I deleted the configuration folder. Trying to start the browser from the terminal gave the following error:

[11606:11606:1216/082555.860625:ERROR:vaapi_wrapper.cc(1212)] vaInitialize failed: unknown libva error [11560:11560:1216/082556.037602:FATAL:url_fetcher_core.cc(107)] Check failed: originalurl.is_valid().

0 0x561a1f0a6407

Received signal 6

0 0x561a1f0a6407

r8: 0000000000000000 r9: 00007fff47c5d340 r10: 0000000000000008 r11: 0000000000000246 r12: 00007fab1f6166c0 r13: 00007fff47c5da50 r14: 0000000004b4312d r15: 00007fff47c5da48 di: 0000000000000002 si: 00007fff47c5d340 bp: 0000000000000068 bx: 0000000000000006 dx: 0000000000000000 ax: 0000000000000000 cx: 00007fab1ecf6860 sp: 00007fff47c5d340 ip: 00007fab1ecf6860 efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000 [end of stack trace] Calling _exit(1). Core file will not be generated.

founderio commented 6 years ago

You sir just made my day. I was able to launch inox and keep it open long enough to switch to the default search engine in time. My stacktrace looks similar - disabling "everything" did not help the issue as my command line clearly shows.

inox -disable-gpu --disable-extensions --disable-d3d11 --disable-local-storage --disable-notifications --disable-offne-pages --disable-plugin-power-saver --disable-plugins-discovery --disable-sync --disable-translate --disable-webgl --no-experiments --no-sandbox
[20271:20287:1218/195731.034202:ERROR:cert_verify_proc_nss.cc(922)] CERT_PKIXVerifyCert for sjs.bizographics.com failed err=-8181
[20271:20290:1218/195740.593748:ERROR:cert_verify_proc_nss.cc(922)] CERT_PKIXVerifyCert for www.bizographics.com failed err=-8181
[20271:20271:1218/195748.057024:FATAL:url_fetcher_core.cc(107)] Check failed: original_url_.is_valid(). 
#0 0x561047043407 <unknown>

Received signal 6
#0 0x561047043407 <unknown>
  r8: 0000000000000000  r9: 00007ffe9880dfa0 r10: 0000000000000008 r11: 0000000000000246
 r12: 00007f27f4b206c0 r13: 00007ffe9880e6b0 r14: 0000000004b4312d r15: 00007ffe9880e6a8
  di: 0000000000000002  si: 00007ffe9880dfa0  bp: 0000000000000068  bx: 0000000000000006
  dx: 0000000000000000  ax: 0000000000000000  cx: 00007f27f4200860  sp: 00007ffe9880dfa0
  ip: 00007f27f4200860 efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000
 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Also it seems that after changing to the default search engine, searching from the omnibox no longer works, at all. I believe this is related to #118.

Tank-Missile commented 6 years ago

I read into issue #118 more and setting --google-base-url="google.com" allows me to do google searches from the address bar without crashes. Obviously, a more permanent solution should be put in place. Just to be clear, adding different search engines other than Google does not cause a crash. I should have been more clear in the title. I need to pay attention to this website's layout more.

Eloston commented 6 years ago

@Tank-Missile

I should have been more clear in the title.

You can edit the title to be more suitable.