Bug#869503: Totem Player Segmentation Fault on Start Up (Debian 9)

[Aaron Valdes]

Thanks 

See below

On Mon, 24 Jul 2017 23:51:49 -0500 Jason Crain  wrote:
> On Mon, Jul 24, 2017 at 10:09:32AM -0400, Aaron Valdes wrote:
> > Thanks Jason for all your guidance.
> > 
> > Here is the backtrace run in the order you suggested.
> > 
> > This is just with bt in gdm.
> > 
> > See below.
> [snip backtrace]
> 
> Please install the following debug packages and create the backtrace
> again so it will include the missing symbols.
> 
> libcogl20-dbgsym
> libclutter-1.0-dbg
> 
> 

gdb totem
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from totem...done.
(gdb) run
Starting program: /usr/bin/totem 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xb16f8b40 (LWP 1922)]
[New Thread 0xb0ef7b40 (LWP 1923)]
[New Thread 0xb02ffb40 (LWP 1924)]
[New Thread 0xaf3e2b40 (LWP 1925)]
[New Thread 0xaea22b40 (LWP 1926)]
[New Thread 0xadeceb40 (LWP 1927)]
[New Thread 0x9d658b40 (LWP 1928)]
[New Thread 0x9b4f5b40 (LWP 1929)]
[New Thread 0x9acf4b40 (LWP 1930)]
[New Thread 0x95fa4b40 (LWP 1931)]
[New Thread 0x955ffb40 (LWP 1932)]

