Bug 335537 – fileroller crashed on cp1250 characters in filename

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 335537 - fileroller crashed on cp1250 characters in filename


Summary:	fileroller crashed on cp1250 characters in filename


Status:	RESOLVED DUPLICATE of bug 323229

Product:	file-roller
Classification:	Applications
Component:	general
Version:	2.10.x
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	Paolo Bacchilega
QA Contact:	file-roller-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-03-22 16:15 UTC by Vladimir Mencl
Modified:	2006-03-22 21:40 UTC

See Also:
GNOME target:	---
GNOME version:	2.9/2.10

Description Vladimir Mencl 2006-03-22 16:15:49 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: fileroller crashed on cp1250 characters in filename
Bugzilla-Product: file-roller
Bugzilla-Component: general
Bugzilla-Version: 2.10.0
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
fileroller crashed when I chose to extract a file.
The zip file had unicode (east european) characters in its name.
The zip file contained a single file, its name had cp1250 characters
(supposedly for iacute) in it.
Fileroller could not decode it and displayed the file as having no
name.
When I chose to extract the file, fileroller crashed.

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)
`shared object read from target memory' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208379712 (LWP 17133)]
(no debugging symbols found)
0x0017f402 in __kernel_vsyscall ()

+ Trace 67139

Thread 1 (Thread -1208379712 (LWP 17133))

#0 __kernel_vsyscall
#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 created by bug-buddy at 2006-03-22 16:15 -------


Unknown version 2.10.0 in product file-roller.  Setting version to "2.10.x".

Comment 1 Sergej Kotliar 2006-03-22 21:40:58 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 323229 ***