|
Bugzilla – Full Text Bug Listing |
| Summary: | chromium: sandbox related stacktrace printed | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Andreas Stieger <astieger> |
| Component: | Network | Assignee: | Forgotten User sM9JzehKpy <forgotten_sM9JzehKpy> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Minor | ||
| Priority: | P5 - None | CC: | aloisio, astieger, robert.simai, wbauer |
| Version: | 13.2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | openSUSE 13.2 | ||
| Whiteboard: | |||
| Found By: | Community User | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Andreas Stieger
2016-02-10 16:28:51 UTC
Hi Andreas, Would it be possible for you to try the chromium build from the network:chromium repository ? I wonder if this is caused by also the system libs (as the other bug) or that it is the patch to use the accelerated Video (libva). Thanks (In reply to Raymond Wooninck from comment #1) > Would it be possible for you to try the chromium build from the > network:chromium repository ? I wonder if this is caused by also the system > libs (as the other bug) or that it is the patch to use the accelerated Video > (libva). This was from network:chromium, chromium-48.0.2564.103-823.1.x86_64, last changelog: - Drop building with systemslibs. This is causing issues. It seems GPU code related. chrome://gpu shows the following for current chromium-48.0.2564.82-67.1.x86_64 -->-- Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Flash: Software only, hardware acceleration unavailable Flash Stage3D: Software only, hardware acceleration unavailable Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable Compositing: Software only, hardware acceleration unavailable Multiple Raster Threads: Unavailable Rasterization: Software only. Hardware acceleration disabled Video Decode: Software only, hardware acceleration unavailable Video Encode: Software only, hardware acceleration unavailable WebGL: Unavailable [...] Log Messages GpuProcessHostUIShim: The GPU process exited with code 256. --<-- Whereas the same on (most current) google-chrome-stable-48.0.2564.109-1.x86_64 gives some acceleration and no real errors: -->-- Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Flash: Hardware accelerated Flash Stage3D: Hardware accelerated Flash Stage3D Baseline profile: Hardware accelerated Compositing: Hardware accelerated Multiple Raster Threads: Enabled Rasterization: Software only. Hardware acceleration disabled Video Decode: Software only, hardware acceleration unavailable Video Encode: Hardware accelerated WebGL: Hardware accelerated --<-- (In reply to Andreas Stieger from comment #2) > (In reply to Raymond Wooninck from comment #1) > > Would it be possible for you to try the chromium build from the > > network:chromium repository ? I wonder if this is caused by also the system > > libs (as the other bug) or that it is the patch to use the accelerated Video > > (libva). > > This was from network:chromium, chromium-48.0.2564.103-823.1.x86_64, last > changelog: > - Drop building with systemslibs. This is causing issues. For completeness, same one this one from network:chromium: chromium-48.0.2564.103-826.1.x86_64 > - Drop completely the option to build with system libraries. This > could lead to issues (boo#965738) Ok. Thanks for testing. At least we can rule out the system libs. This leaves only one thing that could cause this and this would be the patch that activates libva (VAAPI) support. Also comment#3 points towards this as that it seems GPU related. As that this issue does not occur on Leap nor Tumbleweed, I will change the logic in the spec-file to not apply the patch on openSUSE 13.2. Once it got build we can test again. Thanks Andreas, Could you have a look with the latest build in network:chromium for openSUSE 13.2 ? IF this still generates the issue, then it must be a kernel issue as that the build is then equal to the ones delivered before the kernel updates. Thanks That fixes the issue, message no longer printed with that build. $ rpm -q --changelog chromium | head -n3 * Thu Feb 11 2016 tittiatcoke@gmail.com - Don't build with libva support for openSUSE 13.2 and lower (boo#966082) $ rpm -q chromium chromium-48.0.2564.103-828.1.x86_64 *** Bug 965566 has been marked as a duplicate of this bug. *** (In reply to Wolfgang Bauer from comment #8) > *** Bug 965566 has been marked as a duplicate of this bug. *** Apparently this is not only an issue on 13.2, but also Leap 42.1... This is an autogenerated message for OBS integration: This bug (966082) was mentioned in https://build.opensuse.org/request/show/359487 13.1 / chromium openSUSE-SU-2016:0491-1: An update that fixes 6 vulnerabilities is now available. Category: security (moderate) Bug References: 965566,965738,965999,966082 CVE References: CVE-2016-1622,CVE-2016-1623,CVE-2016-1624,CVE-2016-1625,CVE-2016-1626,CVE-2016-1627 Sources used: SUSE Package Hub for SUSE Linux Enterprise 12 (src): chromium-48.0.2564.109-49.1 openSUSE-SU-2016:0518-1: An update that fixes 6 vulnerabilities is now available. Category: security (moderate) Bug References: 965566,965738,965999,966082 CVE References: CVE-2016-1622,CVE-2016-1623,CVE-2016-1624,CVE-2016-1625,CVE-2016-1626,CVE-2016-1627 Sources used: openSUSE 13.1 (src): chromium-48.0.2564.109-125.1 |