They seem to be fine: $ debsums libxcb1 /usr/lib/libxcb.so.1.1.0 OK /usr/share/doc/libxcb1/copyright OK /usr/share/doc/libxcb1/changelog.Debian.gz OK
$ debsums libxcb1-dbg /usr/lib/debug/usr/lib/libxcb.so.1.1.0 OK /usr/share/doc/libxcb1-dbg/copyright OK /usr/share/doc/libxcb1-dbg/changelog.Debian.gz OK Now I've noticed that this segmentation fault occurs whenever I run Chromium with the --single-process flag. So I think it has nothing to do with the lifehacker.com crashes. If I run without that flag, I get these errors: [21419:21419:0417/141426:ERROR:gl_surface_glx.cc(384)] GLX 1.3 or later is required. [21419:21419:0417/141426:ERROR:gl_surface_linux.cc(58)] GLSurfaceGLX::InitializeOneOff failed. And soon after I get an 'Aw, Snap!" crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309045 Title: Chromium tab crashes when opening any lifehacker.com page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1309045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
