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 359182 - crash in Theme: This is a followup to bu...
crash in Theme: This is a followup to bu...
Status: RESOLVED DUPLICATE of bug 352490
Product: gnome-control-center
Classification: Core
Component: [obsolete] theme-manager
2.16.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-03 01:59 UTC by Justin Chudgar
Modified: 2006-10-03 02:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Justin Chudgar 2006-10-03 01:59:00 UTC
Version: 2.16.1

What were you doing when the application crashed?
This is a followup to bug 352490.

I ran from gnome-terminal as requested:

	justin@justin01:~$ gnome-theme-manager
	
	** (bug-buddy:12650): WARNING **: Couldn't load icon for Decrypt File
	
	** (bug-buddy:12650): WARNING **: Couldn't load icon for Import Key
	
	** (bug-buddy:12650): WARNING **: Couldn't load icon for Open Folder
	
	** (bug-buddy:12650): WARNING **: Couldn't load icon for Verify Signature

That is the only output.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 50724864 vsize: 0 resident: 50724864 share: 0 rss: 15425536 rss_rlim: 0
CPU usage: start_time: 1159840311 rtime: 0 utime: 85 stime: 0 cutime:75 cstime: 0 timeout: 10 it_real_value: 0 frequency: 1

Backtrace was generated from '/usr/bin/gnome-theme-manager'

(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 -1225140560 (LWP 12199)]
[New Thread -1244210272 (LWP 12641)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225140560 (LWP 12199))

  • #0 __kernel_vsyscall
  • #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 *__GI___libc_free
    from /lib/tls/i686/cmov/libc.so.6
  • #5 g_free
    from /usr/lib/libglib-2.0.so.0
  • #6 gnome_theme_installer_run_cb
  • #7 g_cclosure_marshal_VOID__VOID
    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 file_transfer_dialog_wrap_async_xfer
  • #13 gnome_vfs_job_get_count
    from /usr/lib/libgnomevfs-2.so.0
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 g_slice_alloc
    from /usr/lib/libglib-2.0.so.0
  • #18 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #21 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #22 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 main
  • #0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-03 02:00:32 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 352490 ***
Comment 2 Elijah Newren 2006-10-03 02:04:27 UTC
Justin: Your responses are less likely to get lost if you just go to the bugzilla website and enter your comments there, rather than filing a new bug every time.  I'll add the info this time, but it's likely to be missed next time...
Comment 3 Karsten Bräckelmann 2006-10-03 02:05:55 UTC
Thanks for providing the requested terminal output, Justin. :)
Added a note to bug 352490.
Comment 4 Karsten Bräckelmann 2006-10-03 02:09:28 UTC
Eliah, *no* additional info is missed, while I am triaging bugs.
(If only I would have not been caught by tw mid-air collisions... ;)


*** This bug has been marked as a duplicate of 352490 ***
Comment 5 Elijah Newren 2006-10-03 02:15:30 UTC
Karsten: True, but assuming *you* will be the one to triage the bug (while not too bad an assumption right now) is not always going to be true.  ;)