Bug 472511 – crash in Home Folder: change the wallpaper

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 472511 - crash in Home Folder: change the wallpaper


Summary:	crash in Home Folder: change the wallpaper


Status:	RESOLVED DUPLICATE of bug 439593

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-09-01 12:20 UTC by lqch.wy
Modified:	2007-10-19 23:27 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description lqch.wy 2007-09-01 12:20:44 UTC

What were you doing when the application crashed?
change the wallpaper


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 113401856 vsize: 113401856 resident: 24973312 share: 17604608 rss: 24973312 rss_rlim: 4294967295
CPU usage: start_time: 1188647035 rtime: 313 utime: 279 stime: 34 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(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 -1208714720 (LWP 2884)]
0x00110402 in __kernel_vsyscall ()

+ Trace 159601

Thread 1 (Thread -1208714720 (LWP 2884))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 g_cclosure_marshal_VOID__ENUM
at gmarshal.c line 334
#3 <signal handler called>
#4 ??
from /usr/lib/libgnome-desktop-2.so.2
#5 gnome_bg_changes_with_size
from /usr/lib/libgnome-desktop-2.so.2
#6 ??
from /usr/lib/libeel-2.so.2
#7 ??
from /usr/lib/libeel-2.so.2
#8 ??
from /usr/lib/libeel-2.so.2
#9 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#10 IA__g_closure_invoke
at gclosure.c line 490
#11 signal_emit_unlocked_R
at gsignal.c line 2440
#12 IA__g_signal_emit_valist
at gsignal.c line 2199
#13 IA__g_signal_emit
at gsignal.c line 2243
#14 ??
from /usr/lib/libeel-2.so.2
#15 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#16 IA__g_closure_invoke
at gclosure.c line 490
#17 signal_emit_unlocked_R
at gsignal.c line 2440
#18 IA__g_signal_emit_valist
at gsignal.c line 2199
#19 IA__g_signal_emit
at gsignal.c line 2243
#20 ??
from /usr/lib/libgnome-desktop-2.so.2
#21 ??
from /usr/lib/libeel-2.so.2
#22 ??
from /usr/lib/libeel-2.so.2
#23 ??
#24 ??
#25 g_timeout_dispatch
at gmain.c line 3422
#26 IA__g_main_context_dispatch
at gmain.c line 2045
#27 g_main_context_iterate
at gmain.c line 2677
#28 IA__g_main_loop_run
at gmain.c line 2881
#29 IA__gtk_main
at gtkmain.c line 1154
#30 main
#0 __kernel_vsyscall



----------- .xsession-errors (45 sec old) ---------------------
    func(*targs, **kargs)
  File "/usr/lib/python2.5/threading.py", line 652, in __exitfunc
    t.join()
  File "/usr/lib/python2.5/threading.py", line 550, in join
    assert self is not currentThread(), "cannot join current thread"
AssertionError: cannot join current thread
Error in sys.exitfunc:
Traceback (most recent call last):
  File "/usr/lib/python2.5/atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "/usr/lib/python2.5/threading.py", line 652, in __exitfunc
    t.join()
  File "/usr/lib/python2.5/threading.py", line 550, in join
    assert self is not currentThread(), "cannot join current thread"
AssertionError: cannot join current thread
--------------------------------------------------

Comment 1 André Klapper 2007-10-19 23:27:36 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 439593 ***