| 2007-03-01 11:39:32 |
Mark Gumprecht |
bug |
|
|
added bug |
| 2007-03-01 11:39:32 |
Mark Gumprecht |
bug |
|
|
added attachment 'CoreDump.gz' (CoreDump.gz) |
| 2007-03-01 11:39:32 |
Mark Gumprecht |
bug |
|
|
added attachment 'Dependencies.txt' (Dependencies.txt) |
| 2007-03-01 11:39:32 |
Mark Gumprecht |
bug |
|
|
added attachment 'Disassembly.txt' (Disassembly.txt) |
| 2007-03-01 11:39:32 |
Mark Gumprecht |
bug |
|
|
added attachment 'ProcMaps.txt' (ProcMaps.txt) |
| 2007-03-01 11:39:32 |
Mark Gumprecht |
bug |
|
|
added attachment 'ProcStatus.txt' (ProcStatus.txt) |
| 2007-03-01 11:39:32 |
Mark Gumprecht |
bug |
|
|
added attachment 'Registers.txt' (Registers.txt) |
| 2007-03-08 14:53:58 |
C de-Avillez |
usplash: status |
Unconfirmed |
Needs Info |
|
| 2007-03-08 14:53:58 |
C de-Avillez |
usplash: assignee |
|
hggdh2 |
|
| 2007-03-08 14:53:58 |
C de-Avillez |
usplash: statusexplanation |
|
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/DebuggingProgramCrash?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 88915.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. |
|
| 2007-03-08 16:33:28 |
C de-Avillez |
title |
reboot after feisti 7.04 update |
usplash crashed with signal 5 on reboot after feisti 7.04 update |
|
| 2007-03-09 17:39:39 |
C de-Avillez |
usplash: status |
Needs Info |
Confirmed |
|
| 2007-03-09 17:39:39 |
C de-Avillez |
usplash: importance |
Undecided |
Medium |
|
| 2007-03-09 17:39:39 |
C de-Avillez |
usplash: statusexplanation |
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/DebuggingProgramCrash?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 88915.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. |
I am confirming this bug. We have some other bugs that are matching in the backtrace, and some others that are a probable match. I am duplicating them all against this bug.
Please undup any you think are not the same issue. |
|
| 2007-03-09 17:39:39 |
C de-Avillez |
usplash: assignee |
hggdh2 |
|
|
| 2007-03-09 17:40:37 |
C de-Avillez |
usplash: status |
Confirmed |
Rejected |
|
| 2007-03-09 17:40:37 |
C de-Avillez |
usplash: importance |
Medium |
Undecided |
|
| 2007-03-09 17:40:37 |
C de-Avillez |
usplash: statusexplanation |
I am confirming this bug. We have some other bugs that are matching in the backtrace, and some others that are a probable match. I am duplicating them all against this bug.
Please undup any you think are not the same issue. |
|
|
| 2007-03-09 17:40:48 |
C de-Avillez |
usplash: status |
Rejected |
Confirmed |
|
| 2007-03-09 17:40:48 |
C de-Avillez |
usplash: importance |
Undecided |
Medium |
|
| 2007-03-13 15:52:32 |
C de-Avillez |
usplash: importance |
Medium |
High |
|
| 2007-03-27 16:01:56 |
miked |
bug |
|
|
added attachment '_sbin_usplash.0.crash' (Crash file Usplash) |
| 2007-03-27 16:05:17 |
miked |
bug |
|
|
added attachment 'gdb-usplash.txt' (gdb-usplash file) |
| 2007-03-27 16:12:55 |
miked |
bug |
|
|
added attachment '_sbin_usplash.0.crash' (Crash file Usplash) |
| 2007-03-27 22:02:00 |
miked |
bug |
|
|
added attachment 'valgrind-logs-usplash.tar.gz' (valgring-logs-usplash) |
| 2007-03-28 00:20:45 |
miked |
bug |
|
|
added attachment 'strace-usplash.log.tar.gz' (strace-usplash.log file) |
| 2007-03-28 09:11:15 |
miked |
bug |
|
|
added attachment '88915.retrace' (88915.retrace file) |
| 2007-03-30 10:47:26 |
miked |
bug |
|
|
added attachment '_sbin_usplash.0.crash' (Crash file Usplash) |
| 2007-03-31 13:40:19 |
miked |
bug |
|
|
added attachment '_sbin_usplash.0.crash' (Crash file Usplash) |
| 2007-04-02 15:03:21 |
miked |
bug |
|
|
added attachment '_sbin_usplash.0.crash' (Crash file Usplash) |
| 2008-02-06 15:01:40 |
Martin Pitt |
usplash: status |
Confirmed |
Fix Released |
|