Thread 1 "totem" received signal SIGSEGV, Segmentation fault.
0x0001 in ?? ()
(gdb) bt
#0  0x0001 in  ()
#1  0xb6af6852 in _cogl_pipeline_flush_gl_state (ctx=, 
pipeline=, framebuffer=, 
with_color_attrib=, unknown_color_alpha=) at 
driver/gl/cogl-pipeline-opengl.c:1459
#2  0xb6af1c1e in _cogl_gl_flush_attributes_state (framebuffer=0x80605bd0, 
pipeline=0x8093c9b0, layers_state=0xbfffe864, 
flags=(COGL_DRAW_SKIP_JOURNAL_FLUSH | COGL_DRAW_SKIP_PIPELINE_VALIDATION | 
COGL_DRAW_SKIP_FRAMEBUFFER_FLUSH | COGL_DRAW_SKIP_LEGACY_STATE | 
COGL_DRAW_COLOR_ATTRIBUTE_IS_OPAQUE), attributes=0x8008c1d8, n_attributes=2) at 
driver/gl/cogl-attribute-gl.c:472
#3  0xb6b10303 in _cogl_flush_attributes_state (framebuffer=0x80605bd0, 
pipeline=0x8093c9b0, flags=(COGL_DRAW_SKIP_JOURNAL_FLUSH | 
COGL_DRAW_SKIP_PIPELINE_VALIDATION | COGL_DRAW_SKIP_FRAMEBUFFER_FLUSH | 
COGL_DRAW_SKIP_LEGACY_STATE | COGL_DRAW_COLOR_ATTRIBUTE_IS_OPAQUE), 
attributes=0x8008c1d8, n_attributes=2)
at cogl-attribute.c:669
#4  0xb6aef2e2 in _cogl_framebuffer_gl_draw_attributes (framebuffer=0x80605bd0, 
pipeline=0x8093c9b0, mode=7, first_vertex=0, n_vertices=4, 
attributes=0x8008c1d8, n_attributes=2, flags=(COGL_DRAW_SKIP_JOURNAL_FLUSH | 
COGL_DRAW_SKIP_PIPELINE_VALIDATION | COGL_DRAW_SKIP_FRAMEBUFFER_FLUSH | 
COGL_DRAW_SKIP_LEGACY_STATE | COGL_DRAW_COLOR_ATTRIBUTE_IS_OPAQUE)) at 
driver/gl/cogl-framebuffer-gl.c:1182
#5  0xb6b33f07 in _cogl_journal_flush_modelview_and_entries 
(batch_start=0x80473d80, batch_len=1, data=0xbfffeb64) at cogl-journal.c:314
#6  0xb6b335c4 in batch_and_call (entries=entries@entry=0x80473d80, 
n_entries=n_entries@entry=1, 
can_batch_callback=can_batch_callback@entry=0xb6b33f70  
to continue, or q  to quit---
_entry_pipelines>, batch_callback=0xb6b34490 
<_cogl_journal_flush_pipeline_and_entries>, data=0xbfffeb64) at 
cogl-journal.c:273
#7  0xb6b33ca1 in _cogl_journal_flush_texcoord_vbo_offsets_and_entries 
(batch_start=0x80473d80, batch_len=1, data=0xbfffeb64) at cogl-journal.c:565
#8  0xb6b335a7 in batch_and_call (entries=entries@entry=0x80473d80, 
n_entries=n_entries@entry=3, 
can_batch_callback=can_batch_callback@entry=0xb6b340f0 
, batch_callback=0xb6b33c00 
<_cogl_journal_flush_texcoord_vbo_offsets_and_entries>, data=0xbfffeb64) at 
cogl-journal.c:266
#9  0xb6b33926 in _cogl_journal_flush_vbo_offsets_and_entries 
(batch_start=0x80473d80, batch_len=3, data=) at 
cogl-journal.c:673
#10 0xb6b335c4 in batch_and_call (entries=, n_entries=3, 
can_batch_callback=, batch_callback=0xb6b337c0 
<_cogl_journal_flush_vbo_offsets_and_entries>, data=0xbfffeb64) at 
cogl-journal.c:273
#11 0xb6b335c4 in batch_and_call (entries=, n_entries=3, 
can_batch_callback=can_batch_callback@entry=0xb6b33640 
, batch_callback=0xb6b336f0 
<_cogl_journal_flush_clip_stacks_and_entries>, data=0xbfffeb64) at 
cogl-journal.c:273
#12 0xb6b35169 in _cogl_journal_flush (journal=0x80226150)
at cogl-journal.c:1400
#13 0xb6b365ee in _cogl_framebuffer_flush_journal (framebuffer=0x80605bd0)
at cogl-framebuffer.c:636
#14 0xb6b04cf2 in cogl_flush () at cogl.c:323
#15 0xb6b39fcc in cogl_onscreen_swap_buffers_with_damage (onscreen=0x80605bd0, 

Bug#869503: Totem Player Segmentation Fault on Start Up (Debian 9)

[Jason Crain]

On Mon, Jul 24, 2017 at 10:09:32AM -0400, Aaron Valdes wrote:
> Thanks Jason for all your guidance.
> 
> Here is the backtrace run in the order you suggested.
> 
> This is just with bt in gdm.
> 
> See below.
[snip backtrace]

Please install the following debug packages and create the backtrace
again so it will include the missing symbols.

libcogl20-dbgsym
libclutter-1.0-dbg

Bug#869503: Totem Player Segmentation Fault on Start Up (Debian 9)

[Aaron Valdes]

Thanks again Jason.
Here is the backtrace with...

thread apply all bt

see below


