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 342016 - totem-xine nautilus integration crashes nautilus
totem-xine nautilus integration crashes nautilus
Status: RESOLVED DUPLICATE of bug 336051
Product: nautilus
Classification: Core
Component: [obsolete] Views: Other
2.14.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 347229 355649 357524 362037 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-05-16 18:26 UTC by Emmanuel Touzery
Modified: 2006-10-18 10:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Emmanuel Touzery 2006-05-16 18:26:47 UTC 
Steps to reproduce:
can't really reproduce it. was browsing a SMB share, clicking on properties of
files (to check their permissions), was in list view with several folders in one
window (listview with treeview). at one point nautilus just crashed.
i didn't realise it was connected to totem nautilus integration until i saw the
stack.

I was mostly browsing DV files in AVI type2 container.


Stack trace:
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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225873728 (LWP 4933)]
[New Thread -1233089616 (LWP 6156)]
[New Thread -1558041680 (LWP 6128)]
[New Thread -1549648976 (LWP 6127)]
[New Thread -1539368016 (LWP 6126)]
[New Thread -1530975312 (LWP 6125)]
[New Thread -1501004880 (LWP 6124)]
[New Thread -1515623504 (LWP 6123)]
[New Thread -1489761360 (LWP 6102)]
[New Thread -1481368656 (LWP 6101)]
[New Thread -1471087696 (LWP 6100)]
[New Thread -1462694992 (LWP 6099)]
[New Thread -1433416784 (LWP 6098)]
[New Thread -1448035408 (LWP 6097)]
[New Thread -1423533136 (LWP 6075)]
[New Thread -1415140432 (LWP 6074)]
[New Thread -1404859472 (LWP 6073)]
[New Thread -1396466768 (LWP 6072)]
[New Thread -1383834704 (LWP 6071)]
[New Thread -1375442000 (LWP 6070)]
[New Thread -1367049296 (LWP 6066)]
[New Thread -1358656592 (LWP 6065)]
[New Thread -1350263888 (LWP 6064)]
[New Thread -1341871184 (LWP 6063)]
[New Thread -1325085776 (LWP 6062)]
[New Thread -1333478480 (LWP 6061)]
[New Thread -1316693072 (LWP 6052)]
[New Thread -1308300368 (LWP 6051)]
[New Thread -1291514960 (LWP 6050)]
[New Thread -1283122256 (LWP 6049)]
[New Thread -1299907664 (LWP 6048)]
[New Thread -1254761552 (LWP 6047)]
[New Thread -1227326544 (LWP 4968)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 68261

Thread 1 (Thread -1225873728 (LWP 4933))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 fm_directory_view_pop_up_location_context_menu
  • #5 g_main_context_is_owner
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #9 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 POA_Nautilus_MetafileFactory__fini
  • #11 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #12 ??
  • #0 __kernel_vsyscall 


Other information:
Comment 1 Bastien Nocera 2006-05-16 18:33:29 UTC 
Actually, the crash was in the main thread, which nautilus owns, trying to popup a contextual menu:

+ Trace 68262

  • #3 <signal handler called>
  • #4 fm_directory_view_pop_up_location_context_menu
  • #5 g_main_context_is_owner
    from /usr/lib/libglib-2.0.so.0 






Comment 2


Fabio Bonelli





          2006-07-11 18:56:13 UTC
        



Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.







Comment 3


Fabio Bonelli





          2006-07-11 18:57:01 UTC
        



*** Bug 347229 has been marked as a duplicate of this bug. ***






Comment 4


Emmanuel Touzery





          2006-08-30 12:02:08 UTC
        



unfortunately, as i said, i can't reproduce the crash... so i won't be able to provide a better stack... sorry.






Comment 5


Christian Kirbach





          2006-09-13 08:57:13 UTC
        



*** Bug 355649 has been marked as a duplicate of this bug. ***






Comment 6


Christian Kirbach





          2006-09-13 08:58:20 UTC
        



Steps to reproduce:
1. Open Nautilus
2. Enter "ftp://ftp.gnome.org" in the location bar and hit enter
3. Select "Connect anonymously" and press the "Connect" button
4. Expand the "mirror" directory by pressing the arrow in front of it (not
double clicking it) so that you stay in the root directory of the FTP site.
5. Now double click the "mirror" directory to change directory.






Comment 7


Christian Kirbach





          2006-09-13 08:59:06 UTC
        



Can you get us one with debugging
symbols? Please see http://live.gnome.org/GettingTraces for more information on
how to do so.






Comment 8


Emmanuel Touzery





          2006-09-13 09:16:18 UTC
        



(In reply to comment #6)
> Steps to reproduce:
> 1. Open Nautilus
> 2. Enter "ftp://ftp.gnome.org" in the location bar and hit enter
> 3. Select "Connect anonymously" and press the "Connect" button
> 4. Expand the "mirror" directory by pressing the arrow in front of it (not
> double clicking it) so that you stay in the root directory of the FTP site.
> 5. Now double click the "mirror" directory to change directory.

"unfortunately" this doesn't crash for me on ubuntu dapper, nautilus 2.14.3.






Comment 9


Emmanuel Touzery





          2006-09-13 09:17:55 UTC
        



(In reply to comment #8)
> (In reply to comment #6)
> > Steps to reproduce:
> > 1. Open Nautilus
> > 2. Enter "ftp://ftp.gnome.org" in the location bar and hit enter
> > 3. Select "Connect anonymously" and press the "Connect" button
> > 4. Expand the "mirror" directory by pressing the arrow in front of it (not
> > double clicking it) so that you stay in the root directory of the FTP site.
> > 5. Now double click the "mirror" directory to change directory.
> 
> "unfortunately" this doesn't crash for me on ubuntu dapper, nautilus 2.14.3.
> 

OK, actually I got it now.. i'll install debug packages for my ubuntu and post backtraces ASAP.






Comment 10


Emmanuel Touzery





          2006-09-13 09:46:56 UTC
        



(In reply to comment #9)
> OK, actually I got it now.. i'll install debug packages for my ubuntu and post
> backtraces ASAP.

OK, here is what I got. setting up debug packages is a mess... i had to build from source from approximate descriptions... (nautilus-dbg from ubuntu repos didn't install, it was 2.14.1 vs my 2.14.3 and downgrading my nautilus only gave me a "broken" nautilus-dbg package) don't be surprised that people take time to do such things for now.


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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1225374016 (LWP 31909)]
[New Thread -1227084880 (LWP 31910)]
0xffffe410 in __kernel_vsyscall ()




+
Trace
    72250






Thread 1
          (Thread -1225374016 (LWP 31909))


    

  • 
#0
__kernel_vsyscall

    • 

  • 
#1
__waitpid_nocancel

    
                from
                /lib/tls/i686/cmov/libpthread.so.0

    

    • 

  • 
#2
libgnomeui_module_info_get

    
                from
                /usr/lib/libgnomeui-2.so.0

    

    • 

  • 
#3
<signal handler called>

    • 

  • 
#4
change_dummy_row_callback

    
                at fm-list-model.c
                  line
                  1693

    

    • 

  • 
#5
g_main_context_is_owner

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#6
g_main_context_dispatch

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#7
g_main_context_check

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#8
g_main_loop_run

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#9
gtk_main

    
                from
                /usr/lib/libgtk-x11-2.0.so.0

    

    • 

  • 
#10
main

    
                at nautilus-main.c
                  line
                  406

    

    • 

  • 
#0
__kernel_vsyscall

    • 













Comment 11


Christian Kirbach





          2006-09-13 11:32:26 UTC
        



last trace is different from the original trace.

I have opened a new report about it: Bug 355758

please post your traces as attachment (so that our duplicate finder does not get confused)

please try to reproduce the original crash again.






Comment 12


Sergej Kotliar





          2006-09-24 21:42:53 UTC
        



*** Bug 357524 has been marked as a duplicate of this bug. ***






Comment 13


Karsten Bräckelmann





          2006-10-13 22:14:13 UTC
        



*** Bug 362037 has been marked as a duplicate of this bug. ***






Comment 14


Alexander Larsson





          2006-10-18 10:51:44 UTC
        



Nah, the two traces are the same, they just look different due to not having debug info.


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