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 323229 - Scandin letters like ä å cause crash in file roller.
Scandin letters like ä å cause crash in file roller.
Status: RESOLVED DUPLICATE of bug 304671
Product: file-roller
Classification: Applications
Component: general
2.10.x
Other other
: Normal normal
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
: 335537 414531 448889 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-12-04 21:49 UTC by e0100347
Modified: 2007-07-29 00:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description e0100347 2005-12-04 21:49:24 UTC
Distribution: Fedora Core release 4 (Stentz)
Package: file-roller
Severity: normal
Version: GNOME2.10.0 2.10.0
Gnome-Distributor: Red Hat, Inc
Synopsis: Scandin letters like ä å  cause crash in file roller.
Bugzilla-Product: file-roller
Bugzilla-Component: general
Bugzilla-Version: 2.10.0
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/file-roller'

(no debugging symbols found)
Using host libthread_db library "/lib/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)
[Thread debugging using libthread_db enabled]
[New Thread -1209002304 (LWP 5200)]
(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)
0x00d39402 in ?? ()

Thread 1 (Thread -1209002304 (LWP 5200))

  • #0 ??
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_utf8_validate
    from /usr/lib/libglib-2.0.so.0
  • #5 window_set_statusbar_visibility
  • #6 g_cclosure_marshal_VOID__STRING
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #11 fr_archive_new
  • #12 g_cclosure_marshal_VOID__STRING
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #17 fr_command_message
  • #18 fr_command_unstuff_new
  • #19 fr_process_set_err_line_func
  • #20 fr_process_set_err_line_func
  • #21 g_main_context_wakeup
    from /usr/lib/libglib-2.0.so.0
  • #22 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #23 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #24 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #25 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 main




------- Bug moved to this database by unknown@gnome.bugs 2005-12-04 21:49 UTC -------


Unknown version 2.10.0 in product file-roller.  Setting version to "2.10.x".
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@gnome.bugs.
   Previous reporter was e0100347@puv.fi.

Comment 1 Teppo Turtiainen 2005-12-05 17:47:19 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 304671 ***
Comment 2 Sergej Kotliar 2006-03-22 21:40:58 UTC
*** Bug 335537 has been marked as a duplicate of this bug. ***
Comment 3 Susana 2007-03-04 13:11:20 UTC
*** Bug 414531 has been marked as a duplicate of this bug. ***
Comment 4 Susana 2007-03-18 00:31:49 UTC
*** Bug 419461 has been marked as a duplicate of this bug. ***
Comment 5 Pedro Villavicencio 2007-07-29 00:27:28 UTC
*** Bug 448889 has been marked as a duplicate of this bug. ***