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 394138 - crash in Computer: The more important quest...
crash in Computer: The more important quest...
Status: RESOLVED DUPLICATE of bug 360691
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-08 05:01 UTC by Yousef Reda
Modified: 2007-01-08 20:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Yousef Reda 2007-01-08 05:01:24 UTC 
What were you doing when the application crashed?
The more important question is... what program crashed? I can't answer your question unless I know what program crashed. I would have to say, then, I have no idea what I was doing when whatever program crashed crashed. Though I was using a KDE application in the GNOME environment, and earlier I had been tinkering with my GDM and KDM settings. So I wouldn't worry too much about this bug, I'd say it's more expected than anything.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 96509952 vsize: 0 resident: 96509952 share: 0 rss: 26316800 rss_rlim: 0
CPU usage: start_time: 1168230315 rtime: 0 utime: 443 stime: 0 cutime:360 cstime: 0 timeout: 83 it_real_value: 0 frequency: 0

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)
[Thread debugging using libthread_db enabled]
[New Thread -1227032912 (LWP 5214)]
[New Thread -1244304480 (LWP 6866)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 100363

Thread 2 (Thread -1244304480 (LWP 6866))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 cairo_restore
    from /usr/lib/libcairo.so.2
  • #5 pango_cairo_show_glyph_string
    from /usr/lib/libpangocairo-1.0.so.0
  • #6 pango_renderer_draw_glyphs
    from /usr/lib/libpango-1.0.so.0
  • #7 pango_renderer_draw_layout_line
    from /usr/lib/libpango-1.0.so.0
  • #8 pango_renderer_draw_layout
    from /usr/lib/libpango-1.0.so.0
  • #9 pango_cairo_show_error_underline
    from /usr/lib/libpangocairo-1.0.so.0
  • #10 rsvg_error_get_type
    from /usr/lib/librsvg-2.so.2
  • #11 rsvg_handle_new_from_data
    from /usr/lib/librsvg-2.so.2
  • #12 rsvg_handle_new_from_data
    from /usr/lib/librsvg-2.so.2
  • #13 rsvg_handle_new_from_data
    from /usr/lib/librsvg-2.so.2
  • #14 rsvg_handle_new_from_data
    from /usr/lib/librsvg-2.so.2
  • #15 rsvg_handle_new_from_data
    from /usr/lib/librsvg-2.so.2
  • #16 rsvg_handle_new_from_data
    from /usr/lib/librsvg-2.so.2
  • #17 rsvg_handle_new_from_data
    from /usr/lib/librsvg-2.so.2
  • #18 rsvg_handle_new_from_data
    from /usr/lib/librsvg-2.so.2
  • #19 rsvg_handle_new_from_data
    from /usr/lib/librsvg-2.so.2
  • #20 rsvg_handle_render_cairo_sub
    from /usr/lib/librsvg-2.so.2
  • #21 rsvg_handle_get_pixbuf_sub
    from /usr/lib/librsvg-2.so.2
  • #22 rsvg_handle_get_pixbuf
    from /usr/lib/librsvg-2.so.2
  • #23 fill_info
    from /usr/lib/gtk-2.0/2.10.0/loaders/svg_loader.so
  • #24 ??
  • #25 ?? 






Comment 1


Yousef Reda





          2007-01-08 05:05:12 UTC
        



Sorry, me again, heh.

Apparently it was Nautilus that crashed - it didn't close until after the bug report was submitted.

I had just downloaded a file using KFTPGrabber and went to go see it in my home folder. Typed in "i" to jump to its position and it crashed.

Perhaps with the file preview tool or something?






Comment 2


Pedro de Medeiros





          2007-01-08 20:58:13 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 360691 ***