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 505539 - crash in CD/DVD Creator: Установил рисунок рабоче...
crash in CD/DVD Creator: Установил рисунок рабоче...
Status: RESOLVED DUPLICATE of bug 499229
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-12-25 10:38 UTC by radyus
Modified: 2007-12-26 01:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description radyus 2007-12-25 10:38:03 UTC
What were you doing when the application crashed?
Установил рисунок рабочего стола


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-15 (ASPLinux)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.8-34.1.0.120asp #1 SMP Mon Dec 10 12:55:55 EET 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 156139520 vsize: 156139520 resident: 39944192 share: 24313856 rss: 39944192 rss_rlim: 4294967295
CPU usage: start_time: 1198309407 rtime: 1762 utime: 1508 stime: 254 cutime:106 cstime: 17 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 -1208571072 (LWP 2718)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208571072 (LWP 2718))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __mktime_internal
    from /lib/libc.so.6
  • #5 timelocal
    from /lib/libc.so.6
  • #6 ??
    from /usr/lib/libgnome-desktop-2.so.2
  • #7 ??
    from /usr/lib/libgnome-desktop-2.so.2
  • #8 gnome_bg_changes_with_size
    from /usr/lib/libgnome-desktop-2.so.2
  • #9 ??
    from /usr/lib/libeel-2.so.2
  • #10 ??
    from /usr/lib/libeel-2.so.2
  • #11 ??
    from /usr/lib/libeel-2.so.2
  • #12 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #13 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #14 ??
    from /lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib/libeel-2.so.2
  • #18 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #19 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #20 ??
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #23 ??
    from /usr/lib/libgnome-desktop-2.so.2
  • #24 ??
    from /usr/lib/libeel-2.so.2
  • #25 ??
    from /usr/lib/libeel-2.so.2
  • #26 ??
  • #27 ??
  • #28 ??
    from /lib/libglib-2.0.so.0
  • #29 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #30 ??
    from /lib/libglib-2.0.so.0
  • #31 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #32 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
[NoScript] *** OVERLAY DISPOSE ***
[NoScript] *** OVERLAY INSTALL ***
[NoScript] *** OVERLAY DISPOSE ***
[NoScript] *** OVERLAY INSTALL ***
[NoScript] *** OVERLAY DISPOSE ***
warning: .dynamic section for "/usr/lib/libexif.so.12" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 Cosimo Cecchi 2007-12-26 01:13:49 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 499229 ***