On Mon, 24 Jul 2017 08:50:15 -0500 Jason Crain  wrote:
> On Sun, Jul 23, 2017 at 08:43:47PM -0400, Aaron Valdes wrote:
> > gdb totem
> > GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
> > Copyright (C) 2016 Free Software Foundation, Inc.
> > License GPLv3+: GNU GPL version 3 or later
> > 
> > This is free software: you are free to change and redistribute it.
> > There is NO WARRANTY, to the extent permitted by law.  Type "show
> > copying"
> > and "show warranty" for details.
> > This GDB was configured as "i686-linux-gnu".
> > Type "show configuration" for configuration details.
> > For bug reporting instructions, please see:
> > .
> > Find the GDB manual and other documentation resources online at:
> > .
> > For help, type "help".
> > Type "apropos word" to search for commands related to "word"...
> > Reading symbols from totem...Reading symbols
> > from 
> > /usr/lib/debug/.build-id/76/c73577645ba60270eb0d6919647d36862f01c7.debug...done.
> > done.
> > (gdb) thread apply all bt
> > (gdb) run
> > Starting program: /usr/bin/totem 
> > [Thread debugging using libthread_db enabled]
> > Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
> > [New Thread 0xb16f1b40 (LWP 7133)]
> > [New Thread 0xb0ef0b40 (LWP 7134)]
> > [New Thread 0xb02ffb40 (LWP 7135)]
> > 
> > (totem:7129): Totem-WARNING **: Failed to register application: Timeout
> > was reached
> > [Thread 0xb02ffb40 (LWP 7135) exited]
> > [Thread 0xb0ef0b40 (LWP 7134) exited]
> > [Thread 0xb16f1b40 (LWP 7133) exited]
> > [Inferior 1 (process 7129) exited normally]
> 
> You've run totem inside of gdb correctly, but to get a good backtrace
> you'll need to first 'run' totem, get it to crash, and then do 'bt' or
> 'thread apply all bt'.  Only then will the backtrace say what totem was
> doing when it crashed.  Were you having trouble getting totem to crash
> while in the debugger?
> 
> 

(gdb) run
Starting program: /usr/bin/totem 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xb16f8b40 (LWP 1586)]
[New Thread 0xb0ef7b40 (LWP 1587)]
[New Thread 0xb02ffb40 (LWP 1588)]
[New Thread 0xaf3e2b40 (LWP 1589)]
[New Thread 0xaea22b40 (LWP 1590)]
[New Thread 0xadeceb40 (LWP 1591)]
[New Thread 0x9d6cdb40 (LWP 1592)]
[New Thread 0x9bf15b40 (LWP 1593)]
[New Thread 0x9b714b40 (LWP 1594)]
[New Thread 0x95f77b40 (LWP 1595)]
[New Thread 0x9576cb40 (LWP 1596)]

Thread 1 "totem" received signal SIGSEGV, Segmentation fault.
0x0001 in ?? ()
(gdb) thread apply all bt

Thread 12 (Thread 0x9576cb40 (LWP 1596)):
#0  0xb7fd9cd9 in __kernel_vsyscall ()
#1  0xb7180627 in syscall () at ../sysdeps/unix/sysv/linux/i386/syscall.S:29
#2  0xb7300bce in g_cond_wait (cond=0x8090f294, mutex=0x8090f28c) at 
././glib/gthread-posix.c:1395
#3  0xb625322b in gst_base_sink_wait_preroll () at 
/usr/lib/i386-linux-gnu/libgstbase-1.0.so.0
#4  0xb6253761 in gst_base_sink_do_preroll () at 
/usr/lib/i386-linux-gnu/libgstbase-1.0.so.0
#5  0xb6253f8e in  () at /usr/lib/i386-linux-gnu/libgstbase-1.0.so.0
#6  0xb62554c4 in  () at /usr/lib/i386-linux-gnu/libgstbase-1.0.so.0
#7  0xb6256d2c in  () at /usr/lib/i386-linux-gnu/libgstbase-1.0.so.0
#8  0xb6dac97c in  () at /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
#9  0xb6db4c84 in gst_pad_push () at 
/usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
#10 0xb6d9bfb4 in gst_proxy_pad_chain_default () at 
/usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
#11 0xb6dac97c in  () at /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
#12 0xb6db4c84 in gst_pad_push () at 
/usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
#13 0xb626152a in  () at /usr/lib/i386-linux-gnu/libgstbase-1.0.so.0
#14 0xb6dac97c in  () at /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
#15 0xb6db4c84 in gst_pad_push () at 
/usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
#16 0xb6d9bfb4 in gst_proxy_pad_chain_default () at 
/usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
#17 0xb6dac97c in  () at /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
#18 0xb6db4c84 in gst_pad_push () at 
/usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
#19 0xb6d9bfb4 in gst_proxy_pad_chain_default () at 
/usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
#20 0xb6dac97c in  () at /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
#21 0xb6db4c84 in gst_pad_push () at 
/usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
#22 0xb626152a in  () at /usr/lib/i386-linux-gnu/libgstbase-1.0.so.0
#23 0xb6dac97c in  () at /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
#24 0xb6db4c84 in gst_pad_push () at 
/usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
#25 0xb626152a in  () at /usr/lib/i386-linux-gnu/libgstbase-1.0.so.0
#26 0xb6dac97c in  () at /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
#27 0xb6db4c84 in gst_pad_push () at 

