I have a remote system that I want KRFB to run on all the time, however When I start KRFB manually it will work fine. However when I reboot the system it would always crash. I then can start it manually and it work fine.

Following the instructions in this thread.. viewtopic.php?f=17&t=84272&p=139829&hilit=krfb+startup#p139829
I decided to put it in autostart as krfb -nodialog but when I reboot it will not start. I then added krfb as the exception to the session manager as suggested and still the same issue.

However if I open shell and type krfb -nodialog it will start fine. Does anyone have any suggestions on why it wont autostart and/or why it crashes at startup?

Thanks,

Can you please generate a backtrace for that crash using the Crash Handler and file a bug report at bugs.kde.org?

You may wish to try adding a script to ~/.kde4/Autostart which will sleep for 30 seconds before running krfb.

Sure I would love to. You will just need to tell me what to do. (Sorry am still rather new to this).

Open KWrite, and enter the following:

Code: Select all

sleep 30s && krfb -nodialog &

Then save it to a file under ~/.kde4/Autostart named "start-krfb.sh"

Then open Konsole and run "chmod +x ~/.kde4/Autostart/start-krfb.sh"

That seemed to work. So I guess the autostart is just running it to fast. Which makes sense because when I would start it manually it would always work okay. Do you still need me to file a bug report. If so what is the best way of doing it. I got the text from the crash log but don't know if it is enough data for you or not. Should I post it on here?

You can post the backtrace here. The crash handler should assess the backtrace for you, those with 3 stars should definitely have a bug filed at bugs.kde.org, as that is a very good trace.

The bug report still should be filed.

This is what it gave me... (Please note this was the error I would get on the autostart before I tried what you told me) Now it is working fine.

Application: Desktop Sharing (krfb), signal: Segmentation fault
[KCrash Handler]
#5 0x00007f80cd88c397 in QDBusAbstractInterface::callWithArgumentList(QDBus::CallMode, QString const&, QList<QVariant> const&) () from /usr/lib64/libQtDBus.so.4
#6 0x00007f80d0bc91aa in ?? () from /usr/lib64/libkdnssd.so.4
#7 0x00007f80d0bc86e4 in ?? () from /usr/lib64/libkdnssd.so.4
#8 0x00007f80d0bc8b96 in ?? () from /usr/lib64/libkdnssd.so.4
#9 0x00007f80cef65aef in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4
#10 0x00007f80d0bcabc3 in ?? () from /usr/lib64/libkdnssd.so.4
#11 0x00007f80d0bcac6b in ?? () from /usr/lib64/libkdnssd.so.4
#12 0x00007f80cd87c9a6 in ?? () from /usr/lib64/libQtDBus.so.4
#13 0x00007f80cd88743f in ?? () from /usr/lib64/libQtDBus.so.4
#14 0x00007f80cef62a29 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#15 0x00007f80cf89276c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#16 0x00007f80cf898d6b in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#17 0x00007f80d0777f8e in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#18 0x00007f80cef52cec in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#19 0x00007f80cef55467 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#20 0x00007f80cef7c693 in ?? () from /usr/lib64/libQtCore.so.4
#21 0x00007f80cc456860 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f80cc45a6c8 in ?? () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f80cc45a87c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f80cef7c1d3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#25 0x00007f80cf94153e in ?? () from /usr/lib64/libQtGui.so.4
#26 0x00007f80cef51612 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#27 0x00007f80cef519ec in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x00007f80cef5572b in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#29 0x000000000040c0f7 in _start ()

Please file a bug report, including that backtrace, as it is sufficient to determine the problem. It is probable that Avahi isn't ready for use when your system automatically logs in, which KRFB should handle gracefully.

Okay I just created a bug report ( Bug 231619 ). I am not sure if I told you guys before, so in case I hadn't I wanted to say that I really appreciate all the hard work you do. I am finally now able to happily use Linux full time at home instead of Windows. I love KDE and look forward to learning it more and seeing it continue to improve as well as helping in what small ways I can.