webbrowser app Segmentation fault (core dumped) on 17.04 Unity7

Bug #1649262 reported by dinamic on 2016-12-12
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Undecided
Unassigned
qtdeclarative-opensource-src (Ubuntu)
Critical
Unassigned

Bug Description

17.04 unity7

~$ webbrowser-app
libGL error: MESA-LOADER: failed to retrieve device information
libGL error: Version 4 or later of flush extension not found
libGL error: failed to load driver: i915
libGL error: MESA-LOADER: failed to retrieve device information

(webbrowser-app:4695): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.

(webbrowser-app:4695): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.

(webbrowser-app:4695): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.
UCUriHandler: Empty "APP_ID" environment variable, ignoring.
unity::action::ActionManager::ActionManager(QObject*):
 Could not determine application identifier. HUD will not work properly.
 Provide your application identifier in $APP_ID environment variable.
libGL error: MESA-LOADER: failed to retrieve device information
libGL error: Version 4 or later of flush extension not found
libGL error: failed to load driver: i915
libGL error: MESA-LOADER: failed to retrieve device information
could not open containers config file "/home/pixel/.local/share/libertine/ContainersConfig.json"
APP_ID isn't set, the handler can not be registered
Input device added: "Power Button" "/dev/input/event1" QFlags(0x1)
Input device added: "Power Button" "/dev/input/event0" QFlags(0x1)
Input device added: "HDA Intel PCH Line Out" "/dev/input/event7" QFlags(0x20)
Input device added: "HDA Intel PCH Rear Mic" "/dev/input/event5" QFlags(0x20)
Input device added: "HDA Intel PCH Line" "/dev/input/event6" QFlags(0x20)
Input device added: "YSPRINGTECH USB OPTICAL MOUSE" "/dev/input/event2" QFlags(0x2)
Input device added: "USB USB Keykoard" "/dev/input/event3" QFlags(0x1|0x10)
Input device added: "USB USB Keykoard" "/dev/input/event4" QFlags(0x1)

(webbrowser-app:4695): IBUS-WARNING **: Unable to connect to ibus: Could not connect: Permission denied
QOpenGLShader: could not create shader
QOpenGLShader: could not create shader
QOpenGLShader: could not create shader
QOpenGLShader: could not create shader
QOpenGLShader: could not create shader
QOpenGLShader: could not create shader
APP_ID isn't set, the handler ignored
qml: Loaded 13 UA override(s) from file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-desktop.js
^CSegmentation fault (core dumped)

dinamic (dinamic6661) wrote :

webbrowser-app/zesty-proposed,now 0.23+17.04.20161202-0ubuntu1 amd64 [installed,automatic]

dinamic (dinamic6661) wrote :

gpu intel sandybridge something

Olivier Tilloy (osomon) wrote :

This looks like a mesa issue. Can you launch e.g. glxgears?

Changed in webbrowser-app (Ubuntu):
status: New → Incomplete
dinamic (dinamic6661) wrote :

soory, i can't test on that pc again (gpu/hdd died almost at the same time r.i.p)
on intel sady bridge webbrowser-app works fine

dinamic (dinamic6661) wrote :

oh, mixed up, this is i think on intel but with the old hdd that died + proposed active

dinamic (dinamic6661) wrote :

17.04
on proposed mesa 13.0.2-1ubuntu1 (main)
on release mesa 12.0.3-1ubuntu2 (main)

if you want to trigger this bug enable proposed

dinamic (dinamic6661) wrote :

