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 531444 - crash in Computer: Browsing mobile phone vi...
crash in Computer: Browsing mobile phone vi...
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-04 21:36 UTC by stevmillar
Modified: 2008-05-04 23:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description stevmillar 2008-05-04 21:36:45 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Browsing mobile phone via bluetooth. (obex://[00:12...)


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Fri Apr 18 23:08:22 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: GartoonRedux

Memory status: size: 428314624 vsize: 428314624 resident: 40828928 share: 23093248 rss: 40828928 rss_rlim: 18446744073709551615
CPU usage: start_time: 1209936487 rtime: 249 utime: 225 stime: 24 cutime:2 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x2b8cc6285b80 (LWP 4100)]
0x00002b8cbfdaaedf in waitpid () from /lib/libpthread.so.0

+ Trace 196868

Thread 1 (Thread 0x2b8cc6285b80 (LWP 4100))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 istr_hash
    at nautilus-directory-async.c line 170
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 dequeue_pending_idle_callback
    at nautilus-directory-async.c line 848
  • #8 directory_load_callback
    at nautilus-directory-async.c line 1035
  • #9 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 main
    at nautilus-main.c line 556
  • #15 __libc_start_main
    from /lib/libc.so.6
  • #16 _start
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (84 sec old) ---------------------
Nautilus-Share-Message: ------------------------------------------
Nautilus-Share-Message: spawn arg "net"
Nautilus-Share-Message: spawn arg "usershare"
Nautilus-Share-Message: spawn arg "info"
Nautilus-Share-Message: end of spawn args; SPAWNING
Nautilus-Share-Message: returned from spawn: SUCCESS: 
Nautilus-Share-Message: exit code 0
Nautilus-Share-Message: caller wants GKeyFile
Nautilus-Share-Message: success from calling net usershare and parsing its output
Nautilus-Share-Message: ------------------------------------------
Got Event! 33, -1
Got Event! 33, -1
Figyelmeztetés az ablakkezelőtől: last_user_time (3263898272) is greater than comparison timestamp (3050806852).  This most likely represents a buggy client sending inaccurate timestamps in message
Figyelmeztetés az ablakkezelőtől: 0x3e00081 (Synaptic c) appears to be one of the offending windows with a timestamp of 3263898272.  Working around...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-04 23:03:07 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 522534 ***