Google Chrome freezes at startup. Reproducible: Always Steps to Reproduce: 1. Login into KDE 2. Run Google Chrome Stable [version 44.0.2403.125] 3. Observe that Chrome is frozen 4. run '$ gdb --pid `pgrep chrome` 5. in gdb type bt Actual Results: Chrome freezes inside Oxygen::QtSettings::runCommand ?! Expected Results: Chrome works as usual (gdb) bt #0 0x00007eff90f891cd in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007eff9545161a in read_ints (__nbytes=8, __buf=0x7ffc34c22a10, __fd=213) at /usr/include/bits/unistd.h:44 #2 0x00007eff9545161a in read_ints (fd=213, buf=buf@entry=0x7ffc34c22a10, n_ints_in_buf=n_ints_in_buf@entry=2, n_ints_read=n_ints_read@entry=0x7ffc34c229bc, error=error@entry=0x0) at gspawn.c:1262 #3 0x00007eff95451a3c in fork_exec_with_pipes (intermediate_child=intermediate_child@entry=0, working_directory=working_directory@entry=0x0, argv=0x1a736ac9b540, envp=envp@entry=0x0, close_descriptors=close_descriptors@entry=1, search_path=search_path@entry=1, search_path_from_envp=0, stdout_to_null=0, stderr_to_null=0, child_inherits_stdin=0, file_and_argv_zero=0, cloexec_pipes=0, child_setup=0x0, user_data=0x0, child_pid=0x7ffc34c22ae8, standard_input=0x0, standard_output=0x7ffc34c22ae0, standard_error=0x0, error=0x0) at gspawn.c:1480 #4 0x00007eff9545215f in g_spawn_sync (working_directory=working_directory@entry=0x0, argv=<optimized out>, envp=envp@entry=0x0, flags=flags@entry=G_SPAWN_SEARCH_PATH, child_setup=child_setup@entry=0x0, user_data=user_data@entry=0x0, standard_output=0x7ffc34c22c80, standard_error=0x0, exit_status=0x0, error=0x0) at gspawn.c:288 #5 0x00007eff954528c3 in g_spawn_command_line_sync (command_line=<optimized out>, standard_output=0x7ffc34c22c80, standard_error=0x0, exit_status=0x0, error=0x0) at gspawn.c:732 #6 0x00007eff7fc5df79 in Oxygen::QtSettings::runCommand(std::string const&, char*&) const () at /usr/lib64/gtk-2.0/2.10.0/engines/liboxygen-gtk.so #7 0x00007eff7fc6263e in Oxygen::QtSettings::kdeIconPathList() const () at /usr/lib64/gtk-2.0/2.10.0/engines/liboxygen-gtk.so #8 0x00007eff7fc74eed in Oxygen::QtSettings::initialize(unsigned int) () at /usr/lib64/gtk-2.0/2.10.0/engines/liboxygen-gtk.so #9 0x00007eff7fc92be1 in Oxygen::Style::initialize(unsigned int) () at /usr/lib64/gtk-2.0/2.10.0/engines/liboxygen-gtk.so #10 0x00007eff7fc93001 in Oxygen::Style::fileChanged(_GFileMonitor*, _GFile*, _GFile*, GFileMonitorEvent, void*) () at /usr/lib64/gtk-2.0/2.10.0/engines/liboxygen-gtk.so #11 0x00007eff8f6d9db0 in ffi_call_unix64 () at /lib64/libffi.so.6 #12 0x00007eff8f6d9818 in ffi_call () at /lib64/libffi.so.6 #13 0x00007eff9570b8bc in g_cclosure_marshal_generic_va (closure=0x1a736ac45020, return_value=0x0, instance=0x1a736ac8f0b0, args_list=<optimized out>, marshal_data=0x0, n_params=3, param_types=0x1a736acda180) at gclosure.c:1541 #14 0x00007eff9570ae84 in _g_closure_invoke_va (closure=closure@entry=0x1a736ac45020, return_value=return_value@entry=0x0, instance=instance@entry=0x1a736ac8f0b0, args=args@entry=0x7ffc34c233a0, n_params=<optimized out>, param_types=0x1a736acda180) at gclosure.c:831 #15 0x00007eff95724b00 in g_signal_emit_valist (instance=0x1a736ac8f0b0, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7ffc34c233a0) at gsignal.c:3218 #16 0x00007eff9572534f in g_signal_emit (instance=instance@entry=0x1a736ac8f0b0, signal_id=<optimized out>, detail=detail@entry=0) at gsignal.c:3365 #17 0x00007eff942b1371 in emit_cb (data=0x1a736ac8f0b0) at gfilemonitor.c:404 #18 0x00007eff9540b7fb in g_main_context_dispatch (context=0x1a736ab41900) at gmain.c:3111 #19 0x00007eff9540b7fb in g_main_context_dispatch (context=context@entry=0x1a736ab41900) at gmain.c:3710 #20 0x00007eff9540bb98 in g_main_context_iterate (context=context@entry=0x1a736ab41900, block=block@entry=0, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3781 #21 0x00007eff9540bc4c in g_main_context_iteration (context=0x1a736ab41900, may_block=0) at gmain.c:3842
My guess is that Chrome is messing with signals, breaking g_spawn_*.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.