Skip to content

On Kubuntu 25.10 modal window apperas in the middle of the screen #2341

New issue
New issue
Closed
Bug
#3218
Closed
On Kubuntu 25.10 modal window apperas in the middle of the screen#2341
Bug
#3218
Labels
fix-upstreamWhen the resolution is in an upstream package/libraryplatform:linuxRelated to linux build

Description

@alexey-anufriev
alexey-anufriev
opened on Oct 30, 2025

🔍 Is there already an issue for your problem?

  • I have checked older issues, open and closed

📝 Description

After upgrade to Kubuntu 25.10 main window on Gitify is now placed in the middle of the screen.
Also right click on tray icon gives no reaction.

🪜 Steps To Reproduce

  1. Open Gitify
  2. Check window placement
  3. Check right click on tray icon reaction

🪵 Log Excerpts

[2025-10-30 21:46:32.570] [info]  [app updater] Starting updater
[2025-10-30 21:46:32.572] [info]  [app updater] Checking for updates on application launch
[2025-10-30 21:46:32.572] [info]  Checking for update
[2025-10-30 21:46:32.572] [info]  [auto updater] Checking for update
[2025-10-30 21:46:34.045] [info]  Update for version 6.10.0 is not available (latest version: 6.10.0, downgrade is disallowed).
[2025-10-30 21:46:34.046] [info]  [auto updater] Update not available
[2025-10-30 21:46:34.046] [debug] checkForUpdatesAndNotify called, downloadPromise is null

Gitify Version

6.10.0

Operating System

Linux

GitHub Account

GitHub Cloud

📸 Screenshots

Image

Activity

  1. alexey-anufriev
    added
    bugSomething isn't working
    on Oct 30, 2025
  2. setchy
    added
    platform:linuxRelated to linux build
    fix-upstreamWhen the resolution is in an upstream package/library
    on Oct 30, 2025

  3. setchy commented on Oct 30, 2025

    @setchy
    setchy
    on Oct 30, 2025
    Member

    Thanks for reporting.

    Fix is likely to reside in https://github.com/max-mapper/menubar - that library needs a lot of love (or we need to choose to fork it and/or reimplement it locally)

  4. setchy
    added the
    Bug
    issue type on Nov 10, 2025
  5. setchy
    changed the issue type from
    Bug
    to
    Documentation
    on Mar 13, 2026
  6. setchy
    changed the issue type from
    Documentation
    to
    Bug
    on Mar 13, 2026
  7. setchy
    removed
    bugSomething isn't working
    on Mar 13, 2026

  8. afonsojramos commented on Aug 20, 2026

    @afonsojramos
    afonsojramos
    on Aug 20, 2026
    Member

    Is this still happening on 7.4.0?

  9. afonsojramos
    closed this as completedon Aug 24, 2026

  10. alexey-anufriev commented on Aug 24, 2026

    @alexey-anufriev
    alexey-anufriev
    on Aug 24, 2026
    Author

    @afonsojramos, yes, even on 7.5.0. Please reopen the issue.

  11. afonsojramos commented on Aug 24, 2026

    @afonsojramos
    afonsojramos
    on Aug 24, 2026
    Member

    @alexey-anufriev On native Wayland, tray-anchored positioning is not possible, and there is nothing us or the library can do about it. Basically, an application cannot set the position of its own window (setPosition is a no-op, getPosition reads back [0, 0]), and the tray icon reports no coordinates. The compositor decides where the popover appears, which is usually the center of the screen.

  12. afonsojramos commented on Aug 24, 2026

    @afonsojramos
    afonsojramos
    on Aug 24, 2026
    Member

    Unless there is a workaround that you are aware of, there is nothing we can do here.

  13. alexey-anufriev commented on Aug 24, 2026

    @alexey-anufriev
    alexey-anufriev
    on Aug 24, 2026
    Author

    --ozone-platform=x11 works as a temp fix.

    Maybe a fix in gitify can looks like this:

    const shouldUseXWayland =
  process.platform === 'linux' &&
  Boolean(process.env.WAYLAND_DISPLAY) &&
  Boolean(process.env.DISPLAY) &&
  !app.commandLine.hasSwitch('ozone-platform');

if (shouldUseXWayland) {
  app.commandLine.appendSwitch('ozone-platform', 'x11');
}

  14. afonsojramos commented on Aug 24, 2026

    @afonsojramos
    afonsojramos
    on Aug 24, 2026
    Member

    I was about to suggest that you gave that a try, but not sure that setting it at the application layer is a good option for us since it degrades the experience for Wayland users to fix placement.

  15. alexey-anufriev commented on Aug 24, 2026

    @alexey-anufriev
    alexey-anufriev
    on Aug 24, 2026
    Author

    Maybe a new setting/toggle?

  16. afonsojramos commented on Aug 24, 2026

    @afonsojramos
    afonsojramos
    on Aug 24, 2026
    Member

    @alexey-anufriev I've opened #3218, which adds an opt-in setting to run Gitify under X11/XWayland. That restores tray-anchored positioning on Wayland sessions. Since I can't reproduce this reliably myself, it would be a big help if you could verify it on Kubuntu 25.10.

    You can test it without building anything. A packaged Linux build from that PR is attached to its CI run:

    1. Go to https://github.com/gitify-app/gitify/actions/runs/32720807129
    2. Under Artifacts, download Gitify-dist-linux
    3. Unzip it and run the AppImage:
    chmod +x Gitify-*.AppImage
./Gitify-*.AppImage
    1. Open Settings → System and enable "Use X11 backend (restart required)"
    2. Quit Gitify completely and start it again
    3. Click the tray icon

    What I'm hoping to hear is whether the window now opens next to the tray icon rather than in the middle of the screen, and whether anything else looks worse, particularly text sharpness, since XWayland does not support fractional scaling as well as native Wayland does.

    To undo it, either turn the setting off and restart, or delete ~/.config/gitify/UseX11Backend.

  17. afonsojramos
    reopened this on Aug 24, 2026
  18. afonsojramos
    linked a pull request that will close this issuefeat(linux): add opt-in X11 backend for tray-anchored positioning #3218on Aug 24, 2026

  19. alexey-anufriev commented on Aug 24, 2026

    @alexey-anufriev
    alexey-anufriev
    on Aug 24, 2026
    Author

    Unfortunately fix didn't help.

    Here is what happens when I start the app with setting disabled:

    ./Gitify-7.5.0.AppImage --password-store=gnome-libsecret
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
21:05:41.346 › [app updater] Starting updater
21:05:41.352 › [app updater] Checking for updates on application launch
21:05:41.352 › [auto updater] Checking for update
[228590:0824/210541.595551:ERROR:ui/ozone/platform/wayland/gpu/wayland_surface_factory.cc:249] '--ozone-platform=wayland' is not compatible with Vulkan. Consider switching to '--ozone-platform=x11' or disabling Vulkan
[228402:0824/210541.802600:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:277] Unable to set image transfer function.
[228402:0824/210541.802612:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:195] Failed to populate image description for color space {primaries:BT709, transfer:SRGB, matrix:RGB, range:FULL}
21:05:42.612 › [auto updater] Update not available
[228402:0824/210549.865149:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:277] Unable to set image transfer function.
[228402:0824/210549.865180:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:195] Failed to populate image description for color space {primaries:BT709, transfer:SRGB, matrix:RGB, range:FULL}
[228402:0824/210549.865194:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_management_surface.cc:64] Failed to get image description for color space.
21:06:06.491 › [settingsReset] Settings have been reset to defaults
21:06:10.003 › [settingsReset] Settings have been reset to defaults

    then I enable and restart:

    ./Gitify-7.5.0.AppImage --password-store=gnome-libsecret
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
21:06:21.582 › [applyOzonePlatform] X11 backend enabled, forcing --ozone-platform=x11
21:06:21.997 › [app updater] Starting updater
21:06:21.997 › [app updater] Checking for updates on application launch
21:06:21.998 › [auto updater] Checking for update
[229643:0824/210622.570632:ERROR:gpu/ipc/client/command_buffer_proxy_impl.cc:285] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[229572:0824/210622.587377:ERROR:content/browser/gpu/gpu_process_host.cc:1089] GPU process exited unexpectedly: exit_code=139
[229572:0824/210623.023025:ERROR:content/browser/gpu/gpu_process_host.cc:1089] GPU process exited unexpectedly: exit_code=139
21:06:23.103 › [auto updater] Update not available
[229572:0824/210623.471537:ERROR:content/browser/gpu/gpu_process_host.cc:1089] GPU process exited unexpectedly: exit_code=139
[229768:0824/210623.478321:ERROR:ui/base/x/x11_software_bitmap_presenter.cc:147] XGetWindowAttributes failed for window 1

    Tray icon shows but nothing happens when I click on it. Task manager icon shows on click as well, but no main window.

  20. afonsojramos commented on Aug 25, 2026

    @afonsojramos
    afonsojramos
    on Aug 25, 2026
    Member

    Thanks, that log is really helpful. It shows the setting is working correctly (forcing --ozone-platform=x11 appears), but X11 then hits a separate problem: the GPU process is segfaulting (exit_code=139), so no window gets drawn.

    I suspect Vulkan. Your first log has Chromium saying '--ozone-platform=wayland' is not compatible with Vulkan, so Vulkan is active on your system. Wayland skips it, X11 tries it, and it appears to crash there.

    Could you try these two, with the setting turned off so we control the flags directly?

    # A: X11 without Vulkan
