Summary: | error unable to find kde text editor | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | joe preacher <joe.preacher> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | office |
Priority: | NOR | Keywords: | drkonqi |
Version: | 2.9.0 | ||
Target Milestone: | kf5 | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
joe preacher
2018-10-20 23:49:02 UTC
The crash is not in Amarok, but in Qt. Did you install Amarok in Ubuntu or do you run a Kubuntu installation? Kubuntu uses different Qt libraries than Ubuntu does, might be the source of the problem. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! Created attachment 128676 [details]
New crash information added by DrKonqi
amarok (2.9.0) on KDE Platform 4.14.38 using Qt 4.8.7
- What I was doing when the application crashed:
i went through the amarok scrips option , and added a "console" amarok then suggested i need a text editor and crashed.
Amarok now crashes on start up
-- Backtrace (Reduced):
#7 0x00007f0011797c65 in ScriptConsoleNS::ScriptConsole::~ScriptConsole (this=0x55b07f3265c0, __in_chrg=<optimized out>) at ./src/scripting/scriptconsole/ScriptConsole.cpp:246
#8 0x00007f0011797ca9 in ScriptConsoleNS::ScriptConsole::~ScriptConsole (this=0x55b07f3265c0, __in_chrg=<optimized out>) at ./src/scripting/scriptconsole/ScriptConsole.cpp:247
#9 0x00007f000f236d38 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x00007f000f79fd9c in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#11 0x00007f000fb84323 in QMainWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
(In reply to Hippy Chris from comment #5) > Created attachment 128676 [details] > New crash information added by DrKonqi > > amarok (2.9.0) on KDE Platform 4.14.38 using Qt 4.8.7 > Which really doesn't help either, as there are no debugging symbols for Amarok or Qt in that backtrace, and as said previously: the crash is not in Amarok, but in Qt. Nothing we can do about. FWIW: Please do not post backtraces in closed bugs, even if Dr. Konqi suggests it is a duplicate. We never had an answer back from the OR, hence it is closed. You should always file a new bug, and make sure to have debugging symbols installed for Amarok and its dependencies to provide a useful backtrace. See also https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports |