webbrowser-app crashed with SIGSEGV

Bug #1341284 reported by Vyacheslav Sedov
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
webbrowser-app (Ubuntu)
New
Medium
Unassigned

Bug Description

maybe this can help

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: webbrowser-app 0.23+14.10.20140709-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4
Uname: Linux 3.16.0-3-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jul 13 16:37:26 2014
ExecutablePath: /usr/bin/webbrowser-app
InstallationDate: Installed on 2014-06-30 (12 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
ProcCmdline: webbrowser-app
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=ru
 XDG_RUNTIME_DIR=<set>
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f17b049b3a4: mov 0x8(%r13),%ecx
 PC (0x7f17b049b3a4) ok
 source "0x8(%r13)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: webbrowser-app
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
Title: webbrowser-app crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Vyacheslav Sedov (schematronic) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 pushbuf_kref (push=push@entry=0x7f17d21e21f0, bo=0x0, flags=0) at ../../nouveau/pushbuf.c:151
 pushbuf_validate (push=0x7f17d21e21f0, retry=<optimized out>) at ../../nouveau/pushbuf.c:503
 nouveau_pushbuf_validate (push=push@entry=0x7f17d21e21f0) at ../../nouveau/pushbuf.c:749
 nvc0_m2mf_push_linear (nv=0x7f17d263a780, dst=0x7f17d268eb20, offset=768, domain=<optimized out>, size=76, data=0x7f17d26b2840) at ../../../../../../src/gallium/drivers/nouveau/nvc0/nvc0_transfer.c:188
 nouveau_transfer_write (nv=nv@entry=0x7f17d263a780, tx=tx@entry=0x7f17d2c29190, offset=offset@entry=0, size=76) at ../../../../../../src/gallium/drivers/nouveau/nouveau_buffer.c:218

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
information type: Private → Public
Revision history for this message
Phillip Sz (phillip-sz) wrote :

related to lp:1241813 ?

Revision history for this message
Olivier Tilloy (osomon) wrote :

No, this is a completely different stacktrace.

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.