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 509025 - crash in Home Folder: Eigenschaften vom USB-St...
crash in Home Folder: Eigenschaften vom USB-St...
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-12 21:07 UTC by choeq-h
Modified: 2008-01-13 12:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description choeq-h 2008-01-12 21:07:22 UTC
What were you doing when the application crashed?
Eigenschaften vom USB-Stick geöffnet


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: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 81354752 vsize: 81354752 resident: 31408128 share: 15958016 rss: 31408128 rss_rlim: 4294967295
CPU usage: start_time: 1200168602 rtime: 49277 utime: 37093 stime: 12184 cutime:1168 cstime: 245 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 0xb6db26b0 (LWP 3053)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6db26b0 (LWP 3053))

  • #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 (24 sec old) ---------------------
/home/my/Desktop/tipp10: error while loading shared libraries: libpng.so.3: cannot open shared object file: No such file or directory
/home/my/Desktop/tipp10: error while loading shared libraries: libpng.so.3: cannot open shared object file: No such file or directory
/home/my/Desktop/tipp10: error while loading shared libraries: libpng.so.3: cannot open shared object file: No such file or directory
/home/my/Desktop/tipp10: error while loading shared libraries: libpng.so.3: cannot open shared object file: No such file or directory
/home/my/Desktop/tipp10: error while loading shared libraries: libpng.so.3: cannot open shared object file: No such file or directory
/home/my/Desktop/tipp10: error while loading shared libraries: libpng.so.3: cannot open shared object file: No such file or directory
/home/my/Desktop/tipp10: error while loading shared libraries: libpng.so.3: cannot open shared object file: No such file or directory
/home/my/Desktop/tipp10: error while loading shared libraries: libpng.so.3: cannot open shared object file: No such file or directory
/home/my/Desktop/tipp10: error while loading shared libraries: libpng.so.3: cannot open shared object file: No such file or directory
/home/my/Desktop/tipp10: error while loading shared libraries: libpng.so.3: cannot open shared object file: No such file or directory
Fenstermanager-Warnung:Ungültiges WM_TRANSIENT_FOR-Fenster 0x44 festgelegt für 0xe185e4 ().
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-13 12:12:58 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 ***