Duncan wrote:
> Sagara Wijetunga posted on Fri, 08 Jan 2010 22:46:37 +0800 as excerpted:
>
>
>> Here are my side info:
>> HAL-0.5.13, Xorg 7.5, Qt-4.6.0, 32-bit x86, OS: FreeBSD 7.2 (Tomahawk
>> Desktop).
>>
>> Its only plasma-desktop crash. After the plasma-desktop crash, I can
>> press Alt-F2 and run krunner, from there I can select and run konsole.
>> The konsole screen appear but goes off, konsole does not crash. Since
>> konsole disappear, I cannot run anything any further.
>>
>
> I have no idea about FreeBSD or Tomahawk, as I rather prefer the down-to-
> the-user freedoms of the GPLs, so haven't messed with the BSDs on
> principle. They're still my free software bretheren and I respect them
> for that (unlike the proprietaryware folks, who won't respect my rights
> as an intelligent human, so I respect them about as I would a slave
> trader trying to ship me off... for the damage they can do and that's
> pretty much it), but it's not my personal choice...
>
> But hal-0.5.13... probably isn't an issue. Xorg shouldn't be either, as
> it seems to be running fine. But it's narrowly possible qt-4.6.0 has
> other issues on the BSDs -- it's new enough, not all of them might be
> well known, yet.
>
> And another thing that's different. I could run most apps including kde
> apps, all the ones I tried, certainly, just not plasma-desktop. Thus,
> konsole ran and stayed open just fine. So your problem seems to be
> different enough from mine, it's probably not related at all.
>
> Question: Do you have any other x-terminal type apps installed that
> could be used in place of konsole? What about xorg's own, xterm?
> There's a number of other reasonably light dependency ones as well, rxvt,
> mrxvt, aterm, etc. If you can get one running, and I bet you can with
> little trouble, you can try running konsole and/or plasma-desktop from
> it, and see what happens. Of course, I'm not sure whether the others
> ensure that the correct environment is there to support kde apps, but
> that should be reasonably easy to fix, if necesary.
>
>
Here is the error list from Alt-F2->xterm->plasma-desktop:
plasma-desktop(1229) KLocalePrivate::initEncoding: Cannot resolve system
encoding, defaulting to ISO 8859-1.
QDBusObjectPath: invalid path ""
plasma-desktop(1229)/plasma PlasmaApp::PlasmaApp: Setting the pixmap
cache size to 15599 kilobytes
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasma-desktop path = <unknown> pid = 1229
plasma-desktop(1234) KLocalePrivate::initEncoding: Cannot resolve system
encoding, defaulting to ISO 8859-1.
QDBusObjectPath: invalid path ""
plasma-desktop(1234)/plasma PlasmaApp::PlasmaApp: Setting the pixmap
cache size to 15599 kilobytes
plasma-desktop(1228): Communication problem with "plasma-desktop" , it
probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message
did not receive a reply (timeout by message bus)" "
plasma-desktop(1233): Communication problem with "plasma-desktop" , it
probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message
did not receive a reply (timeout by message bus)" "
Now plasma-desktop gives only those errors. Can't it still be some
configuration error?
How to find from which service the plasma-desktop expect a reply?
Regards
Sagara
___________________________________________________
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
