H@K3R 008
کاربر فعال
- ارسالها
- 32
- امتیاز
- 50
- نام مرکز سمپاد
- حلی
- شهر
- اردـــــبیل
- مدال المپیاد
- می خوانیم برا کامپیوتر ...!!!!
- رشته دانشگاه
- قراره نرم افزار باشه ... شاید
پاسخ : تاپیک سوالات لینوکس
کد:
kdevelop
WARNING: deleting stale lockfile /home/amirreza/.kde/share/apps/kdevelop/sessions//{b818801f-b16a-4aec-ac20-e8ac2e4b5141}/lock
WARNING: deleting stale lockfile /home/amirreza/.kdevduchain/{b818801f-b16a-4aec-ac20-e8ac2e4b5141}/0/lock
kdevelop(27953)/kdevplatform (language) KDevelop::ItemRepositoryRegistry::open: version-hint not found, seems to be an old version
kdevelop(27953)/kdevplatform (language) KDevelop::ItemRepositoryRegistry::open: "The data-repository at /home/amirreza/.kdevduchain/{b818801f-b16a-4aec-ac20-e8ac2e4b5141}/0 has to be cleared."
void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "F&ull Screen Mode" under id 71
kdevelop(27953)/kdevplatform (shell) KDevelop::PluginController::loadPluginInternal: Loading plugin ' "kdevkonsoleview" ' failed, KPluginLoader reported error: '
"No service matching the requirements was found" '
qrc:/main.qml:23:1: QML QDeclarativeRectangle_QML_0: Binding loop detected for property "areaName"
static bool QDeclarativeMetaType::isModule(const QByteArray&, int, int) Qt 4.7 import detected; please note that Qt 4.7 is directly reusable as QtQuick 1.x with no code changes. Continuing, but startup time will be slower.
QDeclarativeComponent(0x388f990)
QDeclarativeComponent(0x388f990)
kdevelop(27953)/kdevplatform (shell) KDevelop::SessionControllerPrivate::performRecovery: Starting recovery from "/home/amirreza/.kde/share/apps/kdevelop/sessions/{b818801f-b16a-4aec-ac20-e8ac2e4b5141}/recovery/current"
The program 'kdevelop' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 1090 error_code 3 request_code 20 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
register count: 0, destroy count 0:
