Issue 53881 - Program closes when attempting to open existing file.
Summary: Program closes when attempting to open existing file.
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: 680m125
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: caolanm
QA Contact: issues@framework
URL:
Keywords: needmoreinfo
Depends on:
Blocks:
 
Reported: 2005-08-28 22:18 UTC by weinerdogus
Modified: 2005-08-31 14:52 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description weinerdogus 2005-08-28 22:18:06 UTC
When attempting to open an existing file, File > Open > try to select folder
which contains the file, the program closes. No error messages, just close.
Version 1.9.125
Comment 1 michael.ruess 2005-08-29 11:01:06 UTC
Reassigned to ES.
Comment 2 eric.savary 2005-08-29 11:24:28 UTC
Does this happen with any file?
In any OOo application?
Which distribution do you have?
Do you get an error message in the console?

Please try to uninstall and reinstall.
Comment 3 weinerdogus 2005-08-29 19:41:15 UTC
Does this happen with any file?   Yes
In any OOo application?   Yes
Which distribution do you have?   Fedora Core 4
Do you get an error message in the console?   No

Please try to uninstall and reinstall.
Comment 4 weinerdogus 2005-08-29 22:16:37 UTC
Please try to uninstall and reinstall.
Did this. No change. Program still exits when attempting to open an existing file!
using kernel 2.6.12-1.1447_FC4
Comment 5 eric.savary 2005-08-30 08:40:48 UTC
Reassigning to framework
Comment 6 mci 2005-08-30 10:58:22 UTC
Hi weinerdogus,

I followed your steps here on Ubuntu-Linux using m125 (from ftp.linux.cz/...)
and I didn't get your problem...

Do you try to open the file via SMB, NFS, HTTP, FTP or something similar?
Where did you get your OOo from ?

Comment 7 weinerdogus 2005-08-30 12:56:37 UTC
Do you try to open the file via SMB, NFS, HTTP, FTP or something similar?
No.

Where did you get your OOo from ?
Installed with FC4, updated via yum.

Previous version 1.9.118 worked fine. I don't know what could have changed
during update.
Comment 8 weinerdogus 2005-08-30 19:46:28 UTC
Changed setting
Tools > Options > General
check use OpenOffice.org dialogs
Am now able to open existing files without program closing.
Why will it not work without this box checked?
Comment 9 lohmaier 2005-08-31 00:19:31 UTC
adding cmc to cc since he might be interested in this (apparently fedora &
native fpicker specific) problem.
Comment 10 caolanm 2005-08-31 07:59:51 UTC
nope, never saw this. Just "closes", no crash reporter dialog ? Mighty strange.
Comment 11 caolanm 2005-08-31 08:09:58 UTC
if the reporter could reneable the gnome dialog and close ooo and then.

> gdb /usr/lib/openoffice.org2.0/program/soffice.bin
(gdb) run -writer
(gdb) bt
and paste in the results when it crashes that would help
Comment 12 weinerdogus 2005-08-31 11:47:04 UTC
Program received signal SIG33, Real-time event 33.
[Switching to Thread -1242551376 (LWP 2695)]
0x00a03402 in __kernel_vsyscall ()
(gdb) bt
#0  0x00a03402 in __kernel_vsyscall ()
#1  0x002aca5c in poll () from /lib/libc.so.6
#2  0x0218f55e in ?? ()
   from /usr/lib/openoffice.org2.0/program/libdtransX11680li.so
#3  0x0218f625 in ?? ()
   from /usr/lib/openoffice.org2.0/program/libdtransX11680li.so
#4  0x00fcb339 in osl_yieldThread ()
   from /usr/lib/openoffice.org2.0/program/libuno_sal.so.3
#5  0x00af7b80 in start_thread () from /lib/libpthread.so.0
#6  0x002b69ce in clone () from /lib/libc.so.6
(gdb)
Comment 13 caolanm 2005-08-31 12:05:18 UTC
gdb is trapping SIG33, which is not the real problem. Apologies, try...

> gdb /usr/lib/openoffice.org2.0/program/soffice.bin
(gdb) handle SIGPWR nostop noprint
(gdb) handle SIGXCPU nostop noprint
(gdb) handle SIG33 nostop noprint
(gdb) run -writer
(gdb) bt
and paste in the results when it crashes
Comment 14 weinerdogus 2005-08-31 13:19:57 UTC
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208506688 (LWP 2860)]
0x00bdec1a in strcmp () from /lib/libc.so.6
(gdb) bt
#0  0x00bdec1a in strcmp () from /lib/libc.so.6
#1  0x06d83eff in gtk_file_chooser_dialog_new_with_backend ()
   from /usr/lib/libgtk-x11-2.0.so.0
