QTBUG-51112 [qbm] Window is glitchy

[Redsandro]

Description

When typing, I see glitches above the input box sometimes. It appears as if items are moved to the top of the input box before being removed from screen. All of this happens fast and you won't notice if your monitor refresh rate is 60 Hz or lower.

Technically speaking, it appears as if a draw() is performed while the state of the model is still updating, and then another draw() is performed once the update is complete. Or the location of the bottom of the list is moved up before the items are removed.

Expected behavior

Albert should not draw anything above the input box. Albert should not draw() the UI the state is complete.

Steps to reproduce

With the calculator module, typing 1+ shows a list of search engines. When pressing 1 to make 1+1, for one frame you can see the list of search engines above the input box before being removed.

Or simply pressing a and backspace. The items starting with a move from below the input box to above the input box for a fraction of a second before being removed from screen.

Please note that this doesn't happen with Widgets BoxModel. I just thought I'd report this. Feel free to close/disregard.

Source

0.22.2-0+557.1 from ppa

        Albert version: 0.22.2
            Build date: Aug 14 2023 20:53:25
            Qt version: 6.2.4
             Build ABI: x86_64-little_endian-lp64
  Arch (build/current): x86_64/x86_64
 Kernel (type/version): linux/5.15.0-79-generic
                    OS: Linux Mint 21.2
     OS (type/version): linuxmint/21.2
 $QT_QPA_PLATFORMTHEME: qt5ct
         Platform name: xcb
                  Font: Ubuntu,10,-1,5,400,0,0,0,0,0,0,0,0,0,0,1
       Binary location: /usr/bin/albert
                $SHELL: /bin/bash
                 $LANG: en_US.UTF-8
              Language: English
                Locale: en_US
     $XDG_SESSION_TYPE: x11
  $XDG_CURRENT_DESKTOP: X-Cinnamon
      $DESKTOP_SESSION: cinnamon
  $XDG_SESSION_DESKTOP: cinnamon
            Icon theme: Mint-L-Blue
00:12:54 [crit:albert] Application has not been terminated graciously
00:12:54 [debg:albert] Checking for a running instance…
00:12:54 [info:albert] There is another instance of albert running.

[ManuelSchneid3r]

can you please check the images in this bug: https://bugreports.qt.io/browse/QTBUG-51112?filter=-2
is this the glitch you get? or can you post a video?

[Redsandro]

@ManuelSchneid3r it's not that bad and doesn't look exactly the same, but similar, it would roughly match the description in that bug.

Enter 1+:

Enter 1. Frame 1 (fraction of a second):

Frame 2:

[ManuelSchneid3r]

Btw which CPU/GPU do you use?

[abudawud]

Same here, i'm using albert 0.22.15 and use BoxModel as the frontend

[ManuelSchneid3r]

@abudawud Run it from terminal using 'albert - d' and post chekc the runtimes of the handlers.

[abudawud]

@ManuelSchneid3r sure, here's it
albert.log

thanks for your help

[ManuelSchneid3r]

Did you encounter these kind of lags while writing this log? is it only the calculator? Which hardware are you using?

[abudawud]

1. Did you encounter these kind of lags while writing this log ? Yes, and the lags still happens although on normal mode
2. is it only the calculator ? No, it's happened on all handler. example when i type 'a' and erase it again
3. Which hardware are you using ? i don't know how to response this, which hardware ?

i think what @Redsandro said is right

Technically speaking, it appears as if a draw() is performed while the state of the model is still updating, and then another draw() is performed once the update is complete

[ManuelSchneid3r]

3. Which hardware are you using ? i don't know how to response this, which hardware ?

your gpu. or cpu if you are using integrated graphics.

[ManuelSchneid3r]

oh and please always update to the latest version before posting bugs.

[abudawud]

Sure here's the output:

> lspci -v | grep -i "VGA\|3D\|Display"
00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] (rev 02) (prog-if 00 [VGA controller])
01:00.0 3D controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] (rev a1)

> glxinfo | grep -i "device\|memory"
    Device: Mesa Intel(R) UHD Graphics 630 (CFL GT2) (0x3e9b)
    Video memory: 15843MB        
    Unified memory: yes                                                                                   
    GL_AMD_performance_monitor, GL_AMD_pinned_memory,  
    GL_EXT_framebuffer_object, GL_EXT_framebuffer_sRGB, GL_EXT_memory_object, 
    GL_EXT_memory_object_fd, GL_EXT_packed_depth_stencil, GL_EXT_packed_float, 
    GL_AMD_pinned_memory, GL_AMD_query_buffer_object,  
    GL_EXT_gpu_shader4, GL_EXT_memory_object, GL_EXT_memory_object_fd, 
    GL_EXT_instanced_arrays, GL_EXT_map_buffer_range, GL_EXT_memory_object, 
    GL_EXT_memory_object_fd, GL_EXT_multi_draw_arrays,     

> lshw -C display
  *-display                 
       description: 3D controller
       product: TU117M [GeForce GTX 1650 Mobile / Max-Q]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list rom
       configuration: driver=nouveau latency=0
       resources: irq:140 memory:a3000000-a3ffffff memory:90000000-9fffffff memory:a0000000-a1ffffff ioport:4000(size=128) memory:a4000000-a407ffff
  *-display
       description: VGA compatible controller
       product: CoffeeLake-H GT2 [UHD Graphics 630]
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       logical name: /dev/fb0
       version: 02
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
       configuration: depth=32 driver=i915 latency=0 resolution=1920,1080
       resources: irq:147 memory:a2000000-a2ffffff memory:80000000-8fffffff ioport:5000(size=64) memory:c0000-dffff

> inxi -G
Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] driver: i915 v: kernel
  Device-2: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] driver: nouveau
    v: kernel
  Display: x11 server: X.Org v: 21.1.9 with: Xwayland v: 23.2.2 driver: X:
    loaded: modesetting dri: iris,nouveau gpu: i915 resolution: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: iris,nouveau,swrast
    platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.3 vendor: intel mesa v: 23.1.9-manjaro1.1
    renderer: Mesa Intel UHD Graphics 630 (CFL GT2)

oh and please always update to the latest version before posting bugs.

I have used the most recent version, my albert version is 0.22.15 as reported in log above

[ManuelSchneid3r]

@abudawud please open a new issue since this is off topic here. The two frontends use an entirely different backend.

[abudawud]

@ManuelSchneid3r i have tried switch to QML Box Model (QBM) and it's glitch worse than WBM