Bug#869503: Totem Player Segmentation Fault on Start Up (Debian 9)

[Aaron Valdes]

Thanks Jason for all your guidance.

Here is the backtrace run in the order you suggested.

This is just with bt in gdm.

See below.

On Mon, 24 Jul 2017 08:50:15 -0500 Jason Crain  wrote:
> On Sun, Jul 23, 2017 at 08:43:47PM -0400, Aaron Valdes wrote:
> > gdb totem
> > GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
> > Copyright (C) 2016 Free Software Foundation, Inc.
> > License GPLv3+: GNU GPL version 3 or later
> > 
> > This is free software: you are free to change and redistribute it.
> > There is NO WARRANTY, to the extent permitted by law.  Type "show
> > copying"
> > and "show warranty" for details.
> > This GDB was configured as "i686-linux-gnu".
> > Type "show configuration" for configuration details.
> > For bug reporting instructions, please see:
> > .
> > Find the GDB manual and other documentation resources online at:
> > .
> > For help, type "help".
> > Type "apropos word" to search for commands related to "word"...
> > Reading symbols from totem...Reading symbols
> > from 
> > /usr/lib/debug/.build-id/76/c73577645ba60270eb0d6919647d36862f01c7.debug...done.
> > done.
> > (gdb) thread apply all bt
> > (gdb) run
> > Starting program: /usr/bin/totem 
> > [Thread debugging using libthread_db enabled]
> > Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
> > [New Thread 0xb16f1b40 (LWP 7133)]
> > [New Thread 0xb0ef0b40 (LWP 7134)]
> > [New Thread 0xb02ffb40 (LWP 7135)]
> > 
> > (totem:7129): Totem-WARNING **: Failed to register application: Timeout
> > was reached
> > [Thread 0xb02ffb40 (LWP 7135) exited]
> > [Thread 0xb0ef0b40 (LWP 7134) exited]
> > [Thread 0xb16f1b40 (LWP 7133) exited]
> > [Inferior 1 (process 7129) exited normally]
> 
> You've run totem inside of gdb correctly, but to get a good backtrace
> you'll need to first 'run' totem, get it to crash, and then do 'bt' or
> 'thread apply all bt'.  Only then will the backtrace say what totem was
> doing when it crashed.  Were you having trouble getting totem to crash
> while ingdb totem
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from totem...done.
(gdb) run
Starting program: /usr/bin/totem 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xb16f8b40 (LWP 1430)]
[New Thread 0xb0ef7b40 (LWP 1431)]
[New Thread 0xb02ffb40 (LWP 1432)]
[New Thread 0xaf3e2b40 (LWP 1433)]
[New Thread 0xaea22b40 (LWP 1434)]
[New Thread 0xadeceb40 (LWP 1435)]
[New Thread 0x9d658b40 (LWP 1436)]
[New Thread 0x9b4f5b40 (LWP 1437)]
[New Thread 0x9acf4b40 (LWP 1438)]
[New Thread 0x95f37b40 (LWP 1439)]
[New Thread 0x95736b40 (LWP 1440)]

