[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** Tags added: disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1758287 Title: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent() Status in totem package in Ubuntu: Confirmed Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1758287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** Tags added: cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1758287 Title: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent() Status in totem package in Ubuntu: Confirmed Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1758287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
https://bugs.freedesktop.org/show_bug.cgi?id=110452 ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Bug watch added: freedesktop.org Bugzilla #110452 https://bugs.freedesktop.org/show_bug.cgi?id=110452 ** Also affects: mesa via https://bugs.freedesktop.org/show_bug.cgi?id=110452 Importance: Unknown Status: Unknown ** Description changed: 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 ** Description changed: + https://bugs.freedesktop.org/show_bug.cgi?id=110452 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 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1758287 Title: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent() Status in Mesa: Confirmed Status in mesa package in Ubuntu: New Status in totem package in Ubuntu: Confirmed Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1758287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
Launchpad has imported 3 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=110452.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2019-04-16T17:06:03+00:00 El jinete sin cabeza wrote:
Open bug in launchpad.net
https://bugs.launchpad.net/bugs/1758287
"totem crashed with signal 5"
BackTrace:
#0 _g_log_abort (breakpoint=breakpoint@entry=1) at
../../../../glib/gmessages.c:583
debugger_present = 1
#1 0x7f07050f8571 in g_log_writer_default (log_level=6,
log_level@entry=G_LOG_LEVEL_ERROR, fields=fields@entry=0x7fff141276e0,
n_fields=n_fields@entry=6, user_data=user_data@entry=0x0) at
../../../../glib/gmessages.c:2735
__func__ = "g_log_writer_default"
#2 0x7f07050f67de in g_log_structured_array (log_level=G_LOG_LEVEL_ERROR,
fields=0x7fff141276e0, n_fields=6) at ../../../../glib/gmessages.c:1970
writer_func = 0x7f07050f8400
writer_user_data = 0x0
recursion = 0
depth =
n_fields = 6
log_level = G_LOG_LEVEL_ERROR
writer_user_data =
depth =
fields = 0x7fff141276e0
writer_func =
recursion =
_g_boolean_var_ =
writer_func =
writer_user_data =
recursion =
depth =
_g_boolean_var_ =
#3 0x7f07050f722e in g_log_structured_standard
(log_domain=log_domain@entry=0x7f070236b28e "Gdk",
log_level=log_level@entry=G_LOG_LEVEL_ERROR, file=file@entry=0x7f0702389a78
"../../../../../gdk/x11/gdkdisplay-x11.c", line=line@entry=0x7f07023894cf
"2766", func=func@entry=0x7f070238a190 <__func__.74387>
"_gdk_x11_display_error_event",
message_format=message_format@entry=0x7f070238a50b "%s") at
../../../../glib/gmessages.c:2027
fields = {{key = 0x7f0705142464 "PRIORITY", value = 0x7f07051422f9,
length = -1}, {key = 0x7f070514246d "CODE_FILE", value = 0x7f0702389a78, length
= -1}, {key = 0x7f0705142477 "CODE_LINE", value = 0x7f07023894cf, length = -1},
{key = 0x7f0705142481 "CODE_FUNC", value = 0x7f070238a190 <__func__.74387>,
length = -1}, {key = 0x7f0705142451 "MESSAGE", value = 0x56326c71ad30, length =
-1}, {key = 0x7f07051424be "GLIB_DOMAIN", value = 0x7f070236b28e, length = -1}}
n_fields =
message_allocated = 0x56326c71ad30 "The program 'totem' received an X
Window System error.\nThis probably reflects a bug in the program.\nThe error
was 'GLXBadContext'.\n (Details: serial 53257 error_code 169 request_code 155
(GLX) minor_"...
buffer = "vec2 UV)\n{\n
vec\377\377\377\377\000\000\000\000l_sample0\222\n\005\a\177\000\000\020\272\247\005\a\177\000\000\000XProtoError\000LIB",
'\000' , "\200?D", '\000' ,
"?\303\000\000\000\000(\345[\002\a\177\000\000\240\202;l2V\000\000\251\000\000\000\000\000\000\000`|\022\024\377\177\000\000\032\000\000\000\000\000\000\000\233\000\000\000\000\000\000\000\303>\211\005\a\177\000\000\005",
'\000' ,
"\060\222\n\005\a\177\000\000\060|\022\024\377\177\000\000"...
args = {{gp_offset = 48, fp_offset = 48, overflow_arg_area =
0x7fff14127c58, reg_save_area = 0x7fff14127b80}}
#4 0x7f070232de31 in _gdk_x11_display_error_event
(display=display@entry=0x56326c2e3110, error=error@entry=0x7fff14127d30) at
../../../../../gdk/x11/gdkdisplay-x11.c:2766
buf = "GLXBadContext", '\000'
msg =
display_x11 = 0x56326c2e3110
tmp_list =
ignore = 0
__func__ = "_gdk_x11_display_error_event"
#5 0x7f070233acb3 in gdk_x_error (xdisplay=0x56326c2d49e0,
error=0x7fff14127d30) at ../../../../../gdk/x11/gdkmain-x11.c:307
error_display = 0x56326c2e3110
manager =
displays = 0x0
error = 0x7fff14127d30
xdisplay = 0x56326c2d49e0
error_display =
manager =
displays =
gdk_display =
__inst =
__t =
__r =
#6 0x7f0704a0cc8d in _XError (dpy=dpy@entry=0x56326c2d49e0,
rep=rep@entry=0x7fff14127e20) at ../../src/XlibInt.c:1434
rtn_val =
event = {type = 0, xany = {type = 0, serial = 94774563260896,
send_event = 0, display = 0xd009, window = 1743785}, xkey = {type = 0, serial =
94774563260896, send_event = 0, display = 0xd009, window = 1743785, root =
8655628632, subwindow = 94774576511872, time = 3437855993206445056, x =
39845959, y = 0, x_root = 0, y_root = 0, state = 1815665024, keycode = 22066,
same_screen = 39845959}, xbutton = {type = 0, serial = 94774563260896,
send_event = 0, display = 0xd009, window = 1743785, root = 8655628632,
subwindow = 94774576511872, time = 3437855993206445056, x = 39845959, y = 0,
x_root = 0, y_root = 0, state = 1815665024, button = 22066, same_screen =
39845959}, xmotion = {type = 0, serial = 94774563260896, send_event =
[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** Changed in: mesa (Ubuntu)
Status: New => Invalid
** Description changed:
- https://bugs.freedesktop.org/show_bug.cgi?id=110452
+ 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
** Description changed:
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
- totem crashed with signal 5
+ 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
** Also affects: gstreamer (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: gstreamer (Ubuntu)
** Also affects: gstreamer-vaapi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
Status in GStreamer:
Unknown
Status in Mesa:
Confirmed
Status in gstreamer-vaapi package in Ubuntu:
New
Status in mesa package in Ubuntu:
Invalid
Status in totem package in Ubuntu:
Confirmed
Bu
[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues #153
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
** Also affects: gstreamer via
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
Importance: Unknown
Status: Unknown
** Description changed:
+ 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;
- }
+ 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().
+ 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
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
Status in GStreamer:
Unknown
Status in Mesa:
Confirmed
Status in gstreamer-vaapi package in Ubuntu:
New
Status in mesa package in Ubuntu:
Invalid
Status in totem package in Ubuntu:
Confirmed
Bug 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/c7d8b2eb8
[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** Changed in: totem (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
Status in GStreamer:
Unknown
Status in Mesa:
Confirmed
Status in gstreamer-vaapi package in Ubuntu:
New
Status in mesa package in Ubuntu:
Invalid
Status in totem package in Ubuntu:
Invalid
Bug 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1758287/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** Changed in: gstreamer
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
Status in GStreamer:
New
Status in Mesa:
Confirmed
Status in gstreamer-vaapi package in Ubuntu:
New
Status in mesa package in Ubuntu:
Invalid
Status in totem package in Ubuntu:
Invalid
Bug 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1758287/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** No longer affects: mesa
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
Status in GStreamer:
New
Status in gstreamer-vaapi package in Ubuntu:
New
Status in mesa package in Ubuntu:
Invalid
Status in totem package in Ubuntu:
Invalid
Bug 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1758287/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues #143
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
** Description changed:
- https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
+ 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
** No longer affects: gstreamer
** Also affects: totem via
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
Importance: Unknown
Status: Unknown
** Description changed:
- https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
(DUPLICATE OF
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 )
+ 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
[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** Project changed: totem => gstreamer
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
Status in GStreamer:
Unknown
Status in gstreamer-vaapi package in Ubuntu:
New
Status in mesa package in Ubuntu:
Invalid
Status in totem package in Ubuntu:
Invalid
Bug 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1758287/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** Changed in: gstreamer
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
Status in GStreamer:
Fix Released
Status in gstreamer-vaapi package in Ubuntu:
New
Status in mesa package in Ubuntu:
Invalid
Status in totem package in Ubuntu:
Invalid
Bug 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1758287/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** Summary changed: - totem crashed with signal 5 + totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent() ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1758287 Title: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent() Status in totem package in Ubuntu: New Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1758287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: totem (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1758287 Title: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent() Status in totem package in Ubuntu: Confirmed Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1758287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
Also tracking in: https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91 ** Description changed: + 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 + ?? () 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 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1758287 Title: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent() Status in totem package in Ubuntu: Confirmed Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1758287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
