[kde] [Bug 422248] New: VLC sometimes doesn't open to play a file

toni_rocha bugzilla_noreply at kde.org
Sat May 30 02:37:25 BST 2020


https://bugs.kde.org/show_bug.cgi?id=422248

            Bug ID: 422248
           Summary: VLC sometimes doesn't open to play a file
           Product: kde
           Version: unspecified
          Platform: Neon Packages
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: antonioni.rocha at gmail.com
  Target Milestone: ---

Created attachment 128925
  --> https://bugs.kde.org/attachment.cgi?id=128925&action=edit
Command in VLC menu "Properties for vlc.desktop"

SUMMARY
The VLC application sometimes don't open when I click in VLC icon or I try open
a video by VLC. No error is shown.

STEPS TO REPRODUCE
Obs: it hasn't a pattern to reproduce this problem, it occurs in aleatory
moments more frequently after I has open many videos.
1. Click in the VLC icon to run it, or click in a video file to show it in VLC.
2. The clock pointer works for a little moment, but VLC doesn't open.
3. Observe in the System Monitor application a zombie VLC process.
4. It only open if restart or logoff/login in Neon.

OBSERVED RESULT
The VLC application doesn't open and no error appears.

EXPECTED RESULT
The VLC application shoud appear.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION
A) I know that the command to run VLC in Neon is "/usr/bin/vlc
--started-from-file %U" (in "Edit application > Application" popup from VLC in
Application Menu).
If I edit it to "/usr/bin/vlc" the problem disappears. But it is a workaround
solution. If I run "vlc" or "/usr/bin/vlc" in terminal it works too.

B) I didn't found the exact product and component to select for specify this
bug, sorry if it has incorrect options.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list