Will the TSYNC issue that requires newer Linux kernels for Chromium be implemented in Vivaldi?



  • Seeing that Vivaldi is based on Chromium, will it be affected by the TSYNC issue mentioned in this Slashdot story: [url="http://linux.slashdot.org/story/15/03/08/1224210/google-chrome-requires-tsync-support-under-linux"]"Google Chrome Requires TSYNC Support Under Linux"[/url]? This change of Chromium is also mentioned on its issue pages: [url="https://code.google.com/p/chromium/issues/detail?id=401655"]"Not able to install any extension or app, getting error UTILITY_PROCESS_CRASHED_WHILE_TRYING_TO_INSTALL'. Could not install package because a utility process crashed. Try restarting chrome and trying again."[/url]. The links say that Linux kernel versions lower than 3.17 or without a patched kernel will not be supported by Chromium or Chrome, so wondering if this will also be the case with Vivaldi? Here's hoping that the TYSNC requirement will either not be implemented or implemented in a way that can be optional, because a few people do depend on an older kernel.


  • Vivaldi Team

    This affects Vivaldi, but the issue doesn't seem to be as serious as it looks at first glance, https://lists.debian.org/debian-kernel/2015/03/msg00151.html, they have a track record for providing fall backs for missing sandbox features. Also the chromium issue seems not to be related so TSYNC kernels: https://code.google.com/p/chromium/issues/detail?id=401655#c84.

    I expect users not to notice this at all, only that for some users vivaldi://sandbox will say No to "Seccomp-BPF sandbox supports TSYNC".

    Kind regards,

    Björgvin, Vivaldi developer



  • Thanks for the informative reply. Your post certainly makes things a little less stark for us who are a little behind the times kernel-wise.


  • Vivaldi Team

    There is (or perhaps was) a complete misunderstanding of the situation here. TSYNC usage does not prevent the running of Chromium based browser on older distros. Anyone who attempted to install a recent Chrome dev could have verified this for themselves—that Slashdot story was a piece of crap and quickly followed up with another story admitting this.

    Actually, TSYNC is a good thing. If you run Chrome 42 (or Opera 29+) on a system with a Linux kernel of 3.17 or newer (or with TSYNC support backported) the sandbox no longer needs to be setuid to root. The sandbox will work anyway. Personally, I am looking forward to Vivaldi updating to a Chromium 42 based back end. It allows for more flexible install options, for those of us with nosuid mount points.



  • Hey Ruarí, nice to see you over here. :)
    FYI Chromium update is being worked on. It's not gonna be 42, though… :whistle:


  • Vivaldi Team

    I'm not worried. It will eventually get to 42 and beyond I'm sure.

    P.S. Nice to see you too!



  • I actually meant, that 42 gets skipped. ;)


  • Vivaldi Team

    Well that works too! ;)


  • Vivaldi Team

    Was hoping chromium 42 would be the solution to the Ultimate question of life, the Universe, and everything, but seems we just jumped over it, indeed.



  • You know we need challenges, Palli. Just solving everything with 42 is too simple. :silly:


Log in to reply
 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.