QOpenGLShader: could not create shader
QOpenGLShader: could not create shader
intel_do_flush_locked failed: Input/output error
[1213/205431:FATAL:oxide_browser_process_main.cc(423)] Check failed: state_ == STATE_NOT_STARTED || state_ == STATE_SHUTDOWN. BrowserProcessMain::Shutdown() should be called before process exit
#0 0x7f9c6500292e <unknown>
#1 0x7f9c6501c0ee <unknown>
#2 0x7f9c6607fad9 <unknown>
#3 0x7f9ca09872e0 <unknown>
#4 0x7f9ca098733a exit
#5 0x7f9c943cc7ce <unknown>
#6 0x7f9c943d278c <unknown>
#7 0x7f9c943d2959 <unknown>
#8 0x7f9c943d811b <unknown>
#9 0x7f9c941c887c <unknown>
#10 0x7f9c943d944a <unknown>
#11 0x7f9c941b8d1b <unknown>
#12 0x7f9c941b8f86 <unknown>
#13 0x7f9c941b93a8 <unknown>
#14 0x7f9ca203e69c <unknown>
#15 0x7f9ca203f1f2 QOpenGLTextureGlyphCache::fillTexture()
#16 0x7f9ca1fb6044 QTextureGlyphCache::fillInPendingGlyphs()
#17 0x7f9ca26e4328 <unknown>
#18 0x7f9ca26e2264 <unknown>
#19 0x7f9ca2765a47 <unknown>
#20 0x7f9ca276a6a4 <unknown>
#21 0x7f9ca276696c <unknown>
#22 0x7f9ca276542a QQuickText::updatePaintNode()
#23 0x7f9ca2724940 QQuickWindowPrivate::updateDirtyNode()
#24 0x7f9ca272515b QQuickWindowPrivate::updateDirtyNodes()
#25 0x7f9ca272619e QQuickWindowPrivate::syncSceneGraph()
#26 0x7f9ca26f428e <unknown>
#27 0x7f9ca26f5a18 <unknown>
#28 0x7f9ca1d08f65 QWindow::event()
#29 0x7f9ca272f9e3 QQuickWindow::event()
#30 0x7f9ca2acd8ac QApplicationPrivate::notify_helper()
#31 0x7f9ca2ad2d4f QApplication::notify()
#32 0x7f9ca15383c0 QCoreApplication::notifyInternal2()
#33 0x7f9ca1cfe29d QGuiApplicationPrivate::processExposeEvent()
#34 0x7f9ca1cfee7d QGuiApplicationPrivate::processWindowSystemEvent()
#35 0x7f9ca1cdcb2b QWindowSystemInterface::sendWindowSystemEvents()
#36 0x7f9c993e1660 <unknown>
#37 0x7f9ca0212837 g_main_context_dispatch
#38 0x7f9ca0212aa0 <unknown>
#39 0x7f9ca0212b4c g_main_context_iteration
#40 0x7f9ca158e49f QEventDispatcherGlib::processEvents()
#41 0x7f9ca153610a QEventLoop::exec()
#42 0x7f9ca153e91c QCoreApplication::exec()
#43 0x563c4a995935 (/usr/bin/webbrowser-app+0x563c4a995934)
#44 0x7f9ca096d3f1 __libc_start_main
#45 0x563c4a995a9a (/usr/bin/webbrowser-app+0x563c4a995a99)

Aborted (core dumped)

dinamic (dinamic6661) wrote :

on intel sandy bridge ubuntu 17.04 unity8 + proposed, the browser crashes :'(

dinamic (dinamic6661) wrote :

#3 @osomon yep glxgears works fine

summary: - Segmentation fault (core dumped) on 17.04
+ webbrowser app Segmentation fault (core dumped) on 17.04

Confirmed. webbrowser-app crashes immediately on start-up in zesty Unity7 with the same stack trace as comment #7.

I can't find the official crash report on errors.ubuntu.com though...

Changed in canonical-devices-system-image:
status: New → Confirmed
Changed in webbrowser-app (Ubuntu):
status: Incomplete → Confirmed
importance: Undecided → Critical
summary: - webbrowser app Segmentation fault (core dumped) on 17.04
+ webbrowser app Segmentation fault (core dumped) on 17.04 Unity7
dinamic (dinamic6661) wrote :

:'( i get this a lot "your computer does not have enough free memory to automatically analyze the problem and send a report to the developers" https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1649605

Olivier Tilloy (osomon) on 2017-01-27
tags: added: crash startup
Olivier Tilloy (osomon) on 2017-01-27
affects: webbrowser-app (Ubuntu) → oxide
Chris Coulson (chrisccoulson) wrote :

This is not a bug in Oxide - the CHECK failure in this case is a red herring and is a side effect of a bug elsewhere that triggers an unclean exit() (see bug 1663609)

affects: oxide → qtdeclarative-opensource-src (Ubuntu)
Simon Quigley (tsimonq2) wrote :

Is this still a bug?

Changed in qtdeclarative-opensource-src (Ubuntu):
status: Confirmed → Incomplete
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

Changed in canonical-devices-system-image:
status: Confirmed → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for qtdeclarative-opensource-src (Ubuntu) because there has been no activity for 60 days.]

Changed in qtdeclarative-opensource-src (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers