Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

application mysteroisly eats output #14886

Open
6 tasks done
solomoncyj opened this issue Sep 19, 2024 · 4 comments
Open
6 tasks done

application mysteroisly eats output #14886

solomoncyj opened this issue Sep 19, 2024 · 4 comments

Comments

@solomoncyj
Copy link

mpv Information

mpv 0.37.0 Copyright © 2000-2023 mpv/MPlayer/mplayer2 projects
libplacebo version: v6.338.2
FFmpeg version: 6.1.2
FFmpeg library versions:
   libavutil       58.29.100
   libavcodec      60.31.102
   libavformat     60.16.100
   libswscale      7.5.100
   libavfilter     9.12.100
   libswresample   4.12.100

Important Information

- Platform version:
Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.9-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i7-4510U CPU @ 2.00GHz
Memory: 15,0 GiB of RAM
Graphics Processor: 
Manufacturer: Hewlett-Packard
Product Name: HP ProBook 430 G2
System Version: A3009C510002
- GPU model, driver and version: Mesa Intel® HD Graphics 4400, 
- Source: fedora dnf repo
- Introduced in version: ???

Reproduction Steps

mpv 'https://www.youtube.com/watch?v=Ud73fm4Uoq0' --no-video

Expected Behavior

text to appear normaly, and not get eaten

Actual Behavior

at around 2:30, stdout above the lyrics are 'eaten'

Log File

output.txt

Sample Files

No response

I carefully read all instruction and confirm that I did the following:

  • I tested with the latest mpv version to validate that the issue is not already fixed.
  • I provided all required information including system and mpv version.
  • I produced the log file with the exact same set of files, parameters, and conditions used in "Reproduction Steps", with the addition of --log-file=output.txt.
  • I produced the log file while the behaviors described in "Actual Behavior" were actively observed.
  • I attached the full, untruncated log file.
  • I attached the backtrace in the case of a crash.
@CounterPillow
Copy link
Contributor

Don't run the thing in the above comment, it's part of some malware spam campaign.

@solomoncyj
Copy link
Author

Don't run the thing in the above comment, it's part of some malware spam campaign.

-could you please mark it as spam

@CounterPillow
Copy link
Contributor

I can't as I don't have the permissions for doing that, but I have asked people with the permissions to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants
@CounterPillow @solomoncyj and others