David Rosenstrauch wrote:

David C. Rankin wrote:

...

Listmates,

Success, first email from the new arch box on kde3 with opera! The issue I have is that every time kde starts, ksplash crashes with a SIGSEGV (11) message. Is this an easy fix? Thanks!

Dunno. Doesn't happen to me. Try searching arch forums, kdemod forums, or google for some combination of the keywords: ksplash, kdemod, sigsegv, segfault, etc.

Is there any stack trace, btw, or anything getting written to any of the logs?

DR

You might also be able to get some more info by doing "strace ksplash" from the command line. DR

On Thu, 23 Apr 2009 10:47:08 -0500, Bram Schoenmakers <lists@bramschoenmakers.nl> wrote:

On Thursday 23 April 2009 17:37:19 David C. Rankin wrote:

Hello David,

...

Listmates,

Success, first email from the new arch box on kde3 with opera! The issue I have is that every time kde starts, ksplash crashes with a SIGSEGV (11) message. Is this an easy fix? Thanks!

I think the backtrace of that crash ends in a library provided by the libxi package. And these crashes started since I upgraded libxi from 1.1.4 to 1.2.1. Only yesterday I downgraded the package to the previous version and I have yet to hear if that solved the problem.

See this article [1] for more info on downgrading packages.

[1] http://wiki.archlinux.org/index.php/Downgrade_packages

Kind regards,

Thanks Bram, DR, I've attached the backtrace from the kplash crash: ksplash.kcrash (3.4k) -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

On Thursday 23 April 2009 18:35:04 David C. Rankin wrote: Hello David,

Thanks Bram, DR,

I've attached the backtrace from the kplash crash:

ksplash.kcrash (3.4k)

Thank you. It seems this is a different problem than I encountered the other day. This looks like a splash specific problem (Flexible Plugin for KSplash [1]), and it should be reported to the author(s) of that splash screen. If you do so, I'd suggest to install kdemod3-kdelibs-debug and create a new backtrace, before you submit it. As a sidenote, the problem could be triggered by a packaging problem, for instance that the translations are not properly included. Just a shot in the dark. To work around this problem right now, I'd suggest to change the splash screen in the KDE Control Centre. [1] http://kde-look.org/content/show.php?content=20623 Kind regards, -- Bram Schoenmakers What is mind? No matter. What is matter? Never mind. (Punch, 1855)

On Friday 24 April 2009 00:14:15 David C. Rankin wrote: Hello David,

Not having filed with http://bugs.archlinux.org/ before, is there anything special I need to do to make sure it is "reported to the author(s) of that splash screen"? I presume it works like any other bugzilla, but is there something beyond that I should know to make sure it gets to the right place?

I've installed kdemod3-kdelibs-debug and I will gather a new backtrace to submit. Thank you for your help!

First of all, http://bugs.archlinux.org is not the right place for this crash. It's written and packaged outside the official Arch Linux project. The splash screen does not seem to have a dedicated website or bug tracker, so I'd suggest to mail the author directly, and attach the backtrace with more details (so kdemod3-kdelibs-debug provides that). If it turns out to be a packaging problem, you should contact the kdemod guys. http://kdemod.ath.cx/bugs/index.php Kind regards, -- Bram Schoenmakers What is mind? No matter. What is matter? Never mind. (Punch, 1855)