Hide Forgot
Version-Release number of selected component: epiphany-3.11.4-1.fc21 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/libexec/epiphany-search-provider crash_function: ephy_history_service_find_url_rows executable: /usr/libexec/epiphany-search-provider kernel: 3.14.0-0.rc2.git3.2.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (5 frames) #2 ephy_history_service_find_url_rows at ephy-history-service-urls-table.c:302 #3 ephy_history_service_execute_query_urls at ephy-history-service.c:767 #4 ephy_history_service_process_message at ephy-history-service.c:1278 #5 run_history_service_thread at ephy-history-service.c:524 #6 g_thread_proxy at gthread.c:765
Created attachment 863378 [details] File: backtrace
Created attachment 863379 [details] File: cgroup
Created attachment 863382 [details] File: core_backtrace
Created attachment 863384 [details] File: dso_list
Created attachment 863387 [details] File: environ
Created attachment 863390 [details] File: limits
Created attachment 863391 [details] File: maps
Created attachment 863393 [details] File: open_fds
Created attachment 863395 [details] File: proc_pid_status
Created attachment 863398 [details] File: var_log_messages
I also hit this bug if I take the following steps: 1) Log in to the GNOME desktop 2) Enter the Overview 3) Type "software" 4) Hit enter (to launch GNOME Software) Results: This crash occurs and GNOME Software displays a screen with "No Application Data Found" I'm not certain if these are exactly the same bug or simply related.
*** Bug 1165353 has been marked as a duplicate of this bug. ***
(In reply to Stephen Gallagher from comment #11) > I also hit this bug if I take the following steps: > > 1) Log in to the GNOME desktop > 2) Enter the Overview > 3) Type "software" > 4) Hit enter (to launch GNOME Software) > > Results: > This crash occurs Epiphany on Fedora is split into two packages: the epiphany package contains the desktop file and search provider (the thing that could crash if you're tying a search in the overview) but is not installed by default, and the epiphany-runtime package that is installed by default contains the actual browser without any desktop file (so it appears that it is uninstalled), for running web apps that you can install with GNOME Software. My first thought was that this must be a search provider bug, but I guess it's possible that Software is starting Epiphany itself. We can easily rule out the search provider if you have only the epiphany-runtime and not the epiphany package installed: is that the case?
(In reply to Michael Catanzaro from comment #13) > (In reply to Stephen Gallagher from comment #11) > > I also hit this bug if I take the following steps: > > > > 1) Log in to the GNOME desktop > > 2) Enter the Overview > > 3) Type "software" > > 4) Hit enter (to launch GNOME Software) > > > > Results: > > This crash occurs > > Epiphany on Fedora is split into two packages: the epiphany package contains > the desktop file and search provider (the thing that could crash if you're > tying a search in the overview) but is not installed by default, and the > epiphany-runtime package that is installed by default contains the actual > browser without any desktop file (so it appears that it is uninstalled), for > running web apps that you can install with GNOME Software. My first thought > was that this must be a search provider bug, but I guess it's possible that > Software is starting Epiphany itself. We can easily rule out the search > provider if you have only the epiphany-runtime and not the epiphany package > installed: is that the case? I have both packages installed, but I don't recall if I did when I submitted that comment. I'm not seeing this crash anymore, but I have no idea when or how that happened. (I may have told ABRT to ignore it; I'm not sure how to check)
OK. Well actually, using my powers of deduction (aka by reading comment #0) I've determined that the search provider is to blame, and not Software after all.
So it crashed with the "fatal" error: "Could not build urls table query statement: no such table: urls" -- fatal in quotes since it's not robust to intentionally crash whenever a database update fails. I was not able to reproduce this crash with the search provider, but I was able to get the same backtrace by deleting ~/.config/epiphany/ephy-history.db when I had the browser open. We'll need to handle this failure a bit better.
Another user experienced a similar problem: from cold start of laptop, running a PAE kernel, loged in to gnome shell, uninstalled i686 kernel packages which were unnecessary, error got raised. Epeiphany was not executed from initial installation. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/libexec/epiphany-search-provider crash_function: ephy_history_service_find_url_rows executable: /usr/libexec/epiphany-search-provider kernel: 3.17.4-301.fc21.i686+PAE package: epiphany-3.14.2-2.fc21 reason: epiphany-search-provider killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
epiphany-3.14.2-3.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/epiphany-3.14.2-3.fc21
Package epiphany-3.14.2-3.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing epiphany-3.14.2-3.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-16901/epiphany-3.14.2-3.fc21 then log in and leave karma (feedback).
epiphany-3.14.2-3.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
epiphany-3.15.90-3.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/epiphany-3.15.90-3.fc22
(In reply to Fedora Update System from comment #21) > epiphany-3.15.90-3.fc22 has been submitted as an update for Fedora 22. > https://admin.fedoraproject.org/updates/epiphany-3.15.90-3.fc22 Ignore, I pasted the wrong bug URL.