Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Unable to get to the Debugging Information

Closed
  • Is something wrong?
#183 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Domain
desktop

Research direction

Start at the Web app’s main menu and the missing “About Web” entry described in the report; review the flatpak packaging and the CLI options shown in the issue. Confirm how debugging information is currently exposed, then verify that users can reach it in the flatpak without relying on an unavailable menu or undocumented command.

Written by the indexing model from the issue text.

Description

Needs Design Priority: Low Status: Confirmed
What Happened?

The Epiphany issue template at gitlab.gnome.org currently requests the following information:

  • Epiphany version (from About Web in the main menu):
  • WebKitGTK version (from About Web -> Troubleshooting -> Debugging Information):
  • Distributor (Linux operating system, Flathub, Epiphany Tech Preview, etc.):

Because the "About Web" menu item was removed in this flatpak, we're unable to get to About Web -> Troubleshooting -> Debugging Information.

Steps to Reproduce
  1. Open the "Web" app
  2. Open the main menu (cog wheel), and look for "About Web".
Expected Behavior

We should, at least, be able to get to the debugging information. The CLI doesn't expose it.

$ flatpak run org.gnome.Epiphany -h
Usage:
  epiphany [OPTION?] URL ?

Help Options:
  -h, --help                  Show help options

Application Options:
  --new-window                Open a new browser window instead of a new tab
  -l, --load-session=FILE     Load the given session state file
  -i, --incognito-mode        Start an instance with user data read-only
  -p, --private-instance      Start a private instance with separate user data
  -a, --application-mode      Start a private instance in web application mode
  --automation-mode           Start a private instance for WebDriver control
  --profile=DIR               Custom profile directory for private instance
  --search
OS Version

8.x (Circe)

OS Architecture

amd64 (on most hardwares)

Session Type

Secure Session (Wayland, This is the default)

Software Version

Latest release (I have run all updates)

Log Output
Hardware Info

No response

Dominant language
Meson
Stars
8
Forks
4
Avg merge
37m
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elementary/browser

All issues in elementary/browser

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.