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 126403 - .n7
.n7
Status: RESOLVED DUPLICATE of bug 116923
Product: metacity
Classification: Other
Component: general
2.4.x
Other other
: Normal critical
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2003-11-06 23:22 UTC by Jukka-Pekka Partanen
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jukka-Pekka Partanen 2003-11-06 23:22:51 UTC
Distribution: Gentoo 1.4
Package: metacity
Severity: critical
Version: GNOME2.4.0 2.4.x
Gnome-Distributor: Gentoo Linux
Synopsis: Metacity crashes when starting gmplayer
Bugzilla-Product: metacity
Bugzilla-Component: general
Bugzilla-Version: 2.4.x
Description of Problem:
When starting gmplayer, metacity crashes. Sometimes it
starts
automatically, but most of the time it doesn't and you
have to start it
manually.
Crash does not accur with mplayer, only with the
mplayer GUI gmplayer.
                                                      
                         
Steps to reproduce the crash:
1. start gmplayer (v0.92)
2.
3.
 
Expected Results:
metacity dies and sometimes get started automatically
again.
 
How often does this happen?
Always with gmplayer
 
Additional Information:
I don't know if this has anything to do with anything
but it seems that
the problem showed up after I recompiled mplayer with
3dnow and mmx
support.
 
 
 
Debugging Information:
 
Backtrace was generated from '/usr/bin/metacity'
 
(no debugging symbols found)...
Core was generated by `metacity --sm-save-file
1068156494-7535-2893618139.ms'.
Program terminated with signal 11, Segmentation fault.
(no debugging symbols found)...(no debugging symbols
found)...
(no debugging symbols found)...(no debugging symbols
found)...
(no debugging symbols found)...(no debugging symbols
found)...
(no debugging symbols found)...(no debugging symbols
found)...
(no debugging symbols found)...(no debugging symbols
found)...
(no debugging symbols found)...(no debugging symbols
found)...
(no debugging symbols found)...(no debugging symbols
found)...
(no debugging symbols found)...(no debugging symbols
found)...
(no debugging symbols found)...(no debugging symbols
found)...
(no debugging symbols found)...(no debugging symbols
found)...
(no debugging symbols found)...(no debugging symbols
found)...
(no debugging symbols found)...(no debugging symbols
found)...
(no debugging symbols found)...(no debugging symbols
found)...
(no debugging symbols found)...(no debugging symbols
found)...
(no debugging symbols found)...(no debugging symbols
found)...
(no debugging symbols found)...(no debugging symbols
found)...
(no debugging symbols found)...(no debugging symbols
found)...
(no debugging symbols found)...(no debugging symbols
found)...
(no debugging symbols found)...(no debugging symbols
found)...

Thread 1 (process 7704)

  • #0 g_type_check_instance_cast
    from /usr/lib/libgobject-2.0.so.0
  • #1 meta_gdk_pixbuf_get_from_pixmap
  • #2 meta_icon_cache_get_icon_invalidated
  • #3 meta_read_icons
  • #4 meta_window_get_icon_geometry
  • #5 meta_window_new
  • #6 meta_screen_manage_all_windows
  • #7 meta_display_open
  • #8 main
  • #9 __libc_start_main
    from /lib/libc.so.6
 

________________________________________________________________________
Want to chat instantly with your online friends?  Get the FREE Yahoo!
Messenger http://mail.messenger.yahoo.co.uk




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-11-06 18:22 -------

The original reporter (jukpart@yahoo.com) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, metacity-maint@bugzilla.gnome.org.

Comment 1 Rob Adams 2003-11-06 23:41:56 UTC

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