Hi I have 2 questions related to this bug: John, how did you exactly reproduced the problem ? [what arguments ?] Did you run usplash from the console directly ? In my case this does not make it crash. Do you manually issue usplash_write commands ? Which ones ?
All, why would the usplash package need to be "unstripped" ? What is the benefit now to strip it in the first place ? Is this common to a lot of ubuntu packages ? How fat does it grow when unstripped ? Anyone here can approciate the time saved when the package ships unstripped. Stripped binaries are required when disk space is an issue AND binaries are fully stable, I don't want to start a debate, just want to know what's the "ubuntu" option on this. -- [edgy] usplash segfaults https://launchpad.net/bugs/56587 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
