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 536242 - crash in Computer: I just tried to open a m...
crash in Computer: I just tried to open a m...
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-02 13:58 UTC by Rémi Letot
Modified: 2008-06-03 13:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Rémi Letot 2008-06-02 13:58:36 UTC
Version: 2.20.0

What were you doing when the application crashed?
I just tried to open a memo file created on my palm (simple text file once synced on the computer). Nautilus doesn't seem to recognize the file type because there is no default action specified, and when I try to specify the application myself, nautilus crashes.

Note that I just tried experimenting with memo syncing, so I don't know if that problem will ressurface regularly, but another memo file I just created poses no problem.

I can send the problematic file if needed, and/or install nautilus with debugging symbols. Just tell me what is most usefull, I'm not a developper.


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-686 #1 SMP Tue May 27 15:38:35 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 79802368 vsize: 79802368 resident: 26427392 share: 16433152 rss: 26427392 rss_rlim: 4294967295
CPU usage: start_time: 1212414695 rtime: 205 utime: 191 stime: 14 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b40720 (LWP 15985)]
(no debugging symbols found)
0xb7ef1424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6b40720 (LWP 15985))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 strcmp
    from /lib/i686/cmov/libc.so.6
  • #7 g_str_equal
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
    from /usr/lib/libeel-2-2.20.so
  • #9 ??
  • #10 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
seahorse nautilus module initialized
(nautilus:15598): Eel-WARNING **: No extension, not implemented yet
Initializing nautilus-open-terminal extension
Initializing gnome-mount extension
seahorse nautilus module initialized
(nautilus:15634): Eel-WARNING **: No extension, not implemented yet
(nautilus:15634): Eel-WARNING **: No extension, not implemented yet
Initializing nautilus-open-terminal extension
Initializing gnome-mount extension
seahorse nautilus module initialized
(nautilus:15985): Eel-WARNING **: No extension, not implemented yet
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-02 19:06:34 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 355018 ***
Comment 2 Rémi Letot 2008-06-03 13:48:03 UTC
Hello,

I can indeed reproduce bug 355018 in my nautilus by following the detailed steps given by the OP. 

But for my particular case, I have no permission problem. I also moved the problematic file to my home directory, where obviously I have full permissions, I even gave full permissions to everyone on that file, and it still crashes nautilus when I try to open it.

I won't reopen the bug report as you know more than me about what the original bug report was about, but can you confirm that this is the same bug ?

Thanks,
-- 
Rémi