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 483119 - crash in Archive Manager: 그놈 압축관리자로 압축파일을 풀때, 목적위치...
crash in Archive Manager: 그놈 압축관리자로 압축파일을 풀때, 목적위치...
Status: RESOLVED DUPLICATE of bug 357188
Product: file-roller
Classification: Applications
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2007-10-03 21:37 UTC by harusame
Modified: 2007-10-29 22:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description harusame 2007-10-03 21:37:44 UTC 
Version: 2.16.0

What were you doing when the application crashed?
그놈 압축관리자로 압축파일을 풀때, 목적위치를 ftp로 적어주고 풀기버튼을 눌렀음.
이런방식이 안될것을 알지만, 기능을 압축관리자에 추가 할 필요가 있을걷 같다는 생각에....


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 89939968 vsize: 0 resident: 89939968 share: 0 rss: 16678912 rss_rlim: 0
CPU usage: start_time: 1191511980 rtime: 0 utime: 54 stime: 0 cutime:50 cstime: 0 timeout: 4 it_real_value: 0 frequency: 10

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)
[Thread debugging using libthread_db enabled]
[New Thread -1209071920 (LWP 5573)]
(no debugging symbols found)
0x007a2402 in __kernel_vsyscall ()

+ Trace 167530

Thread 1 (Thread -1209071920 (LWP 5573))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_utf8_validate
    from /lib/libglib-2.0.so.0
  • #5 g_filename_display_name
    from /lib/libglib-2.0.so.0
  • #6 g_cclosure_marshal_VOID__BOOLEAN
  • #7 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #8 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #9 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #12 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_button_set_alignment
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_button_set_alignment
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_marshal_BOOLEAN__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 g_value_set_static_boxed
    from /lib/libgobject-2.0.so.0
  • #17 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #21 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #25 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #26 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #27 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #28 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 g_cclosure_marshal_VOID__BOOLEAN
  • #30 __libc_start_main
    from /lib/libc.so.6
  • #31 g_cclosure_marshal_VOID__BOOLEAN
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2007-10-29 22:44:42 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 357188 ***