Screen share: top strip of the stream flickers / shows another frame #589
Open
opened 2026-11-15 05:34:45 +00:00 by charles
·
12 comments
No Branch/Tag specified
main
camera
dailyuse
textchat
fix-1008-idle-in-voice
camera-21-acceptance
feat-1000-app-sounds-output
fix-1001-local-time
camera-20-parity-list-for-the
fix-931-silent-voices
camera-15-ui-settings-voice-video
camera-14-ui-camera-buttons-camera
camera-16-ui-layout-with-cameras
camera-17-core-toggle-camera-shortcut
camera-13-ui-mirrored-video-and
camera-12-appsfluxer-camera-runtime-and
camera-10-capture-camera-on-linux
camera-11-capture-camera-on-windows
camera-9-voice-the-camera-track
camera-7-core-the-own-camera
camera-6-capture-camera-trait-mode
camera-8-core-remote-cameras-tile
camera-3-spike-a-camera-track
camera-4-video-camera-formats-and
camera-18-devserver-camera-scenario
camera-1-spike-capture-linux
camera-5-core-camera-ports-commands
camera-2-spike-capture-windows
camera-plan
shell
fix-925-keybinds-persist
feat-934-935-stream-view
feat-933-stream-output-device
shell-44-acceptance
feat-946-select-message-text
shell-43-parity-list-for-the
fix-589-black-band-linux-sender
shell-37-ui-system-wide-shortcuts
shell-ship
fix-931-voices-silent-after-long-uptime
shell-39-ui-settings-notifications
shell-36-ui-settings-keybinds
shell-16-core-autostart
fix-923-late-publication-next-share
fix-921-share-teardown-publish-race
shell-1-spike-iced-daemon-hide
shell-10-core-instance-messages-tasks
shell-11-core-keybinds-actions-combos
shell-13-core-badge-attention-sound
shell-14-core-notification-settings-inactive
shell-18-platform-desktop-entry-and
shell-2-spike-tray-on-linux
shell-3-spike-wayland-global-shortcuts
shell-41-devserver-shell-scenario
shell-5-spike-overlay-technique-for
shell-6-core-shell-ports-settings
shell-7-platform-settings-shell-keybinds
shell-8-core-tray-model-and
shell-9-core-window-rules-close
fix-913-keep-awake-retry
shell-35-ui-in-window-voice
shell-sync-textchat
shell-34-app-shortcuts-runtime
fix-913-keep-screen-awake
fix-910-deepfilter-windows-timing
shell-33-app-shell-runtime
shell-28-platform-shortcuts-on-wayland
fix-910-deepfilter-late-frame
shell-29-platform-shortcuts-by-direct
shell-27-platform-shortcuts-on-x11
shell-17-platform-single-instance
shell-24-platform-badge-displays-and-24
shell-26-platform-shortcuts-on-windows
shell-21-platform-tray-on-linux
shell-22-platform-tray-on-windows
fix-908-flaky-stream-end-test
shell-30-platform-wayland-activation
shell-38-ui-settings-desktop
shell-19-platform-autostart
shell-25-platform-shortcut-back-end
shell-23-platform-badge-displays-and
shell-40-ui-companion-apps-control
shell-31-statusapi-default-avatars
shell-12-core-system-wide-shortcut
shell-20-platform-tray-trait-icons
shell-32-ui-daemon-window-lifecycle
shell-4-spike-raising-a-wayland
shell-15-core-status-payload-gaps
fix-876-share-resolution-and-bars
shell-42-packaging-windows-shortcuts-and
fix-874-tests-must-not-notify
fix-868-deepfilternet-start
gamenight-plan
fix-867-869-stream-end-soundboard-limits
feat-229-windows-hardware-encoding
fix-857-vaapi-hardware-encoding
fix-849-inert-cards
fix-848-pinned-messages-clickable
shell-plan
fix-764-nvenc-above-720p30
serveradmin
feat-780-forum-archived-filter
serveradmin-35-acceptance
feat-781-no-join-chime-with-entrance-sound
feat-784-rejoin-voice-after-update
fix-779-782-search-dropdown-paste-preview
fix-783-781-dm-rail-entrance-sound
serveradmin-34-parity-screenshots
serveradmin-31-ui-channel-permissions
fix-773-cargo-deny-advisories
serveradmin-33-ui-sudo-delete-transfer
serveradmin-28-ui-members-page
serveradmin-26-ui-role-permissions
serveradmin-30-ui-voice-overview-channel-invites
serveradmin-fix-27-29
serveradmin-25-ui-roles-tab
serveradmin-27-ui-menus-moderation-modals
serveradmin-29-ui-channel-settings
fix-589-stream-top-strip-encode
serveradmin-24-ui-moderation-invites-bans
feat-760-version-in-title
fix-751-stream-audio-pipewire
serveradmin-20-core-menu-rows
fix-752-linux-notification-panic
serveradmin-17-core-overrides
fix-740-updater-always-latest
serveradmin-23-ui-community-settings-overview
serveradmin-12-core-roles
serveradmin-19-core-sudo-delete-transfer
serveradmin-32-ui-sidebar-drag
serveradmin-15-core-members-page
serveradmin-16-core-channel-settings
serveradmin-14-core-bans-invites
fix-615-restore-on-stored-session-start
serveradmin-22-runtime
serveradmin-13-core-member-moderation
serveradmin-18-core-channel-reorder
fix-732-status-api-speaking
serveradmin-10-core-permission-lists
serveradmin-11-core-forms-community
serveradmin-21b-devserver-channels-members-sudo
serveradmin-4-api-community-roles-sudo
serveradmin-9b-core-hierarchy-bulk-events
serveradmin-21a-devserver-community-roles
serveradmin-9a-core-ports
serveradmin-8-form-widgets
serveradmin-5-api-channels-members-bans
serveradmin-7-settings-shell
serveradmin-1-proto-community-roles
serveradmin-3-proto-members-bans-invites
serveradmin-6-reorder-widget
serveradmin-2-proto-channel-admin
fix-706-presence-after-reconnect
fix-615-start-on-last-view
feat-663-create-channel
serveradmin-plan
fix-662-long-text-wrap
fix-660-661-menu-toolbar-paste-focus
fix-620-forum-list-reactions
fix-657-windows-console
fix-622-emoji-in-names
fix-smoke-645-648
fix-614-install-location
dailyuse-41-acceptance
fix/597-copy-id
dailyuse-40-parity-screenshots
dailyuse-35-ui-quick-switcher-keybinds
dailyuse-38-ui-profile-modal
fix/voice-view
fix/side-panel-composer
dailyuse-37b-ui-composer-barriers-blocked
fix/image-viewer
fix/619-picker-flicker
fix/editor-forum-edit
dailyuse-32-ui-status-picker
dailyuse-34b-ui-add-guild-invite-modal
dailyuse-28-app-dailyuse-runtime
dailyuse-36-ui-voice-badge-refusals
fix/594-menu-placement-textchat
fix/589-stream-top-strip
fix/594-menu-placement
dailyuse-39-ui-report-modal
dailyuse-37a-ui-attachment-audio-group-icon
dailyuse-24-core-notification-icon-passive
fix/587-quiet-voice
dailyuse-30-ui-notification-settings-modal
dailyuse-31-ui-user-dm-menus
dailyuse-22b-core-composer-barriers-blocked
dailyuse-22a-core-mark-unread-attachments
dailyuse-29-ui-channel-guild-menus
dailyuse-18-core-user-dm-menus
dailyuse-33-ui-confirm-friends-page
dailyuse-22c-core-trusted-domains-hide-muted
dailyuse-20-core-keyboard-navigation
dailyuse-15-core-friends-blocking
dailyuse-23-core-profile-report-flow
dailyuse-19-core-quick-switcher
dailyuse-14-core-status-idle-presence
dailyuse-17-core-channel-guild-menus
ci/27-linux-cache
dailyuse-37c-ui-trust-links-hide-muted
dailyuse-13-core-honour-mutes
dailyuse-34a-ui-invite-cards-accept
dailyuse-16b-core-create-invites-guilds
dailyuse-12-core-notification-settings-mutes
dailyuse-16a-core-invite-links
dailyuse-25-audio-attachments
dailyuse-21-core-voice-refusals
dailyuse-11b-core-state-skeleton
dailyuse-11a-core-dailyuse-ports
dailyuse-26b-devserver-dailyuse-b
dailyuse-26a-devserver-dailyuse-a
dailyuse-4-api-settings-acks-reports
dailyuse-5-api-relationships-invites-guilds
dailyuse-27-platform-notification-idle
dailyuse-10-highlight-languages
fix-search-focus-hover-emoji
dailyuse-8-context-menu-widget
dailyuse-9-image-load-retry
dailyuse-7-chat-navigation-persistence
dailyuse-2-proto-relationships-invites-reports
dailyuse-1-proto-notification-presence
dailyuse-6-gateway-op12-presence
textchat-next
fix-stream-black
fix-reactions-hover
textchat-68-app-video-playback-runtime
textchat-35-acceptance
textchat-34-parity-screenshots
textchat-74-app-updater-runtime
textchat-67-ui-video-player
textchat-stage-46-47
textchat-47-ui-media-channel
textchat-75-promote-stable-workflow
textchat-46-ui-forum-composer
textchat-73-ui-update-button
textchat-64-media-playback-crate
textchat-stage-43-48
textchat-72-platform-updater
textchat-44-ui-thread-view
textchat-70-release-update-feed
textchat-48-ui-announcements
textchat-45-ui-forum-view
textchat-71-core-updater
textchat-43-ui-sidebar-links-notes
textchat-stage-40
textchat-42-app-channel-types-runtime
textchat-39-core-forums
textchat-40-core-announcements-thread-admin
textchat-60-ui-entrance-sounds
textchat-63-ffmpeg-lgpl-packaging
textchat-stage-batch6
textchat-69-proto-update-manifest
textchat-61-app-soundboard-entrance-runtime
textchat-52-app-audio-devices-runtime
textchat-38-core-channel-routing
soundboard-effect-emoji
status-api-rebind
textchat-28-ui-gif-picker
textchat-41-devserver-channel-types
voice-panel-soundboard
textchat-29-ui-message-actions
textchat-37-api-channel-types
textchat-66-core-video-players
autoupdate-plan
textchat-33-ui-message-list-settings
textchat-32-ui-dms
textchat-62-rename-flaxative
fix-chatcolumn-tree
textchat-65-audio-media-source
textchat-31-ui-threads
textchat-stage-27
textchat-30-ui-search-pins-inbox
textchat-53-ui-audio-sources-menu
textchat-27-ui-expression-picker
textchat-57-core-entrance-library
textchat-36-proto-channel-types
textchat-26-ui-upload-tray
textchat-59-ui-soundboard-popout-parity
textchat-58-audio-sound-edit
textchat-55-proto-api-entrance-library
textchat-25-ui-composer
textchat-56-core-soundboard-parity
rename-video-plan
textchat-stage-25
textchat-stage-23-24
soundboard-plan
textchat-24-ui-message-row
textchat-22-ui-attachments-media
textchat-23-ui-embeds
textchat-14-core-expressions
textchat-21-app-textchat-runtime
textchat-16-core-navigation-read
textchat-17-core-search
textchat-19-core-dms-settings
textchat-stage-13-15-18
textchat-54-livekit-stereo-audio
textchat-50-core-stream-audio-sources
textchat-12-core-uploads
textchat-15-core-message-actions
textchat-11-core-composer
textchat-18-core-threads
textchat-13-core-reactions
textchat-51-audio-pipewire-devices
textchat-49-capture-audio-targets
audio-plan
textchat-plan2
textchat-20-devserver-textchat
textchat-6-api-chat-endpoints
textchat-10-core-chat-ports
textchat-9-ui-code-highlighting
textchat-3-proto-expressions-threads-prefs
textchat-5-api-messages-uploads
textchat-2-proto-chat-requests-events
textchat-8-ui-inline-flow-emoji
screenshare
textchat-7-platform-files-clipboard
textchat-1-proto-message-content
textchat-4-emoji-crate
screenshare-31-acceptance
screenshare-29-parity-screenshots
textchat-plan
screenshare-24-ui-focus-layout
screenshare-27-ui-stream-menu
screenshare-30-packaging-ci
screenshare-21-app-screenshare-runtime
screenshare-22-ui-sidebar-live
screenshare-23-ui-stream-tile
screenshare-26-ui-source-picker
screenshare-28-ui-screenshare-settings
screenshare-13-core-previews
screenshare-12-core-codec-negotiation
screenshare-25-ui-share-controls
screenshare-18-hw-encode-linux
screenshare-19-spike-hw-encode-windows
screenshare-11-core-stream-params
screenshare-20-devserver-screenshare
screenshare-10-core-go-live
screenshare-17-voice-livekit-video
screenshare-14-audio-capture-linux
wip/screenshare-17
screenshare-integration
feat-user-profile
fix-voice-join
feat-entity-images
screenshare-16-voice-video-session
screenshare-9-core-watching
screenshare-5-capture-windows
fix-wire-livekit
screenshare-4-capture-linux
screenshare-15-audio-capture-windows
fix-member-list
screenshare-8-core-stream-ports
fix-live-protocol
screenshare-6-ui-video-widget
screenshare-3-capture-crate
fix-altcha-captcha
screenshare-1-video-frames
screenshare-7-proto-api-streams
screenshare-2-spike-livekit-video
voice
voice-26-acceptance
voice-23-voice-e2ee
voice-25-packaging-ci
voice-13-voice-livekit-interop
voice-24-parity-screenshots
voice-19-ui-soundboard
voice-20-ui-participant-menu
voice-22-ui-dm-calls
voice-21-ui-voice-settings
voice-18-ui-call-view
voice-14-app-voice-runtime
voice-10-core-soundboard
voice-17-ui-voice-panel
voice-9-core-voice-settings-advert
voice-5-audio-clips-chimes
voice-15-devserver-voice
voice-8-core-live-room-volumes
voice-11-core-calls-status
voice-12-voice-session
voice-4-audio-devices-mixer
voice-16-ui-voice-sidebar
voice-7-core-voice-connection
foundation
voice-2-proto-api-soundboard-rtc
voice-6-core-voice-states
voice-3-audio-dsp
voice-1-proto-voice-gateway
task/26-acceptance
task/25-packaging-release
task/24-screenshot-tests
task/20-ui-message-list-composer
task/22-ui-settings-parity
task/18-ui-main-layout
task/23-notifications
task/17-ui-shell-login
task/14-app-runtime
ci/51-windows-disk-space
task/12-platform-persistence
task/13-devserver
task/21-ui-avatar-image-cache
task/10-core-messages-readstate
task/9-core-guilds-channels
task/7-gateway-machine-transport
task/11-core-presence-ui
task/19-ui-rich-text
task/8-core-store-session
task/16-ui-theme-fonts-icons
task/15-status-api
task/4-proto-gateway-events
task/5-openapi-vendor-contract
task/6-api-client
task/3-proto-rest-models
task/2-proto-primitives
task/1-workspace-scaffold
nightly
native-2026.1120.417
native-2026.1119.408
native-2026.1119.406
native-2026.1119.401
native-2026.1119.395
native-2026.1118.390
native-2026.1118.383
ci-log-382-release-windows
native-2026.1118.379
native-2026.1118.377
native-2026.1118.375
native-2026.1118.373
native-2026.1118.371
native-2026.1118.369
native-2026.1117.366
native-2026.1117.364
native-2026.1117.362
native-2026.1117.359
native-2026.1117.355
native-2026.1116.353
native-2026.1116.350
native-2026.1116.347
native-2026.1116.345
native-2026.1116.343
native-2026.1116.341
native-2026.1116.339
native-2026.1116.337
native-2026.1115.335
native-2026.1115.332
native-2026.1115.330
native-2026.1115.328
native-2026.1115.326
native-2026.1115.323
native-2026.1115.321
native-2026.1115.318
native-2026.1115.314
native-2026.1115.307
native-2026.1115.304
native-2026.1114.302
native-2026.1114.297
native-2026.1114.291
native-2026.1114.290
native-2026.1113.288
update-feed
native-2026.1113.301
native-2026.1113.266
native-2026.1113.262
ffmpeg-8.0.3-r1
Labels
Clear labels
bug
A bug found while working on something else; steps to reproduce and the commit seen on
ci
Build, CI runners and workflows
follow-up
Deferred reviewer finding, linked from the PR it came from
good-first-task
Small, well-scoped, no cross-crate knowledge needed
parity
Settings/behaviour parity with the Electron client
question
Design question that needs Charles; blocks its task until answered
ready-to-merge
Reviewer approved, foundation merged in, CI green on both runners; waiting for the orchestrator to merge
task
A plan task (one per Foundation plan task)
No labels
bug
ci
follow-up
good-first-task
parity
question
ready-to-merge
task
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".
No due date set.
Dependencies
No dependencies set.
Reference
charles/fluxer-native#589
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?
Report (Charles, 2026-11-15). Watching a screen share sent from Flaxative, a strip at the top of the stream (roughly the top fifth) flickers: sometimes black, and it looks out of step with the rest of the picture, "as if I'm seeing 1/5 of the next frame too quickly". It looks the same as the artifact seen with the Electron app. A screenshot never shows it: the screenshot always contains a complete frame.
Viewer machine. CachyOS, KDE Plasma on Wayland, NVIDIA RTX 5090 (driver 620.70), two 4K monitors at 120 Hz and 160 Hz, scale 1.45, VRR "Automatic", KWin
AllowTearing=false. Sender's OS not stated.What that suggests. With tearing off in the compositor, a strip of another frame should not come from the display. A transient mix of two frames inside one presented image points at a race on the frame's pixels somewhere between the source and the texture:
fluxer-voicertc.rs, theFrameBus, the conversion to the texture format, plane-by-plane uploads influxer-ui).To do — measure first.
fluxer-capturefrom a source that changes every refresh.Findings (measured), PR #607
Cause found on the sender side (Linux/Wayland), hypothesis 2. libwebrtc's PipeWire capturer hands us a share of one of the two frames in its stream queue. Its PipeWire thread writes a new picture into that same frame two buffers later, even while we are still reading it: it only logs a debug warning, "Overwriting frame that is still shared" (
shared_screencast_stream.ccat the pinnedwebrtc-a545de4, l. 698 and l. 915–917).fluxer-captureconverted that frame to I420 in place (crates/fluxer-capture/src/desktop/rtc.rs, thestart_capturecallback). A 4K frame takes long enough to convert that the writer sometimes overtakes the read position, so the frame comes out with its top part from one picture and the rest from the picture two buffers later. That frame is then encoded, so every viewer sees it (Chromium/Electron uses the same capturer). It lasts one frame at a time, which is why screenshots miss it.How it was measured.
tools/capture-consistency/run.shruns headless: a private D-Bus session, a private PipeWire daemon, a stand-in ScreenCast portal, and a source whose frame n is one solid colour. The real Wayland capture path runs end to end and every frame is checked. Over 20 s per case, before the fix:In every mixed frame the two colours were two frames apart, which is the signature of the 2-frame queue. After the fix, all 7 configurations had 0 mixed frames out of 6,304.
Receive side is clean. Every received frame was checked, for AV1, H.264, VP9 and VP8, at 1080p30, 1080p60 and 1080p→720p mid-stream, with NVDEC and with
LK_DISABLE_NVDEC=1, with and without CPU load. That is 56 runs, about 18,900 frames, with 0 mixed and 0 black top strips. The FrameBus and the widget upload were audited and are safe: frames are immutableArcplanes, and all three planes are written withwrite_texturebefore the draw. So hypotheses 1 and 3 are not the cause, and nothing needs to change for H.264 decoding for this issue.Fix. The capture callback now copies the pixels, checks the copy against the frame, pulls again if the frame changed (at most 3 retries) and converts the copy. The cost is one extra copy and compare per frame. At 4K60 on this loaded machine that meant about 23 % fewer frames delivered.
Not reproduced: the black strip. No configuration produced one. The headless source uses MemFd buffers. KWin normally uses DMA-BUF, and libwebrtc reads those back without any explicit sync (it negotiates no
SPA_META_SyncTimeline). That could explain the black strip on drivers without implicit sync, but it can't be tested without a compositor. Also not covered: a Windows sender (audited only: WGC fills its frames on our capture thread, so this race can't happen there) and the sender's actual OS, which isn't stated here.To confirm on the real machines, run Flaxative with
FLUXER_FRAME_CHECK=1on both the sender and the viewer. Each frame whose top fifth is black while the rest is not gets awarnlog line:side = "captured"on the sender, before encoding, andside = "received"on the viewer, after decoding. Totals are logged every 600 frames.Reopened 2026-11-16. Charles on nightly 2026.1116.341 (the capture fix of PR #607 has been in every nightly since 2026.1115.307): "The black bar still shows up during the streams". So #607 did not fix what he sees, or fixed only one of several causes. It was never confirmed in real use.
Not yet known, and needed before another fix: who was streaming and with which client (Flaxative, the Electron app or the web app), who saw the bar (the streamer in their own preview, or the viewers) and in which client, and whether it is at the top edge only. His log of that session shows him sharing from Flaxative on Linux (SystemPicker, 1920x1046 then 1920x1080, 60 fps, H264, hardware=true, encoder Auto) and no stream-watching lines, so the bar was presumably seen by viewers or in his own preview.
If the streamer was Flaxative with the hardware encoder, the capture copy fixed in #607 is no longer the only suspect: the hardware encode path (frame upload / surface reuse before the encoder has read it) and the viewer-side decode and upload are candidates. Use FLUXER_FRAME_CHECK=1 and a recorded stream to locate the stage.
2026-11-16, more from Charles: every viewer sees the bar on his shares (Flaxative on Linux, H264, hardware encoder). A stream he watched from someone else's machine, in Flaxative, showed no bar. So the viewer side of Flaxative displays a clean stream cleanly, and the defect is tied to the sending side on his machine (capture, conversion or hardware encode), possibly intermittent. Diagnosis continues; no fix has shipped since #607.
PR #763 is merged. This time the defect was measured and measured gone, in a headless setup that copies the reporter's sender (DMA-BUF capture from an NVIDIA GPU, 1080p and 1046p at 60 fps, H.264 6 Mbit/s):
glReadPixelsbeing descheduled under CPU pressure). The frame handed on has the top 6–901 rows of a picture 2–5 frames later. It happens before conversion and encoding, only with DMA-BUF capture and a busy CPU.FLUXER_FRAME_CHECK=1now also checks the frame handed to the encoder and logs per-pull decisions;FLUXER_CAPTURE_VERIFY_LATEST=0turns the fix off for an A/B test.Kept open until the reporter confirms in a real share on his KWin session, which was not driven here.
The fix of PR #763 is in nightly 2026.1116.350. Open until the reporter confirms on a real share.
2026-11-17, from Charles: the share where the top of the frame was still scrambled (seen by him as a viewer, after nightly 350) came from another user, not from his machine. Not yet known: that sharer's client (Flaxative, Electron, web), version and OS.
Why it matters: the fix of PR #763 is only in Flaxative nightlies from 2026.1116.350, and only on the Linux Wayland-portal capture path (X11 and Windows skip the second look). If the sharer was on Flaxative for Windows, or on an older nightly, or on the Electron/web client (which has this artefact by itself), the fix was never in play. Charles's own shares from Linux have not been tried since the fix.
2026-11-18, from Charles: the sharer of the still-scrambled stream was on Linux, Flaxative around nightly 353, so they had the fix of PR #763 (in from 350). So the fix did not cover their setup. What differs from the measured setup is not yet known. The fix's second look runs only on the Wayland portal capture path (X11 skips it), and the measured case was DMA-BUF from an NVIDIA GPU; another GPU, an X11 session, or the SHM path under a different compositor could behave differently.
Needed from the sharer:
echo $XDG_CURRENT_DESKTOP $XDG_SESSION_TYPE), GPU and driver (glxinfo -B | headorlspci | grep -i vga).~/.local/state/flaxative/logs/flaxative.<date>.log. The lines of interest: the PipeWire format (aModifier:line means DMA-BUF), the per-pull trace (trusted / torn / dropped), the torn-frame checker's findings as captured and as handed to the encoder, andvoice: screen share encoder implementation=.FLUXER_CAPTURE_VERIFY_LATEST=0added, to see whether the fix changes anything for them.2026-11-18: Charles is watching a share from a Windows user in Flaxative: the top of the frame is not scrambled so far (client and version of the sharer not yet known). So no sign of the artefact on the Windows capture path in this session; the open case remains the Linux sharer on ~nightly 353.
2026-11-18: the sharer of #876 (Linux Wayland, RTX 4080, 3440×1440 monitor, nightly 2026.1118.373 per the owner) still sees the top strip, so #763 is present and does not cover their case.
Tried at 3440×1440 on textchat head (PR #879's runs):
run.sh --chain, MemFd and DMA-BUF (tiled modifier, stride 13760, no row padding), NVENC and OpenH264, at 1080p, 1440p and Source, 20–55 s each,FLUXER_FRAME_CHECK=1, no synthetic load. Compared with 1920×1080 and 2560×1440.Result: not reproduced.
Needed from the sharer: a share with
FLUXER_FRAME_CHECK=1 FLUXER_LOG=info,fluxer_capture=debug, specifically:Modifier:);side = \"captured\"and at the encoder input.If those stay at 0 while viewers see the strip, the cause is after capture.
Charles captured the artefact in a screenshot on 2026-11-19 (not attached: it shows another member's screen).
Measured on the screenshot (1460x1254, scaled from the stream view): the stream shows a browser window. Rows 45-67 are solid black across the full width (about 22 rows, 1.8% of the height, starting 3.6% from the top), directly under the browser's toolbar and cutting the page's own header line in half. Above it the toolbar is drawn normally; below it the picture is normal. So the band is not at row 0 and it is black, not stale picture.
At 1440 source rows that is roughly rows 52-77, at 1080 roughly 39-58: about one to two 16-pixel block rows. That makes a lost or wrongly coded slice / block row in the encoder or decoder a candidate alongside the capture path. Still needed: who was sending (OS, GPU, screen or window share, chosen resolution), which client the screenshot was taken on, and whether the band flickers or stays.
Charles (2026-11-19): it does not happen when the sender is a Windows client, so this is a source-side problem on Linux senders, not the viewers. An agent is now investigating the Linux sending path (capture, fit/convert, encoder) with these facts.
The fix (#945) is in nightly 2026.1119.406: on Linux with the NVIDIA driver, screen capture now uses memory buffers instead of dmabuf. Not yet confirmed on an affected sender. To confirm, the Linux/NVIDIA person who shares runs
FLUXER_FRAME_CHECK=1 FLUXER_LOG=info,fluxer_capture=debug flaxative, shares for a few minutes and checks the log: it should showbuffers="MemFd" nvidia_driver=trueand no black-band warning. Stays open until then.