Bug 742409 – Chained help window opening

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 742409 - Chained help window opening


Summary:	Chained help window opening


Status:	RESOLVED DUPLICATE of bug 745407

Product:	yelp
Classification:	Applications
Component:	General
Version:	3.14.x
Hardware:	Other Linux

Importance:	Normal major
Target Milestone:	---
Assigned To:	Yelp maintainers
QA Contact:	Yelp maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2015-01-05 19:21 UTC by Viktor Sidochenko
Modified:	2015-03-02 23:06 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Viktor Sidochenko 2015-01-05 19:21:44 UTC

Execute command 
$yelp INFO::main:
As result - Infinite help window opens over all windows(new window appaers on existent closing)

This string is part of log4j output thich parsed by gnome-terminal as link

Full example:
2015-01-05 23:45:47.747:INFO::main: Logging initialized @672ms

Comment 1 André Klapper 2015-01-06 09:06:54 UTC

Confirming for yelp-3.14.1-2.fc21.i686, after a while I end up with:


(yelp:11463): GLib-ERROR **: creating thread 'uri-resolve': Error creating thread: Resource temporarily unavailable

Program received signal SIGTRAP, Trace/breakpoint trap.
g_logv (log_domain=log_domain@entry=0xb55f06ce "GLib", log_level=log_level@entry=G_LOG_LEVEL_ERROR, 
    format=format@entry=0xb55fde76 "creating thread '%s': %s", args=args@entry=0xbfffe9bc "H(\373\267\060J1\b\330\351\377\277") at gmessages.c:1046
1046		  g_private_set (&g_log_depth, GUINT_TO_POINTER (depth));
(gdb) thread apply all bt

+ Trace 234508

Thread 1 (Thread 0xb1d9f8c0 (LWP 11463))

#0 g_logv
at gmessages.c line 1046
#1 g_log
at gmessages.c line 1079
#2 g_thread_new
at gthread.c line 806
#3 resolve_start
at yelp-uri.c line 302
#4 open_uri
#5 yelp_application_command_line
#6 ffi_call_SYSV
from /lib/libffi.so.6
#7 ffi_call
from /lib/libffi.so.6
#8 g_cclosure_marshal_generic_va
#9 g_type_class_meta_marshalv
#10 _g_closure_invoke_va
#11 g_signal_emit_valist
#12 g_signal_emit_by_name
at gsignal.c line 3405
#13 g_application_impl_method_call
at gapplicationimpl-dbus.c line 273
#14 call_in_idle_cb
at gdbusconnection.c line 4884
#15 g_idle_dispatch
at gmain.c line 5367
#16 g_main_dispatch
at gmain.c line 3111
#17 g_main_context_dispatch
at gmain.c line 3710
#18 g_main_context_iterate
at gmain.c line 3781
#19 g_main_context_iteration
at gmain.c line 3842
#20 g_application_run
at gapplication.c line 2282
#21 main

1041		      _g_log_abort (!(test_level & G_LOG_FLAG_RECURSION));
1042	#endif /* !G_OS_WIN32 */
1043		    }
1044		  
1045		  depth--;
1046		  g_private_set (&g_log_depth, GUINT_TO_POINTER (depth));
1047		}
1048	    }
1049	
1050	  g_free (msg_alloc);
(gdb)

Comment 2 David King 2015-03-02 23:06:30 UTC

Thanks for taking the time to report this.
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 in the code repository.

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