(totem:1425): Gtk-WARNING **: Drawing a gadget with negative dimensions. Did 
you forget to allocate a size? (node slider owner GtkScale)

Thread 1 "totem" received signal SIGSEGV, Segmentation fault.
0x0001 in ?? ()
(gdb) bt
#0  0x0001 in  ()
#1  0xb6af6852 in  () at /usr/lib/i386-linux-gnu/libcogl.so.20
#2  0xb6af1c1e in  () at /usr/lib/i386-linux-gnu/libcogl.so.20
#3  0xb6b10303 in  () at /usr/lib/i386-linux-gnu/libcogl.so.20
#4  0xb6aef2e2 in  () at /usr/lib/i386-linux-gnu/libcogl.so.20
#5  0xb6b33f07 in  () at /usr/lib/i386-linux-gnu/libcogl.so.20
#6  0xb6b335c4 in  () at /usr/lib/i386-linux-gnu/libcogl.so.20
#7  0xb6b33ca1 in  () at /usr/lib/i386-linux-gnu/libcogl.so.20
#8  0xb6b335a7 in  () at /usr/lib/i386-linux-gnu/libcogl.so.20
#9  0xb6b33926 in  () at /usr/lib/i386-linux-gnu/libcogl.so.20
#10 0xb6b335c4 in  () at /usr/lib/i386-linux-gnu/libcogl.so.20
#11 0xb6b335c4 in  () at /usr/lib/i386-linux-gnu/libcogl.so.20
#12 0xb6b35169 in  () at /usr/lib/i386-linux-gnu/libcogl.so.20
#13 0xb6b365ee in  () at /usr/lib/i386-linux-gnu/libcogl.so.20
#14 0xb6b04cf2 in cogl_flush () at /usr/lib/i386-linux-gnu/libcogl.so.20
#15 0xb6b39fcc in cogl_onscreen_swap_buffers_with_damage ()
at /usr/lib/i386-linux-gnu/libcogl.so.20
#16 0xb6bd8e5b in  () at /usr/lib/i386-linux-gnu/libclutter-1.0.so.0
#17 0xb6bdc593 in  () at /usr/lib/i386-linux-gnu/libclutter-1.0.so.0
#18 0xb6c4b3e7 in  () at /usr/lib/i386-linux-gnu/libclutter-1.0.so.0
#19 0xb6bdbc32 in  () at /usr/lib/i386-linux-gnu/libclutter-1.0.so.0
#23 

Bug#869503: Totem Player Segmentation Fault on Start Up (Debian 9)

[Jason Crain]

On Sun, Jul 23, 2017 at 08:43:47PM -0400, Aaron Valdes wrote:
> gdb totem
> GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
> Copyright (C) 2016 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> 
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show
> copying"
> and "show warranty" for details.
> This GDB was configured as "i686-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> .
> Find the GDB manual and other documentation resources online at:
> .
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from totem...Reading symbols
> from 
> /usr/lib/debug/.build-id/76/c73577645ba60270eb0d6919647d36862f01c7.debug...done.
> done.
> (gdb) thread apply all bt
> (gdb) run
> Starting program: /usr/bin/totem 
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
> [New Thread 0xb16f1b40 (LWP 7133)]
> [New Thread 0xb0ef0b40 (LWP 7134)]
> [New Thread 0xb02ffb40 (LWP 7135)]
> 
> (totem:7129): Totem-WARNING **: Failed to register application: Timeout
> was reached
> [Thread 0xb02ffb40 (LWP 7135) exited]
> [Thread 0xb0ef0b40 (LWP 7134) exited]
> [Thread 0xb16f1b40 (LWP 7133) exited]
> [Inferior 1 (process 7129) exited normally]

