Control: affects -1 + python3-selenium Control: tags -1 - pending Control: clone -1 -2 Control: reassign -2 src:python-selenium Control: severity -2 wishlist Control: retitle -2 python-selenium should have an autopkgtest that tries to run chromium
Hi, On Thu, Feb 28, 2019 at 12:16:33PM +0100, Antoine Musso wrote: > There is a new Debian package 72.0.3626.96-1~deb9u2: > > https://lists.debian.org/debian-security-announce/2019/msg00039.html > > It addresses the crash when using --headless but --remote-debugging-port > still crashes Chromium (tested on Stretch). I confirm that this is reproducible with deb9u2. This fully breaks selenium when used with chromium: $ python3 -c 'import selenium.webdriver; selenium.webdriver.Chrome("/usr/bin/chromedriver")' Traceback (most recent call last): File "<string>", line 1, in <module> File "/usr/lib/python3/dist-packages/selenium/webdriver/chrome/webdriver.py", line 67, in __init__ desired_capabilities=desired_capabilities) File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py", line 91, in __init__ self.start_session(desired_capabilities, browser_profile) File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py", line 173, in start_session 'desiredCapabilities': desired_capabilities, File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py", line 233, in execute self.error_handler.check_response(response) File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/errorhandler.py", line 194, in check_response raise exception_class(message, screen, stacktrace) selenium.common.exceptions.WebDriverException: Message: unknown error: Chrome failed to start: exited abnormally (unknown error: DevToolsActivePort file doesn't exist) (The process started from chrome location /usr/bin/chromium is no longer running, so ChromeDriver is assuming that Chrome has crashed.) (Driver info: chromedriver=72.0.3626.96,platform=Linux 4.9.0-8-amd64 x86_64) $ An autopkgtest in python-selenium could have easily caught this issue. Please add one. Given that the bug log doesn't contain the relevant crash yet, I'm also giving it here. $ chromium --remote-debugging-port=0 [8463:8463:0307/112419.142839:ERROR:gl_surface_glx.cc(76)] XGetWindowAttributes failed for window 56623107. [8463:8463:0307/112419.142911:ERROR:gl_surface_glx.cc(811)] Failed to get GLXConfig [8463:8463:0307/112419.142935:ERROR:gpu_info_collector.cc(50)] gl::GLContext::CreateOffscreenGLSurface failed [8463:8463:0307/112419.142951:ERROR:gpu_info_collector.cc(180)] Could not create surface for info collection. [8463:8463:0307/112419.142972:ERROR:gpu_init.cc(61)] gpu::CollectGraphicsInfo failed. [8463:8463:0307/112419.145620:ERROR:viz_main_impl.cc(184)] Exiting GPU process due to errors during initialization [8424:8444:0307/112419.196685:ERROR:browser_gpu_channel_host_factory.cc(139)] Failed to launch GPU process. Received signal 11 SEGV_MAPERR 000000000080 #0 0x559a83872791 <unknown> #1 0x559a83872bfb <unknown> #2 0x559a8387325e <unknown> #3 0x7fd0ffb5f0e0 <unknown> #4 0x559a81c5a314 <unknown> #5 0x559a81c651b7 <unknown> #6 0x559a853e76b4 <unknown> #7 0x559a8332afff <unknown> #8 0x559a8336254c <unknown> #9 0x559a8336266e <unknown> #10 0x559a83373453 <unknown> #11 0x559a83373ed5 <unknown> #12 0x559a81bf6fd3 <unknown> #13 0x559a82070c32 <unknown> #14 0x559a81bf9089 <unknown> #15 0x559a81bfa039 <unknown> #16 0x559a81be65be <unknown> #17 0x559a8331d318 <unknown> #18 0x559a8331d581 <unknown> #19 0x559a8331d930 <unknown> #20 0x559a83328bfa <unknown> #21 0x559a8331b745 <unknown> #22 0x559a80fc3d39 ChromeMain #23 0x7fd0f1f892e1 __libc_start_main #24 0x559a80fc3b8a _start r8: 0000000000000003 r9: 00007fd0f20972f0 r10: 72672f656d6f682f r11: 6f632e2f656e686f r12: 00007ffd524f7be0 r13: 0000559a8ad1bb70 r14: 00007ffd524f7c30 r15: 0000559a8ad1b450 di: 00007ffd524f7be0 si: 0000559a8840a8f0 bp: 00007ffd524f7c80 bx: 0000559a8ad1b550 dx: 0000559a81c5a314 ax: 00007ffd524f7be0 cx: 0000000000000319 sp: 00007ffd524f7b80 ip: 0000559a81c5a314 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000004 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000080 [end of stack trace] Calling _exit(1). Core file will not be generated. $ For getting a better trace, we'd need the -dbgsym package, which is unavailable due to #894081. I'll look into building one. Helmut
