Description of problem: From the command: CAMEL_DEBUG=all exec /usr/libexec/webkitgtk3/GtkLauncher >a_local_file I did this in an effort to find out more info as to why evolution seg faults (see https://bugzilla.redhat.com/show_bug.cgi?id=1094017) for my main user. The local file generated contained no output, as you may have guessed. Thanks, YBnawtbug Version-Release number of selected component: webkitgtk3-2.2.7-1.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/libexec/webkitgtk3/GtkLauncher crash_function: WebCore::Style::determineChange executable: /usr/libexec/webkitgtk3/GtkLauncher kernel: 3.14.2-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (2 frames) #0 WebCore::Style::determineChange at Source/WebCore/style/StyleResolveTree.cpp:61 #1 WebCore::Style::resolveTree at Source/WebCore/style/StyleResolveTree.cpp:474
Created attachment 893432 [details] File: backtrace
Created attachment 893433 [details] File: cgroup
Created attachment 893434 [details] File: core_backtrace
Created attachment 893435 [details] File: dso_list
Created attachment 893436 [details] File: environ
Created attachment 893437 [details] File: exploitable
Created attachment 893438 [details] File: limits
Created attachment 893439 [details] File: maps
Created attachment 893440 [details] File: open_fds
Created attachment 893441 [details] File: proc_pid_status
Created attachment 893442 [details] File: var_log_messages
Hurray, I figured it out! The ~/.mozilla/plugins folder was just a mirror of the /usr/iib64/mozilla/plugins folder, so, after moving the local folder to old, then restarting evolution, evolution WORKED! Then, I reran the exec of gtklauncher as above, and it brought up a nice little browser window synced to google.com. I did get three lines of output in the local file, possibly due to when I clicked the close button on my window manager, which also killed that window, and ended the terminal window from which I ran the command. So, it seems to work, at least as needed, so I am happy! {☺ or =+) <-- note the math smiley!} Thanks, YBnawtbug
Possible duplicate of 1026310
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.