#2  0x06d84dcc in gtk_file_chooser_dialog_new_with_backend ()
   from /usr/lib/libgtk-x11-2.0.so.0
#3  0x06d8b45d in gtk_file_chooser_dialog_new_with_backend ()
   from /usr/lib/libgtk-x11-2.0.so.0
#4  0x05475817 in g_cclosure_marshal_VOID__VOID ()
   from /usr/lib/libgobject-2.0.so.0
#5  0x0546a285 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#6  0x0547878b in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0
#7  0x05479ee0 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#8  0x0547a254 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#9  0x06e87498 in gtk_tree_selection_select_range ()
   from /usr/lib/libgtk-x11-2.0.so.0
#10 0x06e9900e in gtk_tree_view_scroll_to_cell ()
   from /usr/lib/libgtk-x11-2.0.so.0
#11 0x06e9f5b7 in gtk_tree_view_set_cursor_on_cell ()
   from /usr/lib/libgtk-x11-2.0.so.0
#12 0x06e9f670 in gtk_tree_view_set_cursor () from /usr/lib/libgtk-x11-2.0.so.0
#13 0x06d88b16 in gtk_file_chooser_dialog_new_with_backend ()
   from /usr/lib/libgtk-x11-2.0.so.0
#14 0x05475817 in g_cclosure_marshal_VOID__VOID ()
---Type <return> to continue, or q <return> to quit---
   from /usr/lib/libgobject-2.0.so.0
#15 0x0546a285 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#16 0x0547878b in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0
#17 0x05479ee0 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#18 0x0547a254 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#19 0x06d96576 in gtk_file_folder_list_children ()
   from /usr/lib/libgtk-x11-2.0.so.0
#20 0x05475817 in g_cclosure_marshal_VOID__VOID ()
   from /usr/lib/libgobject-2.0.so.0
#21 0x0546a285 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#22 0x0547878b in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0
#23 0x05479ee0 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#24 0x0547ca40 in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0
#25 0x05c71b2c in gtk_file_system_gnome_vfs_new ()
   from /usr/lib/gtk-2.0/2.4.0/filesystems/libgnome-vfs.so
#26 0x01d270c9 in _gnome_vfs_job_go () from /usr/lib/libgnomevfs-2.so.0
#27 0x02a3a650 in g_child_watch_add () from /usr/lib/libglib-2.0.so.0
#28 0x02a383ee in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#29 0x02a3b3f6 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#30 0x02a3b6e3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#31 0x06d666d1 in gtk_dialog_run () from /usr/lib/libgtk-x11-2.0.so.0
#32 0x027c79c1 in ?? ()
   from /usr/lib/openoffice.org2.0/program/fps_gnome.uno.so
---Type <return> to continue, or q <return> to quit---
#33 0x027c7a05 in ?? ()
   from /usr/lib/openoffice.org2.0/program/fps_gnome.uno.so
#34 0x02a39f06 in g_main_context_wakeup () from /usr/lib/libglib-2.0.so.0
#35 0x02a383ee in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#36 0x02a3b3f6 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#37 0x02a3b8d8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#38 0x017195f9 in ?? ()
   from /usr/lib/openoffice.org2.0/program/libvclplug_gtk680li.so
#39 0x00000000 in ?? ()
(gdb)

Comment 15 caolanm 2005-08-31 13:49:17 UTC
good backtrace, but the crash is in gtk not OOo IMO. 

these bugs looks very similiar:
http://bugzilla.gnome.org/show_bug.cgi?id=314033
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=165970

I propose to open a bug against fedora gtk as
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167182
Comment 16 caolanm 2005-08-31 13:50:08 UTC
can't be fixed in OOo, needs to be fixed in gtk2/gnome-vfs2 , so "INVALID" for OOo
Comment 17 caolanm 2005-08-31 13:50:57 UTC
.
Comment 18 caolanm 2005-08-31 13:53:19 UTC
btw, it is *any* directory or a specific directory, e.g. one that you don't have
permissions to visit, e.g. if you use gedit and navigate to the same directory
does gedit crash ?
Comment 19 weinerdogus 2005-08-31 14:52:24 UTC
it can be any directory. if i attempt to open "Text_Files in my user directory,
it crashes. Similar if i attempt to open filesystem, it crashes.
Yes. gedit does the same thing.
thanks