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 409670 - crash in Trash: Change Themes
crash in Trash: Change Themes
Status: RESOLVED DUPLICATE of bug 356181
Product: gnome-applets
Classification: Other
Component: trash applet
unspecified
Other All
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
: 410124 411494 418432 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-02-19 17:12 UTC by nylon6_10
Modified: 2007-03-31 00:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description nylon6_10 2007-02-19 17:12:30 UTC
What were you doing when the application crashed?
Change Themes


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-1.2911.fc6 #1 SMP Sat Feb 10 15:51:47 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 57507840 vsize: 0 resident: 57507840 share: 0 rss: 9412608 rss_rlim: 0
CPU usage: start_time: 1171904698 rtime: 0 utime: 30 stime: 0 cutime:27 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/libexec/trashapplet'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208248624 (LWP 20744)]
(no debugging symbols found)
0x00f19402 in __kernel_vsyscall ()

Thread 1 (Thread -1208248624 (LWP 20744))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 gdk_x11_drawable_get_xdisplay
    from /usr/lib/libgdk-x11-2.0.so.0
  • #6 gdk_events_pending
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 gdk_events_pending
    from /usr/lib/libgdk-x11-2.0.so.0
  • #8 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #9 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #10 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #12 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #13 bonobo_generic_factory_main_timeout
    from /usr/lib/libbonobo-2.so.0
  • #14 bonobo_generic_factory_main
    from /usr/lib/libbonobo-2.so.0
  • #15 panel_applet_factory_main_closure
    from /usr/lib/libpanel-applet-2.so.0
  • #16 panel_applet_factory_main
    from /usr/lib/libpanel-applet-2.so.0
  • #17 g_cclosure_marshal_VOID__VOID
  • #18 __libc_start_main
    from /lib/libc.so.6
  • #19 g_cclosure_marshal_VOID__VOID
  • #0 __kernel_vsyscall

----------- .xsession-errors ---------------------
Failed to initialize Panel Agent!
Failed to initialize Panel Agent!
(pam-panel-icon:20951): Gtk-WARNING **: module_path にはテーマ・エンジンがありません: "rezlooks",
/home/sato/.themes/Rezlooks-Royale/gtk-2.0/gtkrc:186: error: invalid string constant "panel", expected valid string constant
** (bug-buddy:20957): WARNING **: フォルダを開く のアイコンを読み込めませんでした
(bug-buddy:20953): Gtk-WARNING **: module_path にはテーマ・エンジンがありません: "rezlooks",
/home/sato/.themes/Rezlooks-Royale/gtk-2.0/gtkrc:186: error: invalid string constant "panel", expected valid string constant
** (bug-buddy:20964): WARNING **: フォルダを開く のアイコンを読み込めませんでした
(gnome-theme-manager:20812): Gtk-WARNING **: module_path にはテーマ・エンジンがありません: "rezlooks",
/home/sato/.themes/Rezlooks-Royale/gtk-2.0/gtkrc:186: error: invalid string constant "panel", expected valid string constant
--------------------------------------------------
Comment 1 palfrey 2007-02-20 17:01:01 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!
Comment 2 Pedro Villavicencio 2007-02-20 22:48:48 UTC
*** Bug 410124 has been marked as a duplicate of this bug. ***
Comment 3 Susana 2007-02-24 20:32:01 UTC
*** Bug 411494 has been marked as a duplicate of this bug. ***
Comment 4 Pedro Villavicencio 2007-03-15 02:44:36 UTC
*** Bug 418432 has been marked as a duplicate of this bug. ***
Comment 5 André Klapper 2007-03-31 00:58:08 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 356181 ***