Bug 397573 – crash in GNOME Commander: een zoekopdracht in alle...

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 397573 - crash in GNOME Commander: een zoekopdracht in alle...


Summary:	crash in GNOME Commander: een zoekopdracht in alle...


Status:	RESOLVED DUPLICATE of bug 356666

Product:	gnome-commander
Classification:	Other
Component:	application
Version:	1.2.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	1.2.4
Assigned To:	epiotr
QA Contact:	epiotr

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-01-17 10:18 UTC by pascal.wilikens
Modified:	2007-01-18 11:30 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description pascal.wilikens 2007-01-17 10:18:32 UTC

Version: 1.2.0

What were you doing when the application crashed?
een zoekopdracht in alle bestanden van mijn HDA


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

Memory status: size: 45047808 vsize: 0 resident: 45047808 share: 0 rss: 15990784 rss_rlim: 0
CPU usage: start_time: 1169029000 rtime: 0 utime: 286 stime: 0 cutime:214 cstime: 0 timeout: 72 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-commander'

(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 -1225693520 (LWP 25551)]
[New Thread -1239557216 (LWP 25566)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 102922

Thread 2 (Thread -1239557216 (LWP 25566))

#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_cairo_renderer_get_type
from /usr/lib/libpangocairo-1.0.so.0
#8 gdk_draw_layout_line
from /usr/lib/libgdk-x11-2.0.so.0
#9 pango_renderer_draw_glyphs
from /usr/lib/libpango-1.0.so.0
#10 pango_renderer_draw_layout_line
from /usr/lib/libpango-1.0.so.0
#11 pango_renderer_draw_layout
from /usr/lib/libpango-1.0.so.0
#12 gdk_draw_layout_with_colors
from /usr/lib/libgdk-x11-2.0.so.0
#13 gdk_draw_layout
from /usr/lib/libgdk-x11-2.0.so.0
#14 ??
#15 ??
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
from /usr/lib/libgobject-2.0.so.0
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??

Comment 1 André Klapper 2007-01-18 11:30:53 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 356666 ***