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 505347 - crash in Computer: J'ai voulu associer un f...
crash in Computer: J'ai voulu associer un f...
Status: RESOLVED DUPLICATE of bug 440988
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-12-24 03:40 UTC by rugobert.labonte
Modified: 2007-12-24 14:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description rugobert.labonte 2007-12-24 03:40:06 UTC 
Version: 2.18.3

What were you doing when the application crashed?
J'ai voulu associer un fichier mp3 pour le faire lire par banshee et en cliquant dessus avec le bouton droit de la souris j'ai eu un message d'erreur.

I tried to associate a mp3 file with Banshee and everyrime i click on the mouse's right button to go on properties i get an error message


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: Clearlooks
Icon Theme: Tangerine

Memory status: size: 87388160 vsize: 87388160 resident: 29310976 share: 14852096 rss: 29310976 rss_rlim: 4294967295
CPU usage: start_time: 1198467308 rtime: 252 utime: 230 stime: 22 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 0xb6e146b0 (LWP 7123)]
(no debugging symbols found)
0xb7652321 in waitpid () from /lib/libpthread.so.0

+ Trace 182866

Thread 1 (Thread 0xb6e146b0 (LWP 7123))

  • #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 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 ??
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 ??
  • #30 ??
  • #31 ??
  • #32 ??
  • #33 ??
  • #34 ??
  • #35 ??
  • #36 ??
  • #37 ??
  • #38 ??
  • #39 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 ??
  • #41 ??
  • #42 ??
  • #43 ??
  • #44 ??
  • #45 ??
  • #46 ??
  • #47 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #48 ??
  • #49 ??
  • #50 ??
  • #51 ??
  • #52 ??
  • #53 ??
  • #54 g_sequence_sort_changed_iter
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (2310 sec old) ---------------------
(evolution-2.10:5329): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution-2.10:5329): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution-2.10:5329): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution-2.10:5329): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution-2.10:5329): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution-2.10:5329): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution-2.10:5329): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2007-12-24 14:29:49 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 440988 ***