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 497112 - crash in Computer: guardat informació
crash in Computer: guardat informació
Status: RESOLVED DUPLICATE of bug 454799
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-15 17:04 UTC by silviapetiteta
Modified: 2007-11-16 13:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description silviapetiteta 2007-11-15 17:04:17 UTC
Version: 2.18.3

What were you doing when the application crashed?
guardat informació


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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 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: 101752832 vsize: 101752832 resident: 36556800 share: 24547328 rss: 36556800 rss_rlim: 4294967295
CPU usage: start_time: 1195146203 rtime: 116 utime: 106 stime: 10 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 -1208564000 (LWP 4095)]
[New Thread -1211044976 (LWP 4108)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1211044976 (LWP 4108))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strstr
    from /lib/libc.so.6
  • #5 ??
  • #6 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #7 ??
  • #8 ??
  • #9 ??


----------- .xsession-errors ---------------------
0x0751f2c3: 0x002fe638: /usr/lib/openoffice.org/program/libsfx680li.so + 0x1592c3
0x0752068b: 0x002fe638: /usr/lib/openoffice.org/program/libsfx680li.so + 0x15a68b
0x075a4b0f: 0x002fe638: /usr/lib/openoffice.org/program/libsfx680li.so + 0x1deb0f
0x075a5070: 0x002fe638: /usr/lib/openoffice.org/program/libsfx680li.so + 0x1df070 (SfxDispatcher::_Execute(SfxShell&, SfxSlot const&, SfxRequest&, unsigned short) + 0x150)
0x0759b3f9: 0x002fe638: /usr/lib/openoffice.org/program/libsfx680li.so + 0x1d53f9
0x075b9744: 0x002fe638: /usr/lib/openoffice.org/program/libsfx680li.so + 0x1f3744
0x075b9caf: 0x002fe638: /usr/lib/openoffice.org/program/libsfx680li.so + 0x1f3caf
0x02932c95: 0x001f67b0: /usr/lib/openoffice.org/program/libfwk680li.so + 0xcdc95
0x02932d4f: 0x001f67b0: /usr/lib/openoffice.org/program/libfwk680li.so + 0xcdd4f
0x06dedf56: 0x002f90dc: /usr/lib/openoffice.org/program/libvcl680li.so + 0x1d1f56 (Menu::Select() + 0x4c)
0x06decc1e: 0x002f90dc: /usr/lib/openoffice.org/program/libvcl680li.so + 0x1d0c1e
0x06e3f6f0: 0x002f90dc: /usr/lib/openoffice.org/program/libvcl680li.so + 0x2236f0
0x00e9b901: 0x00069a30: /usr/lib/openoffice.org/program/libvclplug_gen680li.so + 0x46901 (SalDisplay::DispatchInternalEvent() + 0x83)
0x00e16c23: 0x00041a50: /usr/lib/openoffice.org/program/libvclplug_gtk680li.so + 0x11c23
0x00e16c52: 0x00041a50: /usr/lib/openoffice.org/program/libvclplug_gtk680li.so + 0x11c52
0x0601ba91: 0x0009d29c: /l
--------------------------------------------------
Comment 1 palfrey 2007-11-16 13:41:12 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 454799 ***