mirror of
https://github.com/benbusby/whoogle-search.git
synced 2026-04-25 12:15:50 +03:00
[GH-ISSUE #476] Manjaro update breaks Whoggle #312
Labels
No labels
Fixed (Pending PR Merge)
Stale
bug
enhancement
enhancement
good first issue
help wanted
keep-open
needs more info
pull-request
question
theme
unfortunate
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/whoogle-search#312
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @IAmHugh001 on GitHub (Oct 20, 2021).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/476
I just got the latest testing update for Manjaro and after a reboot and launching Vivaldi I noticed Whoogle didn't launch. I closed Vivaldi and checked Whoogles status and got the below. I have also tried to enable and start whoogle's service and still the below. Running the latest Manjaro with KDE Plasma 2.23 desktop
@benbusby commented on GitHub (Oct 20, 2021):
Can you post the detailed logs for the service (i.e.
journalctl -u whoogle)?@IAmHugh001 commented on GitHub (Oct 20, 2021):
Here you go.
@shayaknyc commented on GitHub (Oct 20, 2021):
Came here to see if this was posted. Seems like this is an Arch issue (and not specific to Manjaro, as I'm running Garuda), related to a recent KDE update. Here's the traceback on manually running the ExecStart command from the whoogle.service script (both with and without
sudo):/opt/whoogle-search/venv/bin/python3 -um app --host 0.0.0.0 --port 5000Here's a link to a thread on the Garuda forum that had a similar issue (same error referencing
libffi.so.7) but for FireDragon browser:https://forum.garudalinux.org/t/this-is-just-a-heads-up-i-think/13426
@IAmHugh001 commented on GitHub (Oct 20, 2021):
According to that thread it's fixed but still having the issue here.
@IAmHugh001 commented on GitHub (Oct 20, 2021):
Just got the update and all is good now. Thanks
@shayaknyc commented on GitHub (Oct 20, 2021):
@Locutus64 they only fixed the FireDragon issue with a rebuild. The fix for FireDragon was specific to that program, but the thread mentions what the issue was, and I thought it would be relevant here.
@IAmHugh001 commented on GitHub (Oct 20, 2021):
I'd be willing to bet the two issues are one and the same. Odds are against have two separate issues arise the same day.