You've run totem inside of gdb correctly, but to get a good backtrace
you'll need to first 'run' totem, get it to crash, and then do 'bt' or
'thread apply all bt'.  Only then will the backtrace say what totem was
doing when it crashed.  Were you having trouble getting totem to crash
while in the debugger?

Bug#869503: Totem Player Segmentation Fault on Start Up (Debian 9)

[Aaron Valdes]

My previous backtrace, I thought it froze, so I CTRL-C gdm.

I have run it again here but did not CTRL-C it.

See below.


On Sun, 23 Jul 2017 15:12:26 -0500 Jason Crain  wrote:
> On Sun, Jul 23, 2017 at 02:55:48PM -0400, Aaron Valdes wrote:
> > The system that this is happening on is a Dell Latitude D505 laptop.  I
> > do thing the problem is system related because it works fine on other
> > machines.
> > 
> > I can post lspci and lshw if it would help.
> > 
> > (totem:3998): Gtk-WARNING **: Drawing a gadget with negative dimensions.
> > Did you forget to allocate a size? (node slider owner GtkScale)
> > Segmentation fault
> > 
> > This is happening when playing all file types.
> > 
> > What other log files can I check?
> 
> It would be helpful if you can provide a backtrace.
> https://wiki.debian.org/HowToGetABacktrace can help tell you how to
> enable debug repositories, install debug symbols, and get a backtrace.
> You'll need to install at least gdb, totem-dbgsym, libtotem0-dbgsym,
> totem-plugins-dbgsym, libgtk-3-0-dbgsym, libglib2.0-0-dbg, and possibly
> others depending on what symbols are missing from the backtrace.
> 
> 

gdb totem
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from totem...Reading symbols
from 
/usr/lib/debug/.build-id/76/c73577645ba60270eb0d6919647d36862f01c7.debug...done.
done.
(gdb) thread apply all bt
(gdb) run
Starting program: /usr/bin/totem 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xb16f1b40 (LWP 7133)]
[New Thread 0xb0ef0b40 (LWP 7134)]
[New Thread 0xb02ffb40 (LWP 7135)]

(totem:7129): Totem-WARNING **: Failed to register application: Timeout
was reached
[Thread 0xb02ffb40 (LWP 7135) exited]
[Thread 0xb0ef0b40 (LWP 7134) exited]
[Thread 0xb16f1b40 (LWP 7133) exited]
[Inferior 1 (process 7129) exited normally]

Bug#869503: Totem Player Segmentation Fault on Start Up (Debian 9)

[Aaron Valdes]

Thanks

I ran this time with more options.

See below

On Sun, 23 Jul 2017 15:12:26 -0500 Jason Crain  wrote:
> On Sun, Jul 23, 2017 at 02:55:48PM -0400, Aaron Valdes wrote:
> > The system that this is happening on is a Dell Latitude D505 laptop.  I
> > do thing the problem is system related because it works fine on other
> > machines.
> > 
> > I can post lspci and lshw if it would help.
> > 
> > (totem:3998): Gtk-WARNING **: Drawing a gadget with negative dimensions.
> > Did you forget to allocate a size? (node slider owner GtkScale)
> > Segmentation fault
> > 
> > This is happening when playing all file types.
> > 
> > What other log files can I check?
> 
> It would be helpful if you can provide a backtrace.
> https://wiki.debian.org/HowToGetABacktrace can help tell you how to
> enable debug repositories, install debug symbols, and get a backtrace.
> You'll need to install at least gdb, totem-dbgsym, libtotem0-dbgsym,
> totem-plugins-dbgsym, libgtk-3-0-dbgsym, libglib2.0-0-dbg, and possibly
> others depending on what symbols are missing from the backtrace.
> 
> 

gdb totem
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from totem...Reading symbols
from 
/usr/lib/debug/.build-id/76/c73577645ba60270eb0d6919647d36862f01c7.debug...done.
done.
(gdb) thread apply all bt
(gdb) run
Starting program: /usr/bin/totem 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xb16f1b40 (LWP 7048)]
[New Thread 0xb0ef0b40 (LWP 7049)]
[New Thread 0xb02ffb40 (LWP 7050)]
^C
Thread 1 "totem" received signal SIGINT, Interrupt.
0xb7fd9cd9 in __kernel_vsyscall ()
(gdb) bt
#0  0xb7fd9cd9 in __kernel_vsyscall ()
#1  0xb717ec5f in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0xb72cd180 in poll (__timeout=25000, __nfds=1, __fds=0x80470810)
at /usr/include/i386-linux-gnu/bits/poll2.h:46
#3  0xb72cd180 in g_poll (fds=0x80470810, nfds=1, timeout=25000)
at ././glib/gpoll.c:124
#4  0xb72bd71c in g_main_context_poll (priority=,
n_fds=1, fds=0x80470810, timeout=, context=0x802d4888)
at ././glib/gmain.c:4228
#5  0xb72bd71c in g_main_context_iterate (context=0x802d4888,
block=block@entry=1, dispatch=dispatch@entry=1, self=)
at ././glib/gmain.c:3924
#6  0xb72bdb39 in g_main_loop_run (loop=0x8003b588)
at ././glib/gmain.c:4125
#7  0xb74b8b39 in g_dbus_connection_send_message_with_reply_sync
(connection=0x80235050 [GDBusConnection], message=0x802be290
[GDBusMessage], flags=G_DBUS_SEND_MESSAGE_FLAGS_NONE, timeout_msec=-1,
out_serial=0x0, cancellable=0x0, error=0xbfffed48)
at ././gio/gdbusconnection.c:2151
#8  0xb74b8ec7 in g_dbus_connection_call_sync_internal
(connection=0x80235050 [GDBusConnection], bus_name=,
object_path=0x804710e0 "/org/gnome/Totem", interface_name=0xb752c985
"org.gtk.Actions", method_name=0xb752c9b3 "DescribeAll", parameters=0x0,
reply_type=0xb752c9bf, flags=G_DBUS_CALL_FLAGS_NONE, timeout_msec=-1,
fd_list=0x0, out_fd_list=0x0, cancellable=0x0, error=0xbfffee88)
at ././gio/gdbusconnection.c:5935
#9  0xb74bacc3 in g_dbus_connection_call_sync (connection=, bus_name=, object_path=,
interface_name=, method_name=,
parameters=, reply_type=, flags=, timeout_msec=, cancellable=,
error=0xbfffee88) at ././gio/gdbusconnection.c:6162
#10 0xb749f881 in g_dbus_action_group_sync (group=0x8046bbb8
[GDBusActionGroup], cancellable=0x0, error=0xbfffee88)
at ././gio/gdbusactiongroup.c:527
#11 0xb749b787 in g_application_impl_register (application=0x80019080
[TotemObject], appid=0x802aebc0 "org.gnome.Totem",
flags=G_APPLICATION_HANDLES_OPEN, exported_actions=0x80011928,
remote_actions=0x8001905c, cancellable=0x0, error=0xbfffee88)
at ././gio/gapplicationimpl-dbus.c:582
#12 0xb74983a0 in g_application_register (application=0x80019080
[TotemObject], cancellable=0x0, error=0xbfffee88)
at ././gio/gapplication.c:2033
#13 0xb7f539c5 in totem_object_app_handle_local_options
(application=0x80019080 [TotemObject], option---Type  to
continue, or q  to quit---
s=0x802f0e50) at totem-object.c:274
#14 0xb6324e3a in ffi_call_SYSV ()
at /usr/lib/i386-linux-gnu/libffi.so.6
#15 0xb6324aac in ffi_call () at /usr/lib/i386-linux-gnu/libffi.so.6
#16 0xb73b0830 in g_cclosure_marshal_generic_va (closure=0x800163f0,
return_value=0xb144, instance=, 

