[prev in list] [next in list] [prev in thread] [next in thread] 

List:       amarok-bugs-dist
Subject:    [amarok] [Bug 397351] New: Segfault after enabling script console
From:       Dan Dart <bugzilla_noreply () kde ! org>
Date:       2018-08-10 16:15:26
Message-ID: bug-397351-71684 () http ! bugs ! kde ! org/
[Download RAW message or body]

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

            Bug ID: 397351
           Summary: Segfault after enabling script console
           Product: amarok
           Version: 2.9.0
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: amarok-bugs-dist@kde.org
          Reporter: kde@dandart.co.uk
  Target Milestone: kf5

After enabling the script console

Message box:

A KDE text-editor component could not be found.
Please check your KDE installation.  Exiting the console!

and then a segfault report every time I start it, breaking it completely (with
no good segfault information, even with debug packages).

I don't think it's https://bugs.kde.org/show_bug.cgi?id=363176 as that's
related to writing files in the wrong place.

However, it can be worked around by using the same disable script console
method by editing /home/dwd/.kde/share/config/amarokrc.

-- 
You are receiving this mail because:
You are the assignee for the bug.=
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic