[apport] usplash crashed with SIGSEGV

Bug #83785 reported by miked
4
Affects Status Importance Assigned to Milestone
usplash (Ubuntu)
Invalid
High
Unassigned

Bug Description

Binary package hint: usplash

Fresh install 5th time. Ubuntu 7.04 Feisty Fawn Herd3 i386.iso
Installed 102 of 103 updates available gnome-app-install 0.3.11 to 0.3.17(180kb) was held back for some reason. I have restarted my computer since the updates (I will try to log out and back in) because sometimes the computer doesn't recover. The default install Screen Resolution 1280x1024@75Hz gives me vertical lines about an inch apart. I switched to 1024x768@85Hz which works good until I log out or off. After I do, the screen comes up black with the mouse pointer as the moving ubuntu circle pointer. It's nice to see the auto-filing, auto-naming, and auto reporting working right today. I know this probably posted in the wrong place so feel free to move it. I need to restart the computer, so if if it works I will try to put the report in the right place. If it doesn't it may be awhile but for I post again. I thought I should post this time, because it's still happening, like the CLVM Cluster Management problem/bug in Herd2 I never posted because I thought it was some I did wrong. I also have an update-app-install crash. When my computer start up the normal verbose posts instead appear as 5 vertical rows of white on black blocks with visible screen refresh problems.

ProblemType: Crash
Date: Wed Feb 7 07:01:53 2007
Disassembly: 0xb7fbbefa:
DistroRelease: Ubuntu 7.04
ExecutablePath: /sbin/usplash
Package: usplash 0.4-36
ProcCmdline: /sbin/usplash -c -x 1280 -y 1024
ProcCwd: /dev/.initramfs
ProcEnviron:
 LANGUAGE=
 PATH=/sbin:/bin:/usr/sbin:/usr/bin
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: usplash
Stacktrace:
 Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
 #0 0xb7fbbefa in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Uname: Linux ubuntu704ah3 2.6.20-6-generic #2 SMP Wed Jan 31 20:53:39 UTC 2007 i686 GNU/Linux
UserGroups:

Revision history for this message
miked (miked11) wrote :
Revision history for this message
miked (miked11) wrote :

Can't upload usplash crash file it says it's empty.

Revision history for this message
miked (miked11) wrote :

No longer getting this crash/error with fresh install #6 and the 160 dist-upgrades.

Revision history for this message
miked (miked11) wrote :

This bug came back after multiple updates, and upgrades.

Revision history for this message
miked (miked11) wrote :

still crashing after multiple updates

Revision history for this message
miked (miked11) wrote :

computer login in unreadable multi-colored vertical lines.
login in by memory
with user name then password

Revision history for this message
miked (miked11) wrote :

Fresh install Ubuntu 7.04 The Feisty Fawn Alpha Herd4 i386/i686.iso
without updates.
will update next.

Revision history for this message
miked (miked11) wrote :

Added updates and upgrades
still getting crash balloon.
had to lower screen resolution from 1152x864@85Hz to 1024x768@85Hz because I started getting vertical lines on the screen when I moved the mouse.

Revision history for this message
miked (miked11) wrote :

{!} on start-up

Revision history for this message
miked (miked11) wrote :

How do you attach the bug report being send to developers, that looks more helpful and extensive ?

I have been sending those reports, but I don't really know where they are going to developers somewhere I guess.

Revision history for this message
miked (miked11) wrote :

Herd4

Revision history for this message
miked (miked11) wrote :

Herd5, Crash {!} not after install, but after updating.
I don't know anything about what this means, but the last line of the report to be sent to developers says:
"ProcCmdline
/sbin/usplash -c -x 1280 -y 1024"
that resolution 1280x1024@75Hz? does not work right on this monitor (Sony Trinitron MultiScan E200)
I just got another crash by clicking on screen resolution while looking up the resolution.
Screen Resolution does not open after trying to start.
There is more updates now, so we'll see what happens.

Revision history for this message
miked (miked11) wrote :

added updates, still crashing

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

miked -- thank you for your tenacity, and I am sorry we took us that long to get back to you.

Could you please edit /etc/usplash.conf and change the resolution to one that works on your monitor, and then try again?

The configuration file is quite simple: just two lines; right now, per your reports, it is probably like:

yres=1280
xres=1024

and this is not good for your monitor...

Changed in usplash:
assignee: nobody → hggdh2
status: Unconfirmed → Needs Info
C de-Avillez (hggdh2)
Changed in usplash:
assignee: hggdh2 → nobody
C de-Avillez (hggdh2)
Changed in usplash:
assignee: nobody → hggdh2
Revision history for this message
miked (miked11) wrote :

you bet, I will try that later, gotta run.

Revision history for this message
miked (miked11) wrote :

I tried changing the /etc/usplash.conf file to
yres=1152
xres=864
which is a resolution that works o.k. on my monitor,
but I still get the lines and jumbleg groupings before I login into the gnome desktop, and the crash after I log in.
I will try a lower resolution to see if that fixes it.
yres=1024
xres=768

Revision history for this message
miked (miked11) wrote :

crash is back, can't upload usplash crash file because, when I updated the kernel to 2.6.20.10 it changed my gdm settings and dis-abled root login, so I had to log in with a admin user account and that does not seem to have permission to attach this type of file.

Revision history for this message
C de-Avillez (hggdh2) wrote : Re: [Bug 83785] Re: [apport] usplash crashed with SIGSEGV

On Tue, 2007-03-13 at 21:45 +0000, miked wrote:
> crash is back, can't upload usplash crash file because, when I updated
> the kernel to 2.6.20.10 it changed my gdm settings and dis-abled root
> login, so I had to log in with a admin user account and that does not
> seem to have permission to attach this type of file.
>

No problem. Let's say the crash file is called _CRASH_, and it is
under /var/crash; finally let's assume your login id is miked.

So you:

cd /var/crash
sudo chown miked _CRASH_

and then you upload it at will.

Revision history for this message
miked (miked11) wrote :
Revision history for this message
miked (miked11) wrote :

Fresh install Ubuntu 7.04 Beta Alternative Install i386/i686.iso
This crash showed up right after first apt-get update, and apt-get dist-upgrade and restart.

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

duplicate of bug # 88915

Changed in usplash:
assignee: hggdh2 → nobody
importance: Undecided → High
status: Needs Info → Rejected
Revision history for this message
miked (miked11) wrote :
Revision history for this message
miked (miked11) wrote :
Revision history for this message
miked (miked11) wrote :
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.