Bug#869503: Totem Player Segmentation Fault on Start Up (Debian 9)

[Aaron Valdes]

See below.


On Sun, 23 Jul 2017 15:12:26 -0500 Jason Crain  wrote:
> On Sun, Jul 23, 2017 at 02:55:48PM -0400, Aaron Valdes wrote:
> > The system that this is happening on is a Dell Latitude D505 laptop.  I
> > do thing the problem is system related because it works fine on other
> > machines.
> > 
> > I can post lspci and lshw if it would help.
> > 
> > (totem:3998): Gtk-WARNING **: Drawing a gadget with negative dimensions.
> > Did you forget to allocate a size? (node slider owner GtkScale)
> > Segmentation fault
> > 
> > This is happening when playing all file types.
> > 
> > What other log files can I check?
> 
> It would be helpful if you can provide a backtrace.
> https://wiki.debian.org/HowToGetABacktrace can help tell you how to
> enable debug repositories, install debug symbols, and get a backtrace.
> You'll need to install at least gdb, totem-dbgsym, libtotem0-dbgsym,
> totem-plugins-dbgsym, libgtk-3-0-dbgsym, libglib2.0-0-dbg, and possibly
> others depending on what symbols are missing from the backtrace.
> 
> 

gdb totem
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from totem...Reading symbols
from 
/usr/lib/debug/.build-id/76/c73577645ba60270eb0d6919647d36862f01c7.debug...done.
done.
(gdb) run
Starting program: /usr/bin/totem 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xb16f1b40 (LWP 6836)]
[New Thread 0xb0ef0b40 (LWP 6837)]
[New Thread 0xb02ffb40 (LWP 6838)]
[New Thread 0xaf3e2b40 (LWP 6839)]
[New Thread 0xaea23b40 (LWP 6840)]
[New Thread 0xaded3b40 (LWP 6841)]
[New Thread 0x9d6d2b40 (LWP 6842)]
[New Thread 0x9bf3ab40 (LWP 6843)]
[New Thread 0x9b739b40 (LWP 6844)]
[New Thread 0x95f77b40 (LWP 6845)]
[New Thread 0x95762b40 (LWP 6846)]

Thread 1 "totem" received signal SIGSEGV, Segmentation fault.
0x0001 in ?? ()

Bug#869503: Totem Player Segmentation Fault on Start Up (Debian 9)

[Jason Crain]

On Sun, Jul 23, 2017 at 02:55:48PM -0400, Aaron Valdes wrote:
> The system that this is happening on is a Dell Latitude D505 laptop.  I
> do thing the problem is system related because it works fine on other
> machines.
> 
> I can post lspci and lshw if it would help.
> 
> (totem:3998): Gtk-WARNING **: Drawing a gadget with negative dimensions.
> Did you forget to allocate a size? (node slider owner GtkScale)
> Segmentation fault
> 
> This is happening when playing all file types.
> 
> What other log files can I check?

It would be helpful if you can provide a backtrace.
https://wiki.debian.org/HowToGetABacktrace can help tell you how to
enable debug repositories, install debug symbols, and get a backtrace.
You'll need to install at least gdb, totem-dbgsym, libtotem0-dbgsym,
totem-plugins-dbgsym, libgtk-3-0-dbgsym, libglib2.0-0-dbg, and possibly
others depending on what symbols are missing from the backtrace.

Bug#869503: Totem Player Segmentation Fault on Start Up (Debian 9)

[Aaron Valdes]

Package: totem
Version: 3.22.1-1

The system that this is happening on is a Dell Latitude D505 laptop.  I
do thing the problem is system related because it works fine on other
machines.

I can post lspci and lshw if it would help.

(totem:3998): Gtk-WARNING **: Drawing a gadget with negative dimensions.
Did you forget to allocate a size? (node slider owner GtkScale)
Segmentation fault

This is happening when playing all file types.

What other log files can I check?