Bug 459689 – crash in Help: open http://xmradio.com

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 459689 - crash in Help: open http://xmradio.com


Summary:	crash in Help: open http://xmradio.com


Status:	RESOLVED DUPLICATE of bug 364790

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-07-23 19:31 UTC by systemid
Modified:	2007-07-24 13:47 UTC

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

Description systemid 2007-07-23 19:31:58 UTC

Version: 2.16.0

What were you doing when the application crashed?
open http://xmradio.com


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.fc6 #1 SMP Tue Jun 19 18:50:05 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 507305984 vsize: 507305984 resident: 19824640 share: 12652544 rss: 19824640 rss_rlim: -1
CPU usage: start_time: 1185218972 rtime: 24 utime: 21 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496450512 (LWP 9191)]
[New Thread 1084229952 (LWP 9207)]
(no debugging symbols found)
0x000000342780d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 150065

Thread 1 (Thread 46912496450512 (LWP 9191))

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



----------- .xsession-errors ---------------------
Could not load library! Trying exec....
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x5c
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...
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x5c
** (bug-buddy:9266): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Comment 1 Iestyn Pryce 2007-07-24 13:47:59 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.

duplicate via Bug373623

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