Bug 193587 - k3b crashed at starting
Summary: k3b crashed at starting
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: Data Project (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2009-05-22 00:58 UTC by rodolphe robles
Modified: 2018-10-27 02:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rodolphe robles 2009-05-22 00:58:46 UTC
Version:           1.65.0 (using KDE 4.2.2)
OS:                Linux
Installed from:    Mandriva RPMs

When I try to open k3b, I could just see the presentation window a few second and then nothing. I try to write on a console the command "k3b" and I receive this message :

k3b(4615): ""Backgroundcolor" - conversion from "Window" to QColor failed" " (wrong format: expected '3' or '4' items, read '1')"

k3b(4615): ""Foregroundcolor" - conversion from "WindowText" to QColor failed" " (wrong format: expected '3' or '4' items, read '1')"

k3b(4615): ""Backgroundcolor" - conversion from "Window" to QColor failed" " (wrong format: expected '3' or '4' items, read '1')"

k3b(4615): ""Foregroundcolor" - conversion from "WindowText" to QColor failed" " (wrong format: expected '3' or '4' items, read '1')"

K3bQProcess::QProcess(0x0)
<unknown program name>(4612)/: Communication problem with  "k3b" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

[toto@localhost ~]$ KCrash: Application 'k3b' crashing...
Comment 1 Dario Andres 2009-05-22 03:44:12 UTC
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks
Comment 2 Dario Andres 2009-06-26 15:56:09 UTC
Marking as NEEDSINFO
Comment 3 Andrew Crouthamel 2018-09-25 03:46:04 UTC
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!
Comment 4 Andrew Crouthamel 2018-10-27 02:32:16 UTC
Dear Bug Submitter,

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!