Unable to open Gitify on Pop!_OS 22.04 #1612
Comments
|
There's not enough information included in this Issue for us to act on it:
In general, filing Issues saying simply "not works" isn't a good use of anyone's time, for any project. If you're unsure about your English, there's more than enough LLMs out there to help you translate. They could also guide you through common debugging steps, and suggest what you could do to fill out an effective bug report. If you're unsure what even to prompt it, you could copy paste my message and your issue and it would probably explain in whatever language you'd like. Happy to re-open this if sufficiently more information is provided later. |
boundless-forest
changed the title
|
I sincerely apologize for my informal description of the issue. I have added more details to it; would you mind reviewing it again? Please feel free to ask me for any additional information if needed. @bmulholland |
|
Much better, thank you! |
|
@boundless-forest if possible, I'd be interested to hear your experience running Gitify from source code on your PopOS machine. Does that work? |
|
I'm stuck at the first step when installing dependencies; it reports the following error, indicating something unexpected in the post-install script. ⋊> ~/w/gitify on main ◦ pnpm install 13:58:56
Lockfile is up to date, resolution step is skipped
Packages: +2 -20
++--------------------
Progress: resolved 0, reused 21, downloaded 1, added 2, done
node_modules/electron: Running postinstall script, failed in 2m 15.9s
node_modules/electron postinstall$ node install.js
│ RequestError
│ at ClientRequest.<anonymous> (/home/bear/working-on/gitify/node_modules/got/dist/source/core/index.js:970:111)
│ at Object.onceWrapper (node:events:622:26)
│ at ClientRequest.emit (node:events:519:35)
│ at origin.emit (/home/bear/working-on/gitify/node_modules/@szmarczak/http-timer/dist/source/index.js:43:20)
│ at emitErrorEvent (node:_http_client:103:11)
│ at TLSSocket.socketErrorListener (node:_http_client:506:5)
│ at TLSSocket.emit (node:events:507:28)
│ at emitErrorNT (node:internal/streams/destroy:170:8)
│ at emitErrorCloseNT (node:internal/streams/destroy:129:3)
│ at process.processTicksAndRejections (node:internal/process/task_queues:90:21)AggregateError [ETIMEDOUT]:
│ at internalConnectMultiple (node:net:1128:18)
│ at afterConnectMultiple (node:net:1693:7)
└─ Failed in 2m 15.9s at /home/bear/working-on/gitify/node_modules/electron
ELIFECYCLE Command failed with exit code 1. |
|
Yeah, env issues can be frustrating! Let us know when you've worked through issues installing electron etc and have details on running Gitify itself. |
|
ACtually i have the exact same issue on PopOS 22.04. The tray appear but does not react to click (left/right). |
setchy
added
the
priority:low
|
I have this same issue. Can't be used right now on Pop!_OS. |
|
Curious if any of you have tried downgrading Gitify. I'm interested in what is the latest working version |
|
I did a test with those versions, neither of them works, but I noticed a strange log in the installation, not sure if it's helpful. ⋊> ~/Downloads sudo dpkg -i gitify_5.10.0_amd64.deb 13:49:46
dpkg: warning: downgrading gitify from 5.17.0 to 5.10.0
(Reading database ... 235664 files and directories currently installed.)
Preparing to unpack gitify_5.10.0_amd64.deb ...
Unpacking gitify (5.10.0) over (5.17.0) ...
Setting up gitify (5.10.0) ...
update-alternatives is /usr/bin/update-alternatives
Could not parse file "/usr/share/applications/guake.desktop": No such file or directory // this line
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Processing triggers for desktop-file-utils (0.26-1ubuntu3) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu3) ...The log looks like this: ⋊> ~ cat ~/.config/gitify/logs/main.log 14:00:26
[2024-12-26 13:36:47.848] [info] Electron's autoUpdater does not support the 'linux' platform. Ref: https://www.electronjs.org/docs/latest/api/auto-updater#platform-notices
[2024-12-26 13:41:42.718] [info] Electron's autoUpdater does not support the 'linux' platform. Ref: https://www.electronjs.org/docs/latest/api/auto-updater#platform-notices
[2024-12-26 13:42:00.910] [info] Electron's autoUpdater does not support the 'linux' platform. Ref: https://www.electronjs.org/docs/latest/api/auto-updater#platform-notices
[2024-12-26 13:42:31.155] [info] Electron's autoUpdater does not support the 'linux' platform. Ref: https://www.electronjs.org/docs/latest/api/auto-updater#platform-notices
[2024-12-26 13:46:09.007] [info] Electron's autoUpdater does not support the 'linux' platform. Ref: https://www.electronjs.org/docs/latest/api/auto-updater#platform-notices
[2024-12-26 13:46:37.737] [info] Electron's autoUpdater does not support the 'linux' platform. Ref: https://www.electronjs.org/docs/latest/api/auto-updater#platform-notices
[2024-12-26 13:51:21.548] [info] Electron's autoUpdater does not support the 'linux' platform. Ref: https://www.electronjs.org/docs/latest/api/auto-updater#platform-notices
|
|
Thanks @boundless-forest So to confirm my understanding, these versions were tested and found incompatible with PopOS
Re: the |
|
Yes, it's a bit strange that I noticed from the GitHub issues that Gitify appears to work on other Linux platforms except Pop!_OS. However, since Pop!_OS is based on Ubuntu, it should function properly as well. I have researched this issue extensively but have not found a workaround. Do you have any suggestions? |
I'd continue to debug the logic within https://github.com/gitify-app/gitify/blob/main/src/main/main.ts, which controls showing/hiding the main window with the help of the package https://github.com/max-mapper/menubar |
|
I'm here if anything that I can help. Please tell me. |
Thank you. As above, I'd recommend continuing to debug those areas. The maintainers don't have readily access to an environment to reproduce atm |
|
Im getting a similar problem, even though for me, the window does appear very briefly and dissapears. It did appear alright when i first logged in tho. I'm running the AppImage. OS ➜ Arch Linux x86_64 WM ➜ Hyprland (Wayland) |
|
I have the same issue, After installing the I am using Ubuntu 22.04.5 LTS |
setchy
added
priority:medium
I have an Ubuntu 24.04.1 LTS VM and was able to verify both 5.18.0 running and the upcoming 6.0.0 release To install and run gitify I had to do a few steps Install First Launch Running Fix Chrome Sandbox permissions Success
I don't have a PopOS VM so wasn't able to test this variant |
|
I have followed all the steps you provided, but it still doesn’t work. I encountered the same permission issue you mentioned and executed the commands you suggested. However, even after doing so, the problem persists. I killed the process and restarted it, but the issue remains unchanged. I also restarted the machine, but unfortunately, the result is still the same.
should I wait for the next release? |
Damn!
you're welcome to report back with v6.0.0, but please note there isn't any specific changes related to this. This morning I tested all releases from v5.12.1 through to v6.0.0 on my Ubuntu VM and they worked by following the above steps. To resolve this for other users like yourself, I'll need further community assistance with debugging. |
|
@hazemadelkhalel - apologies, i noticed I made a typo above The second script should be I've also added this as a FAQ on https://gitify.io/faq |
Issue:After running Diagnosis:The errors indicate that the application is unable to connect to the X11 display server and the D-Bus message bus. This is likely due to missing or improperly configured dependencies related to the graphical environment (X11) and D-Bus. Solution:The issue was resolved by installing the dbus-x11 package, which provides the necessary D-Bus integration for X11 environments. To fix this, run the following command: This package ensures that the application can properly communicate with the X11 display server and D-Bus, resolving the errors related to display initialization and authorization. Additional Notes:If you are using a different desktop environment or display server (e.g., Wayland), you may need to install additional packages or configure your environment accordingly. For example, Wayland users might need to install wayland or weston packages. If the issue persists after installing dbus-x11, ensure that your X11 server is running and properly configured. You can also try running the application with the --no-sandbox flag as a temporary workaround, though this is not recommended for long-term use due to security implications. |
🔍 Is there already an issue for your problem?
📝 Description
I discovered Gitify this afternoon and attempted to install the deb version on PopOS first, which installed successfully. However, when I click the icon, the Gitify window does not open. The icon appears in the system bar, but there is no response when clicked.
I checked the process info like this:
I guess AppImage might work, so I’ll give it a try, but no luck. The Gitify window still hasn’t popped up.
The AppImage console output:
I'm not sure what to do next; perhaps there's a way to output a debug log?
🪜 Steps To Reproduce
Gitify Version
5.16.1
Operating System
PopOs 22.04
The text was updated successfully, but these errors were encountered: