From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: splashutils users: how often does fbsplashd crash for you?
Date: Mon, 01 Jun 2015 10:31:07 +0300 [thread overview]
Message-ID: <mkh1nq$9de$1@ger.gmane.org> (raw)
In-Reply-To: <556AE396.3010308@baums-on-web.de>
On 31/05/15 13:33, Heiko Baums wrote:
> Am 31.05.2015 um 12:01 schrieb Nikos Chantziaras:
>> how often does fbsplashd crash for you?
>
> For me not once since it exists.
>
>> fbsplashd.stati[599]: segfault at 7f24ceb9b000 ip 000000000050a6f0 sp
>> 00007f24ce35fd08 error 6 in fbsplashctl
>
> Are you sure that there's no other problem with your system?
There doesn't seem to be anything wrong with it.
> fbsplashd.stati is actually fbsplashd.static. But I don't know if your
> system logger just cuts the file name.
>
> I would first try to reinstall media-gfx/splashutils.
Already did that. Funny thing is: the bootsplash works fine. There's
nothing wrong it, other than the segfault messages in dmesg.
prev parent reply other threads:[~2015-06-01 7:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-31 10:01 [gentoo-user] splashutils users: how often does fbsplashd crash for you? Nikos Chantziaras
2015-05-31 10:33 ` Heiko Baums
2015-06-01 7:31 ` Nikos Chantziaras [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='mkh1nq$9de$1@ger.gmane.org' \
--to=realnc@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox