webbrowser-app crashed with SIGABRT

Bug #1449231 reported by Christopher Townsend
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
oxide-qt (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

With fully updated Vivid system, I run into this crash when trying to start it in a Unity 8 desktop session.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: webbrowser-app 0.23+15.04.20150416-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
Date: Mon Apr 27 15:29:55 2015
ExecutablePath: /usr/bin/webbrowser-app
InstallationDate: Installed on 2013-03-18 (770 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
ProcCmdline: webbrowser-app
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=en_US
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: webbrowser-app
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
Title: webbrowser-app crashed with SIGABRT
UpgradeStatus: Upgraded to vivid on 2014-10-20 (189 days ago)
UserGroups: adm autopilot cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers

Revision history for this message
Christopher Townsend (townsend) wrote :
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in webbrowser-app (Ubuntu):
status: New → Confirmed
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 base::debug::BreakDebugger () at ../../../../third_party/chromium/src/base/debug/debugger_posix.cc:241
 logging::LogMessage::~LogMessage (this=0x7ffd29688030, __in_chrg=<optimized out>) at ../../../../third_party/chromium/src/base/logging.cc:639
 oxide::Compositor::DidFailToInitializeOutputSurface (this=0x7f9f58523210) at ../../../../shared/browser/compositor/oxide_compositor.cc:185
 cc::ThreadProxy::DidInitializeOutputSurface (this=0x7f9f58561100, success=<optimized out>, capabilities=...) at ../../../../third_party/chromium/src/cc/trees/thread_proxy.cc:253
 Run (this=0x7ffd296883f8) at ../../../../third_party/chromium/src/base/callback.h:396

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in webbrowser-app (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Olivier Tilloy (osomon)
affects: webbrowser-app (Ubuntu) → oxide-qt (Ubuntu)
Revision history for this message
Christopher Townsend (townsend) wrote :

This still occurs on the latest Unity 8 desktop session in Wily.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.