| 2007-03-06 17:02:56 |
Holger Peifer |
bug |
|
|
added bug |
| 2007-03-06 17:02:56 |
Holger Peifer |
bug |
|
|
added attachment 'CoreDump.gz' (CoreDump.gz) |
| 2007-03-06 17:02:56 |
Holger Peifer |
bug |
|
|
added attachment 'Dependencies.txt' (Dependencies.txt) |
| 2007-03-06 17:02:56 |
Holger Peifer |
bug |
|
|
added attachment 'Disassembly.txt' (Disassembly.txt) |
| 2007-03-06 17:02:56 |
Holger Peifer |
bug |
|
|
added attachment 'ProcMaps.txt' (ProcMaps.txt) |
| 2007-03-06 17:02:56 |
Holger Peifer |
bug |
|
|
added attachment 'ProcStatus.txt' (ProcStatus.txt) |
| 2007-03-06 17:02:56 |
Holger Peifer |
bug |
|
|
added attachment 'Registers.txt' (Registers.txt) |
| 2007-03-08 14:45:36 |
C de-Avillez |
usplash: status |
Unconfirmed |
Needs Info |
|
| 2007-03-08 14:45:36 |
C de-Avillez |
usplash: assignee |
|
hggdh2 |
|
| 2007-03-08 14:45:36 |
C de-Avillez |
usplash: statusexplanation |
|
Hello Holger,
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 90157.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-09 15:37:04 |
C de-Avillez |
usplash: assignee |
hggdh2 |
|
|
| 2007-03-09 15:37:04 |
C de-Avillez |
usplash: statusexplanation |
Hello Holger,
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 90157.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-09 15:42:56 |
C de-Avillez |
usplash: assignee |
|
hggdh2 |
|
| 2007-03-09 17:41:55 |
C de-Avillez |
usplash: status |
Needs Info |
Rejected |
|
| 2007-03-09 17:41:55 |
C de-Avillez |
usplash: assignee |
hggdh2 |
|
|
| 2007-03-09 17:42:05 |
C de-Avillez |
marked as duplicate |
|
88915 |
|
