Bug 452011 – crash in Help: Runing OpenOffice 2.2

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 452011 - crash in Help: Runing OpenOffice 2.2


Summary:	crash in Help: Runing OpenOffice 2.2


Status:	RESOLVED DUPLICATE of bug 371007

Product:	yelp
Classification:	Applications
Component:	General
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Yelp maintainers
QA Contact:	Yelp maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-28 19:53 UTC by richards
Modified:	2007-06-29 11:56 UTC

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

Description richards 2007-06-28 19:53:29 UTC

Version: 2.16.0

What were you doing when the application crashed?
Runing OpenOffice 2.2


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2962.fc6xen #1 SMP Tue Jun 19 19:47:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 61820928 vsize: 0 resident: 61820928 share: 0 rss: 15949824 rss_rlim: 0
CPU usage: start_time: 1183060329 rtime: 0 utime: 43 stime: 0 cutime:34 cstime: 0 timeout: 9 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/yelp'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208674592 (LWP 4546)]
[New Thread -1210774640 (LWP 4646)]
(no debugging symbols found)
0x00ea1402 in __kernel_vsyscall ()

+ Trace 144423

Thread 1 (Thread -1208674592 (LWP 4546))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/nosegneg/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/i686/nosegneg/libc.so.6
#6 abort
from /lib/i686/nosegneg/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 g_cclosure_marshal_VOID__VOID
#10 gnome_ice_init
from /usr/lib/libgnomeui-2.so.0
#11 g_closure_invoke
from /lib/libgobject-2.0.so.0
#12 g_signal_chain_from_overridden
from /lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#14 g_signal_emit
from /lib/libgobject-2.0.so.0
#15 gnome_client_set_clone_command
from /usr/lib/libgnomeui-2.so.0
#16 _SmcProcessMessage
from /usr/lib/libSM.so.6
#17 IceProcessMessages
from /usr/lib/libICE.so.6
#18 gnome_ice_init
from /usr/lib/libgnomeui-2.so.0
#19 g_io_channel_unix_get_fd
from /lib/libglib-2.0.so.0
#20 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#21 g_main_context_check
from /lib/libglib-2.0.so.0
#22 g_main_loop_run
from /lib/libglib-2.0.so.0
#23 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#24 g_cclosure_marshal_VOID__VOID
#25 __libc_start_main
from /lib/i686/nosegneg/libc.so.6
#26 g_cclosure_marshal_VOID__VOID
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
restoring session
ASSERT: "!name.isEmpty()" in kdirlister.cpp (969)
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  154
  Minor opcode:  6
  Resource id:  0xa8
QClipboard::setData: Cannot set X11 selection owner for PRIMARY
DCOP: unregister 'anonymous-4641'
kdeinit: PID 4641 terminated.
Yelp-ERROR **: Cannot recieve window list - Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply 
aborting...
** (bug-buddy:4650): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Comment 1 palfrey 2007-06-29 11:56:07 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

*** This bug has been marked as a duplicate of 371007 ***