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 118128 - bug-buddy crash -- after 'metacity theme crash upon theme installation'
bug-buddy crash -- after 'metacity theme crash upon theme installation'
Status: RESOLVED DUPLICATE of bug 118028
Product: bug-buddy
Classification: Deprecated
Component: general
2.1.x(GNOME2.x)
Other other
: High critical
: ---
Assigned To: Bug-buddy Maintainers
Bug-buddy Maintainers
: 118170 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-07-25 00:29 UTC by tackill
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2



Description tackill 2003-07-23 16:27:23 UTC
Package: bug-buddy
Severity: critical
Version: GNOME2.2.0 2.2.102
os_details: Gnome.Org
Synopsis: metacity theme crash upon theme installation
Bugzilla-Product: bug-buddy
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)
Description:
Description of Problem:
Upon installation of a theme, Metacity crashes

Steps to reproduce the problem:
1. install theme from tarball or folder
2. 
3. 

Actual Results:
program crashes


Expected Results
see actual results:


How often does this happen?
everytime metacity tries to install a theme

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/bug-buddy'

(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)...[New Thread 16384 (LWP 11607)]
[New Thread 32769 (LWP 11608)]
[New Thread 16386 (LWP 11609)]
(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)...0x4090cf29 in wait4 () from
/lib/libc.so.6

Thread 1 (Thread 16384 (LWP 11607))

  • #0 wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    from /lib/libpthread.so.0
  • #3 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #4 __pthread_sighandler
    from /lib/libpthread.so.0
  • #5 <signal handler called>
  • #6 strlen
    from /lib/libc.so.6
  • #7 _IO_stdin_used
  • #8 md5_get_digest_from_file
  • #9 md5_get_digest_from_file
  • #10 md5_get_digest_from_file
  • #11 g_hash_table_foreach
    from /usr/lib/libglib-2.0.so.0
  • #12 load_bugzilla_xml
  • #13 main
  • #14 __libc_start_main
    from /lib/libc.so.6
  • #0 wait4
    from /lib/libc.so.6




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-07-23 12:27 -------

The original reporter (tackill@hushmail.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, bug-buddy-maint@bugzilla.gnome.org.

Comment 1 Elijah Newren 2003-07-25 19:54:17 UTC
The stack trace you've shown is for a bug-buddy crash.  Can you also
get a stack trace for the metacity crash (or does metacity itself
crash at all?)  I'm updating the summary because of this.  I was
pretty sure there was another bug that this was a duplicate of that
was reported a while ago, but I didn't find any, so I'll leave this
open and set all fields appropriately.
Comment 2 Elijah Newren 2003-07-25 19:54:40 UTC
*** Bug 118170 has been marked as a duplicate of this bug. ***
Comment 3 Fernando Herrera 2003-08-09 18:47:16 UTC

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