After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 454890 - Totem crash when is resized
Totem crash when is resized
Status: RESOLVED DUPLICATE of bug 355793
Product: totem
Classification: Core
Component: general
2.16.x
Other other
: High critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-07-08 16:33 UTC by androdebian
Modified: 2007-07-11 13:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description androdebian 2007-07-08 16:33:30 UTC
Distribution: Debian 4.0
Package: totem
Severity: Normal
Version: GNOME2.14.3 2.16.5
Gnome-Distributor: Debian
Synopsis: Totem crash when is resized
Bugzilla-Product: totem
Bugzilla-Component: general
Bugzilla-Version: 2.16.5
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
The program was crashed when i open a film and while i resized the
program window.

Steps to reproduce the crash:
1. Open a film with totem.
2. Resize the window while the program is loading.
3. The program crashed

Expected Results:


How often does this happen?
Since was crashed when was resize. now, the program crash all times.

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/totem'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224739136 (LWP 12022)]
[New Thread -1239254096 (LWP 12024)]
[New Thread -1228940368 (LWP 12023)]
(no debugging symbols found)
0xb7f1b792 in ?? () from /lib/ld-linux.so.2

Thread 1 (Thread -1224739136 (LWP 12022))

  • #0 ??
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 bacon_video_widget_get_backend_name
  • #5 bacon_video_widget_dvd_event
  • #6 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #12 gtk_widget_realize
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_widget_set_parent
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_box_pack_start
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_box_pack_start_defaults
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_box_pack_start_defaults
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 g_cclosure_marshal_VOID__OBJECT
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #23 gtk_container_add
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 totem_action_exit
  • #25 main
  • #0 ??
    from /lib/ld-linux.so.2




------- Bug created by bug-buddy at 2007-07-08 16:33 -------


Bugreport had an attachment. This cannot be imported to Bugzilla.
Contact bugmaster@gnome.org if you are willing to write a patch for this.
Unknown version 2.16.5 in product totem.  Setting version to "2.16.x".

Comment 1 Philip Withnall 2007-07-11 13:25:45 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 355793 ***