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 421147 - crash in Open Folder: Laukiau kol atsitaisys
crash in Open Folder: Laukiau kol atsitaisys
Status: RESOLVED DUPLICATE of bug 364335
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-21 18:10 UTC by ednet_smile
Modified: 2007-03-21 18:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description ednet_smile 2007-03-21 18:10:59 UTC 
What were you doing when the application crashed?
Laukiau kol atsitaisys


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 181059584 vsize: 0 resident: 181059584 share: 0 rss: 54013952 rss_rlim: 0
CPU usage: start_time: 1174453526 rtime: 0 utime: 1040599 stime: 0 cutime:968423 cstime: 0 timeout: 72176 it_real_value: 0 frequency: 722185

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226410320 (LWP 4368)]
[New Thread -1360028768 (LWP 7856)]
[New Thread -1299338336 (LWP 5086)]
[New Thread -1290925152 (LWP 4938)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 120858

Thread 1 (Thread -1226410320 (LWP 4368))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 nautilus_clipboard_monitor_emit_changed
  • #5 nautilus_clipboard_monitor_emit_changed
  • #6 nautilus_directory_async_state_changed
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #0 __kernel_vsyscall 






Comment 1


Christian Kirbach





          2007-03-21 18:29:38 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 364335 ***