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

            Bug ID: 468346
           Summary: Invalid .desktop files can crash plasmashell when
                    trying to edit them from kickoff.
    Classification: Plasma
           Product: plasmashell
           Version: 5.27.4
          Platform: Archlinux
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: generic-crash
          Assignee: plasma-b...@kde.org
          Reporter: david.alejandro.ru...@gmail.com
  Target Milestone: 1.0

Created attachment 157985
  --> https://bugs.kde.org/attachment.cgi?id=157985&action=edit
use this to reproduce issue

SUMMARY
Pretty much the title. If the Exec= file of a .desktop file contains ' at the
start and end, AND the application contains switches (--example), plasmashell
will segfault when trying to edit them (right click, "edit application") from
the kickoff menu.

I haven't been able to get debug logs yet, but so far two people I know have
been able to reproduce this issue. A file is attached to this bug report which
should reproduce it.

The main issue here is that that "Edit Application" dialog is what added the
single commas to the start and end of the Exec line, therefore making it
possible for someone to make an application invalid and be unable to edit it if
they're unaware of the location of the desktop file on the filesystem (this
could be a separate bug, let me know)

STEPS TO REPRODUCE
1. Create a .desktop file with an Exec line that starts and ends on a single
comma (') and that contains command line switches (--example)
2. Open kickoff, search the malformed .desktop file and right click it,
selecting Edit Application

OBSERVED RESULT
plasmashell segfaults

EXPECTED RESULT
no crash occurs, instead plasmashell should let 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux 6.2.10-arch1-1 (64-bit)
(available in About System)
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
A file is attached to this bug report which should reproduce the issue
described.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to