| 2018-03-23 09:51:09 |
dinamic |
bug |
|
|
added bug |
| 2018-03-23 09:58:25 |
Apport retracing service |
bug |
|
|
added subscriber Crash bug triagers for Ubuntu packages |
| 2018-03-23 09:58:27 |
Apport retracing service |
attachment added |
|
Stacktrace.txt https://bugs.launchpad.net/bugs/1758287/+attachment/5087918/+files/Stacktrace.txt |
|
| 2018-03-23 09:58:27 |
Apport retracing service |
attachment added |
|
StacktraceSource.txt https://bugs.launchpad.net/bugs/1758287/+attachment/5087919/+files/StacktraceSource.txt |
|
| 2018-03-23 09:58:28 |
Apport retracing service |
attachment added |
|
ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1758287/+attachment/5087920/+files/ThreadStacktrace.txt |
|
| 2018-03-23 09:58:29 |
Apport retracing service |
attachment removed |
CoreDump.gz https://bugs.launchpad.net/bugs/1758287/+attachment/5087904/+files/CoreDump.gz |
|
|
| 2018-03-23 09:58:30 |
Apport retracing service |
totem (Ubuntu): importance |
Undecided |
Medium |
|
| 2018-03-23 09:58:31 |
Apport retracing service |
tags |
amd64 apport-crash bionic need-amd64-retrace |
amd64 apport-crash bionic |
|
| 2018-03-26 02:11:45 |
Daniel van Vugt |
summary |
totem crashed with signal 5 |
totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent() |
|
| 2018-03-26 02:11:54 |
Daniel van Vugt |
information type |
Private |
Public |
|
| 2018-04-23 19:57:57 |
Launchpad Janitor |
totem (Ubuntu): status |
New |
Confirmed |
|
| 2018-04-23 21:11:09 |
Kai Kasurinen |
bug |
|
|
added subscriber Kai Kasurinen |
| 2018-04-24 01:26:46 |
Daniel van Vugt |
description |
totem crashed with signal 5
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
totem crashed with signal 5
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
| 2018-05-23 22:30:23 |
Apport retracing service |
tags |
amd64 apport-crash bionic |
amd64 apport-crash bionic cosmic |
|
| 2019-03-20 17:41:47 |
Apport retracing service |
tags |
amd64 apport-crash bionic cosmic |
amd64 apport-crash bionic cosmic disco |
|
| 2019-04-16 16:59:43 |
El jinete sin cabeza |
bug |
|
|
added subscriber El jinete sin cabeza |
| 2019-04-16 17:02:23 |
El jinete sin cabeza |
bug task added |
|
mesa (Ubuntu) |
|
| 2019-04-16 17:06:24 |
El jinete sin cabeza |
bug watch added |
|
https://bugs.freedesktop.org/show_bug.cgi?id=110452 |
|
| 2019-04-16 17:06:24 |
El jinete sin cabeza |
bug task added |
|
mesa |
|
| 2019-04-16 17:06:52 |
El jinete sin cabeza |
description |
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
totem crashed with signal 5
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
https://bugs.freedesktop.org/show_bug.cgi?id=110452
---
totem crashed with signal 5
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
| 2019-04-16 17:11:29 |
El jinete sin cabeza |
description |
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
https://bugs.freedesktop.org/show_bug.cgi?id=110452
---
totem crashed with signal 5
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
https://bugs.freedesktop.org/show_bug.cgi?id=110452
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
totem crashed with signal 5
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
| 2019-04-16 17:41:00 |
Bug Watch Updater |
mesa: status |
Unknown |
Confirmed |
|
| 2019-04-16 17:41:00 |
Bug Watch Updater |
mesa: importance |
Unknown |
Medium |
|
| 2019-04-17 11:59:35 |
El jinete sin cabeza |
mesa (Ubuntu): status |
New |
Invalid |
|
| 2019-04-17 11:59:49 |
El jinete sin cabeza |
description |
https://bugs.freedesktop.org/show_bug.cgi?id=110452
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
totem crashed with signal 5
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
totem crashed with signal 5
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
| 2019-04-17 12:01:02 |
El jinete sin cabeza |
description |
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
totem crashed with signal 5
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
Backtrace goes through:
totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX (MakeContextCurrent) -> Xlib (XError)
Ubuntu bug doesn't say anything about what's the use-case / when this happens and whether it's reproducible (is it e.g. timing related), it seems just some random crash that Apport collects.
In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell that it was given invalid/bad context. Corresponding Mesa code:
---------------------------
if (gc) {
/* Attempt to bind the context. We do this before mucking with
* gc and __glXSetCurrentContext to properly handle our state in
* case of an error.
*
* If an error occurs, set the Null context since we've already
* blown away our old context. The caller is responsible for
* figuring out how to handle setting a valid context.
*/
if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
__glXSetCurrentContextNull();
__glXUnlock();
__glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
False);
return GL_FALSE;
}
---------------------------
I.e. bug is in what is given to Mesa, not what Mesa does.
-> NOTOURBUG
To me it looks something that could happen when Totem is exiting, gst-vaapi is trying to use resources that have already been freed, and X catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects() ask libglvnd to do CommonMakeCurrent().
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
| 2019-04-17 12:02:32 |
El jinete sin cabeza |
bug task added |
|
gstreamer (Ubuntu) |
|
| 2019-04-17 12:02:39 |
El jinete sin cabeza |
bug task deleted |
gstreamer (Ubuntu) |
|
|
| 2019-04-17 12:03:02 |
El jinete sin cabeza |
bug task added |
|
gstreamer-vaapi (Ubuntu) |
|
| 2019-04-17 12:08:46 |
El jinete sin cabeza |
bug watch added |
|
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 |
|
| 2019-04-17 12:08:46 |
El jinete sin cabeza |
bug task added |
|
gstreamer |
|
| 2019-04-17 12:09:08 |
El jinete sin cabeza |
description |
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
Backtrace goes through:
totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX (MakeContextCurrent) -> Xlib (XError)
Ubuntu bug doesn't say anything about what's the use-case / when this happens and whether it's reproducible (is it e.g. timing related), it seems just some random crash that Apport collects.
In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell that it was given invalid/bad context. Corresponding Mesa code:
---------------------------
if (gc) {
/* Attempt to bind the context. We do this before mucking with
* gc and __glXSetCurrentContext to properly handle our state in
* case of an error.
*
* If an error occurs, set the Null context since we've already
* blown away our old context. The caller is responsible for
* figuring out how to handle setting a valid context.
*/
if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
__glXSetCurrentContextNull();
__glXUnlock();
__glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
False);
return GL_FALSE;
}
---------------------------
I.e. bug is in what is given to Mesa, not what Mesa does.
-> NOTOURBUG
To me it looks something that could happen when Totem is exiting, gst-vaapi is trying to use resources that have already been freed, and X catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects() ask libglvnd to do CommonMakeCurrent().
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
Backtrace goes through:
totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX (MakeContextCurrent) -> Xlib (XError)
Ubuntu bug doesn't say anything about what's the use-case / when this happens and whether it's reproducible (is it e.g. timing related), it seems just some random crash that Apport collects.
In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell that it was given invalid/bad context. Corresponding Mesa code:
---------------------------
if (gc) {
/* Attempt to bind the context. We do this before mucking with
* gc and __glXSetCurrentContext to properly handle our state in
* case of an error.
*
* If an error occurs, set the Null context since we've already
* blown away our old context. The caller is responsible for
* figuring out how to handle setting a valid context.
*/
if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
__glXSetCurrentContextNull();
__glXUnlock();
__glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
False);
return GL_FALSE;
}
---------------------------
I.e. bug is in what is given to Mesa, not what Mesa does.
-> NOTOURBUG
To me it looks something that could happen when Totem is exiting, gst-vaapi is trying to use resources that have already been freed, and X catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects() ask libglvnd to do CommonMakeCurrent().
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
| 2019-04-17 12:21:35 |
El jinete sin cabeza |
totem (Ubuntu): status |
Confirmed |
Invalid |
|
| 2019-04-17 13:08:32 |
Bug Watch Updater |
gstreamer: status |
Unknown |
New |
|
| 2019-04-17 13:49:53 |
El jinete sin cabeza |
bug task deleted |
mesa |
|
|
| 2019-04-17 17:49:37 |
El jinete sin cabeza |
bug watch added |
|
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 |
|
| 2019-04-17 17:50:59 |
El jinete sin cabeza |
description |
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
Backtrace goes through:
totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX (MakeContextCurrent) -> Xlib (XError)
Ubuntu bug doesn't say anything about what's the use-case / when this happens and whether it's reproducible (is it e.g. timing related), it seems just some random crash that Apport collects.
In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell that it was given invalid/bad context. Corresponding Mesa code:
---------------------------
if (gc) {
/* Attempt to bind the context. We do this before mucking with
* gc and __glXSetCurrentContext to properly handle our state in
* case of an error.
*
* If an error occurs, set the Null context since we've already
* blown away our old context. The caller is responsible for
* figuring out how to handle setting a valid context.
*/
if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
__glXSetCurrentContextNull();
__glXUnlock();
__glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
False);
return GL_FALSE;
}
---------------------------
I.e. bug is in what is given to Mesa, not what Mesa does.
-> NOTOURBUG
To me it looks something that could happen when Totem is exiting, gst-vaapi is trying to use resources that have already been freed, and X catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects() ask libglvnd to do CommonMakeCurrent().
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 (DUPLICATE OF https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 )
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
Backtrace goes through:
totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX (MakeContextCurrent) -> Xlib (XError)
Ubuntu bug doesn't say anything about what's the use-case / when this happens and whether it's reproducible (is it e.g. timing related), it seems just some random crash that Apport collects.
In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell that it was given invalid/bad context. Corresponding Mesa code:
---------------------------
if (gc) {
/* Attempt to bind the context. We do this before mucking with
* gc and __glXSetCurrentContext to properly handle our state in
* case of an error.
*
* If an error occurs, set the Null context since we've already
* blown away our old context. The caller is responsible for
* figuring out how to handle setting a valid context.
*/
if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
__glXSetCurrentContextNull();
__glXUnlock();
__glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
False);
return GL_FALSE;
}
---------------------------
I.e. bug is in what is given to Mesa, not what Mesa does.
-> NOTOURBUG
To me it looks something that could happen when Totem is exiting, gst-vaapi is trying to use resources that have already been freed, and X catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects() ask libglvnd to do CommonMakeCurrent().
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
| 2019-04-17 17:51:11 |
El jinete sin cabeza |
bug task deleted |
gstreamer |
|
|
| 2019-04-17 17:51:20 |
El jinete sin cabeza |
bug task added |
|
totem |
|
| 2019-04-17 17:53:28 |
El jinete sin cabeza |
description |
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 (DUPLICATE OF https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 )
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
Backtrace goes through:
totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX (MakeContextCurrent) -> Xlib (XError)
Ubuntu bug doesn't say anything about what's the use-case / when this happens and whether it's reproducible (is it e.g. timing related), it seems just some random crash that Apport collects.
In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell that it was given invalid/bad context. Corresponding Mesa code:
---------------------------
if (gc) {
/* Attempt to bind the context. We do this before mucking with
* gc and __glXSetCurrentContext to properly handle our state in
* case of an error.
*
* If an error occurs, set the Null context since we've already
* blown away our old context. The caller is responsible for
* figuring out how to handle setting a valid context.
*/
if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
__glXSetCurrentContextNull();
__glXUnlock();
__glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
False);
return GL_FALSE;
}
---------------------------
I.e. bug is in what is given to Mesa, not what Mesa does.
-> NOTOURBUG
To me it looks something that could happen when Totem is exiting, gst-vaapi is trying to use resources that have already been freed, and X catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects() ask libglvnd to do CommonMakeCurrent().
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 DUPLICATE OF:
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
Backtrace goes through:
totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX (MakeContextCurrent) -> Xlib (XError)
Ubuntu bug doesn't say anything about what's the use-case / when this happens and whether it's reproducible (is it e.g. timing related), it seems just some random crash that Apport collects.
In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell that it was given invalid/bad context. Corresponding Mesa code:
---------------------------
if (gc) {
/* Attempt to bind the context. We do this before mucking with
* gc and __glXSetCurrentContext to properly handle our state in
* case of an error.
*
* If an error occurs, set the Null context since we've already
* blown away our old context. The caller is responsible for
* figuring out how to handle setting a valid context.
*/
if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
__glXSetCurrentContextNull();
__glXUnlock();
__glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
False);
return GL_FALSE;
}
---------------------------
I.e. bug is in what is given to Mesa, not what Mesa does.
-> NOTOURBUG
To me it looks something that could happen when Totem is exiting, gst-vaapi is trying to use resources that have already been freed, and X catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects() ask libglvnd to do CommonMakeCurrent().
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
| 2019-04-17 18:53:02 |
El jinete sin cabeza |
affects |
totem |
gstreamer |
|
| 2019-04-17 22:29:28 |
Bug Watch Updater |
gstreamer: status |
Unknown |
Fix Released |
|
