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 510544 - crash in File Browser: po nacisnieci własciwosc...
crash in File Browser: po nacisnieci własciwosc...
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-19 04:09 UTC by jukmasz
Modified: 2008-01-20 12:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description jukmasz 2008-01-19 04:09:43 UTC 
Version: 2.18.3

What were you doing when the application crashed?
po nacisnieci własciwosci wyskoczyl ten komunikat


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SmoothCat
Icon Theme: OsX_MoD

Memory status: size: 78102528 vsize: 78102528 resident: 26820608 share: 16076800 rss: 26820608 rss_rlim: 4294967295
CPU usage: start_time: 1200715659 rtime: 120 utime: 113 stime: 7 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6dea6b0 (LWP 4091)]
[New Thread 0xb4cb2b90 (LWP 4109)]
[New Thread 0xb64b5b90 (LWP 4108)]
[New Thread 0xb54b3b90 (LWP 4107)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 185916

Thread 1 (Thread 0xb6dea6b0 (LWP 4091))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 strcmp
    from /lib/i686/cmov/libc.so.6
  • #7 ??
  • #8 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 81dff80
** Message: volume = 0
** Message: drive = 81dff30
** Message: volume = 0
** Message: drive = 81dfac0
** Message: volume = 81e4c60
** Message: drive = 81dfa70
** Message: volume = 0
/home/jarek/.themes/SmoothCat/gtk-2.0/iconrc:13: Nie można odnaleźć pliku z obrazem na ścieżce: "stock_apply.png"
/home/jarek/.themes/SmoothCat/gtk-2.0/iconrc:15: Nie można odnaleźć pliku z obrazem na ścieżce: "stock_ok.png"
/home/jarek/.themes/SmoothCat/gtk-2.0/iconrc:16: Nie można odnaleźć pliku z obrazem na ścieżce: "stock_apply.png"
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-20 12:03:08 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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