./Gitify-7.5.0.AppImage --ozone-platform=x11 --disable-features=Vulkan

# B: X11 with GPU acceleration off entirely
./Gitify-7.5.0.AppImage --ozone-platform=x11 --disable-gpu

    If either shows the window next to the tray icon, that tells me what to pair with the X11 switch. Also, which GPU and driver are you on (lspci -k | grep -A3 VGA)?

  21. alexey-anufriev commented on Aug 25, 2026

    @alexey-anufriev
    alexey-anufriev
    on Aug 25, 2026
    Author

    Both, A and B work correctly, window is now placed as it should be. Also no errors in the logs.

    Here is GPU info:

    01:00.0 VGA compatible controller: NVIDIA Corporation GA102 [GeForce RTX 3080 Ti] (rev a1)
        Subsystem: ASUSTeK Computer Inc. Device 8802
        Kernel driver in use: nvidia
        Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia

  22. afonsojramos commented on Aug 26, 2026

    @afonsojramos
    afonsojramos
    on Aug 26, 2026
    Member

    @alexey-anufriev Thank you, that isolated it exactly. Option A is what I've implemented.

    The cause was Vulkan, as your first log hinted. Chromium skips Vulkan under Wayland because the two are incompatible, then initialises it once X11 is in play, and on the NVIDIA proprietary driver that segfaults the GPU process (exit_code=139 is SIGSEGV).

    I went with A over B because both fixed the placement, but --disable-gpu would throw away all hardware acceleration to work around one broken code path. Enabling the setting now applies --ozone-platform=x11 --disable-features=Vulkan together.

  23. afonsojramos
    closed this as completedin #3218on Aug 26, 2026

  24. alexey-anufriev commented on Aug 26, 2026

    @alexey-anufriev
    alexey-anufriev
    on Aug 26, 2026
    Author

    Thank you @afonsojramos. I have just updated to 7.6.0 and can confirm that it works as expected now. Appreciate your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    fix-upstreamWhen the resolution is in an upstream package/libraryplatform:linuxRelated to linux build

    Type

    Bug

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions