2014-08-04 2:46 GMT+04:00 Stefan Wollny <stefan.wol...@web.de>:
> Am 08/03/14 um 20:25 schrieb Vadim Zhukov:
>> 2014-08-03 22:24 GMT+04:00 Stefan Wollny <stefan.wol...@web.de>:
>>> Am 08/03/14 um 19:39 schrieb Vadim Zhukov:
>>>>> Does this help you:
>>>>>> ~ $ kile -v kile:/usr/lib/libstdc++.so.57.0:
>>>>>> /usr/local/lib/libestdc++.so.16.0 : WARNING:
>>>>>> symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch,
>>>>>> relink your program
>>>> This is normal for stuff built with non-base GCC...
>>>>
>>>>>> kile:/usr/local/lib/qt4/libQtScript.so.2.0:
>>>>>> /usr/local/lib/kde4/libs/libkhtml.so.50.2 : WARNING:
>>>>>> symbol(_ZTIN14WTFNoncopyable11NoncopyableE) size mismatch,
>>>>>> relink your program
>>>> ... and this one is not. It looks like you have different binaries
>>>> (libraries or kile executable itself) linked with different
>>>> libraries. Check for (normally hidden) .libs-* packages, e.g., "ls
>>>> -d /var/db/pkg/.libs*".
>>>
>>> ~ $ sudo ld -d /var/db/pkg/.libs*
>>> /var/db/pkg/.libs-firefox-30.0p0: file not recognized: File truncated
>>
>> Wut? Please look at the command line above AGAIN.
>>
>>>>>> Qt: 4.8.6 KDE Development Platform: 4.13.3 Kile: 2.1.3
>>>>>>
>>>>>>
>>>>>>
>>>>>> Would it be helpful if I delete kile-kde4 and kde4-libs and
>>>>>> give it a new try from ports?
>>>> Why don't you use official packages?
>>>
>>> Because with kde4 kde3-based kile from packages gave me the same
>>> behaviour...
>>
>> Wut? There are kile packages both for KDE3 and KDE4.
>>
>>> I will de-install kile and the package in /usr/ports and give the
>>> official package a second try.
>>
>> Please do.
>>
>> --
>>   WBR,
>>   Vadim Zhukov
>>
> Hi Vadim,
>
> sorry that it took so long for the next tests: I did an upgrade to
> amd64-current #316 and fsck'd the partitions while being there.
>
> OK - one more info that doesn't make a difference in reality: I had
> 'only' installed kde4-minimal so far prior to installing kile. Now for
> the sake of testing I accepted the pollution in particular of kde4-games
> just to be shure we do not miss a piece and installed kde4 from
> packages. So far I started X with fluxbox and now did an additional test
> with ../startkde4: Same result - kile becomes irresponsible after startup.
>
> I did thé last tests with all references under ~/.kde4/ to kile where
> deleted. Mmmh  - I will redo the test after having moved ~/.kde4 to
> ~/_kde4 - let's see if kile recreates this folder...
>
> Well - yes, it does. But just before as this is the second startup of
> kile it stops right here:
>
> ~ $ kile
> kile:/usr/lib/libstdc++.so.57.0: /usr/local/lib/libestdc++.so.16.0 :
> WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch,
> relink your program
> kile:/usr/local/lib/qt4/libQtScript.so.2.0:
> /usr/local/lib/kde4/libs/libkhtml.so.50.2 : WARNING:
> symbol(_ZTIN14WTFNoncopyable11NoncopyableE) size mismatch, relink your
> program
> Object::connect: No such signal
> org::freedesktop::UPower::DeviceAdded(QString)
> Object::connect: No such signal
> org::freedesktop::UPower::DeviceRemoved(QString)
>
>
>
> Still I am requested to 'relink' the program ...
>
> It will be annoying - but unless you come up with a better suggestion I
> will reinstall the entire system from scratch to the bare minimum to be
> assured that I did not make an error with the present installation. But
> not before monday night.
>
> BTW: Any other tests related to kde4 you'd like me to do? (Just drop me
> a note privately to not pollute misc@)
>
> Have a nice week!

I reproduced your problem here. It looks like the root of problem is
in libinotify, which doesn't handle named pipes well. The Kile creates
two named pipes to talk with LyX server (see
http://wiki.lyx.org/LyX/LyXServer). And then at some point libinotify
tries to open those files...

You can try to run the two following commands:

$ kwriteconfig4  --file ~/.kde/share/config/kilerc --group DirWatch
--key PreferredMethod Fam
$ rm ~/{.lyx/,}.lyxpipe*

(if your KDEHOME isn't in the ~/.kde, tweak the first command accordingly)
And then start Kile again. See if it helps.

--
  WBR,
  Vadim Zhukov

Reply via email to