Bug#240329: fails to launch
DEGAND Nicolas writes:
> Le dimanche 4 Avril 2004 20:16, vous avez écrit :
>> DEGAND Nicolas writes:
>> >> >> >> > if I launch knode, it uses the hard drive extensively
>> >> >> >> > then fails with the following message :
>> >> >> >>
>> >> >> >> Can you follow the instructions here, by installing the
>> >> >> >> debug packages and getting a crash backtrace or a valgrind
>> >> >> >> output?
>> >
>> > 1° Knode works flawlessly with the debug packages... Why, oh
>> > why...
>>
>> That's very strange.
> Do not know. Maybe something changed in my config since last week.
Possibly, yes.
>> > 2° Now I have ugly grey bars between my icons on the
>> > taskbar. They are not even perfectly aligned with the icons. And
>> > how can I downgrade kdelibs without risking destroying my whole
>> > KDE install.
>>
>> Oh, were you still using KDE 3.1 ? Anyway, I had this problem as
>> well. It went away when I resized the panel.
> No. KDE 3.2.1 was installed from scratch on this computer. Just
> imported some KDE 3.1 config files from another computer for a few
> applications (Kmail, Knode, Kopete... but not the desktop
> setup). But in any case this worked flawlessly with my previous KDE
> 3.2.1 packages.
> It indeed go away when I resize the panel to a size higher than
> "small". But I did not have this problem with the previous packages.
Strange strange strange.
>> > 3° Ksnapshot is now broken (it reports "bus error") so I cannot
>> > attach a screenshot about the problem 2°.
>>
>> That's also very strange, I cannot reproduce that at all. There
>> seem to be stange things going on there :) Do you perhaps have any
>> extra useful information about your setup that may be useful in
>> debugging this problem ?
> Do not know. here is the list of KDE-related installed packages :
Just two remarks:
1 In the list below, there are no debug packages listed. Have you
uninstalled them again ?
2 The strange thing about all the previous things that went wrong, is
that my debug packages are completely identical to the normal
packages, except for the debugging symbols. If there is a problem
in them, then it must either be a very strange compiler bug, or
a problem in some debug code. Both of these are pretty unlikely.
cheers
domi
Reply to: