[apport] usplash crashed with SIGSEGV on start up
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
usplash (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: usplash
Automatic report generated on booting Feisty Herd 4 as a virtual machine (on OS X Parallels).
Different circumstances to bug 83785, despite similar names.
ProblemType: Crash
Date: Sat Feb 17 00:25:22 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /sbin/usplash
Package: usplash 0.4-41
ProcCmdline: /sbin/usplash -c -x 1024 -y 768
ProcCwd: /dev/.initramfs
ProcEnviron:
LANGUAGE=
PATH=/
LANG=en_GB.UTF-8
Signal: 11
SourcePackage: usplash
Stacktrace:
Using host libthread_db library "/lib/tls/
Core was generated by `/sbin/usplash -c -x 1024 -y 768'.
Program terminated with signal 11, Segmentation fault.
#0 0xb7d30f5a in ?? () from /lib/libx86.so.1
#0 0xb7d30f5a in ?? () from /lib/libx86.so.1
StacktraceTop: ?? () from /lib/libx86.so.1
ThreadStacktrace:
.
Thread 1 (process 10831):
#0 0xb7d30f5a in ?? () from /lib/libx86.so.1
Uname: Linux feisty 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux
UserGroups:
Changed in usplash: | |
assignee: | hggdh2 → nobody |
Changed in usplash: | |
assignee: | nobody → hggdh2 |
Changed in usplash: | |
assignee: | hggdh2 → nobody |
status: | Needs Info → Rejected |
Thank you for your bug report.
Unfortunately the stack trace / backtrace is not detailed enough to help. If this bug is reproducible at will, could you please:
1. add to your /etc/apt/ sources. list the debug symbols repository? You can edit it directly with the editor of your preference (as root), and add at the bottom the following line:
deb http:// people. ubuntu. com/~pitti/ ddebs feisty main universe
You can also use Synaptic (under Gnome, go to System/ Administration/ Synaptic Package Manager and then, on Synaptic, select Settings/ Repositories, and add the entry under the "Third Party" tab.
Please read on https:/ /wiki.ubuntu. com/DebuggingPr ogramCrash? highlight= %28%2F% 2Fpeople. ubuntu. com%2F% 7Epitti% 2Fddebs% 29 for details.
2. update the repositories, but do not install any upgraded package.
3. Now we have two options: we can just retrace the report you have, or we can try to reproduce it. I think, right now, retracing is simpler.
Your issue report should be at /var/crash. Open a terminal session, and then:
cd /var/crash
Find the name of the bug report, and issue
apport-retrace <name of the bug report file> -o 85742.retrace
this command will take a bit to complete, and during its execution it will download any necessary debug packages.
After the completion of the retrace, please upload the newly-created report here.
Thank you.