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 514405 - crash in Home Folder: I wanted to open a pictu...
crash in Home Folder: I wanted to open a pictu...
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-04 20:42 UTC by arne_bruesch
Modified: 2008-02-05 15:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description arne_bruesch 2008-02-04 20:42:18 UTC 
What were you doing when the application crashed?
I wanted to open a picture which was saved without any format as shown in the data-type options-dialogue of GIMP. When I tried to to "open with..." nautilus crashed.


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (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: Amaranth
Icon Theme: SphereCrystal

Memory status: size: 78532608 vsize: 78532608 resident: 27811840 share: 16138240 rss: 27811840 rss_rlim: 4294967295
CPU usage: start_time: 1202159720 rtime: 303 utime: 286 stime: 17 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6bd56c0 (LWP 3651)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 188092

Thread 1 (Thread 0xb6bd56c0 (LWP 3651))

  • #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 ---------------------
---------------------------------
kbuildsycoca running...
(gnome-panel:3652): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -35 and height 28
DCOP Cleaning up dead connections.
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
QObject::connect: Incompatible sender/receiver arguments
	StarManager::ratingsColorsChanged() --> ContextBrowser::ratingOrScoreOrLabelsChanged(const QString&)
Fenstermanager-Warnung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x180005f (Buddy-List)
Fenstermanager-Warnung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
STARTUP
(nautilus:3651): Eel-WARNING **: No extension, not implemented yet
--------------------------------------------------
Comment 1 Gianluca Borello 2008-02-05 15:34:26 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 ***