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 536415 - crash in Home Folder: Browsing my mobile phone...
crash in Home Folder: Browsing my mobile phone...
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-03 12:11 UTC by debian
Modified: 2008-06-03 12:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Attachments
Backtrace-536415.txt (7.71 KB, text/plain)
2008-06-03 12:39 UTC, debian
Details

Description debian 2008-06-03 12:11:59 UTC
What were you doing when the application crashed?
Browsing my mobile phone (K800i) via Obex and bluetooth.


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 Sat May 10 09:28:10 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: CleanestBrushedGnome
Icon Theme: Snow-Apple

Memory status: size: 535375872 vsize: 535375872 resident: 54112256 share: 20533248 rss: 54112256 rss_rlim: 18446744073709551615
CPU usage: start_time: 1212476938 rtime: 3310 utime: 2744 stime: 566 cutime:389 cstime: 80 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 0x2b48e18b9240 (LWP 4475)]
[New Thread 0x41802950 (LWP 17562)]
(no debugging symbols found)
0x00002b48dadafedf in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2b48e18b9240 (LWP 4475))

  • #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 ??
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 ??
  • #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 ??
  • #15 __libc_start_main
    from /lib/libc.so.6
  • #16 ??
  • #17 ??
  • #18 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (951 sec old) ---------------------
Docking to right or left
Docking to right or left
Docking to right or left
Docking to right or left
Docking to right or left
Docking to right or left
Docking to right or left
Docking to right or left
Docking to right or left
Docking to right or left
Docking to right or left
Docking to right or left
Docking to right or left
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 A. Walton 2008-06-03 12:15:55 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 debian 2008-06-03 12:38:02 UTC
Ok, here we go again with some more details :-)
I can reproduce the crash by choosing a certain folder on my mobile:

obex://[XX:XX:XX:XX:XX:XX]/Memory%20Stick/System/ams

other folders (parallel to that ams folder, or somewhere else on that phone) are working fine.

Backtrace attached as text file.
Comment 3 debian 2008-06-03 12:39:05 UTC
Created attachment 112054 [details]
Backtrace-536415.txt

Backtrace with debugging symbols
Comment 4 Cosimo Cecchi 2008-06-03 12:46:10 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 ***