Re: SIGSEGV when starting kmail

2005-07-12 Thread Thomas Brinker
Hi! Thanks a lot for your help. I just downgraded everything and now (as you can see) it's fine. Regards Thomas BTW: How can I add e correct In-reply-to: manually in kmail? -- Wo kämen wir hin, wenn alle sagten, wo kämen wir hin, und niemand ginge, um einmal zu schauen, wohin man käme, wenn ma

Re: SIGSEGV when starting kmail

2005-07-09 Thread Wolfgang Rohdewald
On Freitag 08 Juli 2005 16:08, Ken Wahl wrote: > For anyone new to debian (like myself) reverting the packages was accomplished > with the following commands: > > cd /var/cache/apt/archives > > dpkg -i --force-downgrade kdelibs_4%3a3.3.2-6.1_all.deb > kdelibs4_4%3a3.3.2-6.1_i386.deb kdelibs-bin_4

Re: SIGSEGV when starting kmail

2005-07-08 Thread Ken Wahl
On Fri, Jul 08, 2005 at 11:22:58AM +0200, Adeodato Simó wrote: > > Just revert kdelibs to 3.3.2-6.1. I'm terribly sorry for having > 3.3.2-7 give so much trouble, but it's probably not worth > investigating since we'll begin with the c++ abi transition soon. > > Please spread the word: do

[Workaround] Re: SIGSEGV when starting kmail

2005-07-08 Thread Tim Ruehsen
If you installed kontact, just start it and klick on the Emails Icon. It will start kmail, even with kdelibs 3.3.2-7. Tim Am Donnerstag, 7. Juli 2005 17:59 schrieb Thomas Brinker: > Hello! > > Today I updated my unstable debian to the least recent packet versions, > as I do every week. Everythi

Re: SIGSEGV when starting kmail

2005-07-08 Thread Walter Hofmann
On Fri, Jul 08, 2005 at 08:37:31AM +0200, Sylvain Joyeux wrote: > Amarok crashes here. I get that as output: > > Object::connect: Cannot connect Engine::Base::statusText( const QString& ) > to (null)::shortMessage( const QString& ) > QObject::connect: Cannot connect Engine::Base::infoMessage( con

Re: SIGSEGV when starting kmail

2005-07-08 Thread Adeodato Simó
* Thomas Brinker [Thu, 07 Jul 2005 17:59:17 +0200]: > Hello! > Today I updated my unstable debian to the least recent packet versions, > as I do every week. Everything looks fine. All KDE Apps in my interest > run except kmail. It right away crashes with a SIGSEGV. As far as I can > see it just l

Re: SIGSEGV when starting kmail

2005-07-07 Thread Sylvain Joyeux
Amarok crashes here. I get that as output: Object::connect: Cannot connect Engine::Base::statusText( const QString& ) to (null)::shortMessage( const QString& ) QObject::connect: Cannot connect Engine::Base::infoMessage( const QString& ) to (null)::longMessage( const QString& ) Does not look ver

Re: SIGSEGV when starting kmail

2005-07-07 Thread Luca Botti
I see the behaviour with amarok - SIGSEGV 11 at startup... Alle Thursday 7 July 2005 19:26, Ken Wahl ha scritto: > On Thu, Jul 07, 2005 at 05:59:17PM +0200, Thomas Brinker wrote: > > Hello! > > > > Today I updated my unstable debian to the least recent packet versions, > > as I do every week. Eve

Re: SIGSEGV when starting kmail

2005-07-07 Thread Ken Wahl
On Thu, Jul 07, 2005 at 05:59:17PM +0200, Thomas Brinker wrote: > Hello! > > Today I updated my unstable debian to the least recent packet versions, > as I do every week. Everything looks fine. All KDE Apps in my interest > run except kmail. It right away crashes with a SIGSEGV. As far as I can >

SIGSEGV when starting kmail

2005-07-07 Thread Thomas Brinker
Hello! Today I updated my unstable debian to the least recent packet versions, as I do every week. Everything looks fine. All KDE Apps in my interest run except kmail. It right away crashes with a SIGSEGV. As far as I can see it just loads the librarys and the crashes, replacing the configs and th