[apport] usplash crashed with SIGILL

Bug #86728 reported by Alex Wauck
2
Affects Status Importance Assigned to Milestone
usplash (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: usplash

usplash crashed during boot. Oddly, the progress bar seemed to fill up most of the way, but the messages that came after the crash indicated that there was still a lot of work to do.

ProblemType: Crash
Date: Thu Feb 15 15:34:23 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: PATH=/bin:/usr/bin:/sbin:/usr/sbin
Signal: 4
SourcePackage: usplash
StacktraceTop:
 ?? () from /lib/libx86.so.1
 ?? () from /lib/libx86.so.1
 ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 16026):
 #0 0xb7d1cf6a in ?? () from /lib/libx86.so.1
 #1 0xb7d1e800 in ?? () from /lib/libx86.so.1
 #2 0x00000000 in ?? ()
Uname: Linux scorpion 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux
UserGroups:

Revision history for this message
Alex Wauck (awauck) wrote :
Revision history for this message
C de-Avillez (hggdh2) wrote :

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 most recent bug report file> -o 86728.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.

Changed in usplash:
assignee: nobody → hggdh2
status: Unconfirmed → Needs Info
Revision history for this message
Alex Wauck (awauck) wrote : Re: [Bug 86728] Re: [apport] usplash crashed with SIGILL

I'm having more problems with usplash (i.e. it doesn't even show up anymore),
and the crash report currently in /var/crash is dated March 1st, while the
bug was reported in February. I think I'll reinstall from Herd 5 (I think
this install originated from Herd 3) and see what happens then. I suspect
something strange happened during upgrades, especially since this doesn't
seem to be a problem for anybody else.

Alex

On Thursday 08 March 2007 12:05:21 pm hggdh wrote:
> 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.ubu
>ntu.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 most recent bug report file> -o
> 86728.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.
>
>
> ** Changed in: usplash (Ubuntu)
> Assignee: (unassigned) => hggdh
> Status: Unconfirmed => Needs Info

Revision history for this message
C de-Avillez (hggdh2) wrote :

Actually, we have some other bugs similar to yours. Also, the current usplash (0.4-43) *did* fix some memory issues that could cause a series of problems, perhaps similar to yours. In fact, the maintainer stated "causing all sorts of unpredictable problems".

So... I think the best option right now is for us to wait a bit on this one, since it may have been fixed by 0.4-43. Better safe than sorry, and all of that.

On not seeing usplash at all: this is a different issue, and I would like you to open a new bug on it. Please specify the usplash version and, if you are running kubuntu, please also specify the version of kubuntu-artwork-usplash (or the corresponding artwork package).

C de-Avillez (hggdh2)
Changed in usplash:
assignee: hggdh2 → nobody
C de-Avillez (hggdh2)
Changed in usplash:
assignee: nobody → hggdh2
C de-Avillez (hggdh2)
Changed in usplash:
assignee: hggdh2 → nobody
importance: Undecided → Medium
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.