Usplash was not working on my laptop (dell latitude c640, ATI Mobility 7500)
but I
had not got any segmentation faults.
The problem was that the /etc/usplash.conf was misconfigured for some
unknown reason. Instead of 1024x768 it got entries for 1280x1024. After
correcting this entry and
This seems to be working correctly after running apt-update on installed
Edgy RC. I don't have to remove splash and the system boots from GRUB
to kdm login in 39 seconds.
On Edgy Beta the screen was garbled if I ran usplash.
System: AMD64/Nvidia 410 chipset
--
[edgy] usplash segfaults
I still get corruption on my VTs and something new is happening. If I
switch to a VT and switch back to X all I see is a blank screen and my
mouse, which moves... I'm not sure if this is a usplash issue.
I have an X800
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
On Tue, Oct 17, 2006 at 10:29:50PM -, Jeff Hanson wrote:
I'm still getting a corrupt/garbled screen while the system boots up. I
can almost make out a progress bar but it is very garbled and shows up
on my screen in three different places.
Let me know what information I can provide to
Fantastic I now have a boot splash screen however when shutting down the
system hard crashes this is the problem I had in Dapper that is still
specific to the card driver I believe.
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing list
* Jeff Hanson
| I'm still getting a corrupt/garbled screen while the system boots up. I
| can almost make out a progress bar but it is very garbled and shows up
| on my screen in three different places.
This should be fixed with the new artwork. The problem was our old
artwork didn't ship a
I'm still getting a corrupt/garbled screen while the system boots up. I
can almost make out a progress bar but it is very garbled and shows up
on my screen in three different places.
Let me know what information I can provide to help, I'm not new to Linux
by any means but I am new to reporting
I still have the same problem here !
Amd64 edgy with nvidia geforcge 6600gt
i get :
$ dmesg | grep usplash
[ 25.985482] usplash[870]: segfault at ffab rip 2b2943ce18a2
rsp 7fff66f058d0 error 4
Would be nice to have usplash for the release !
Anyway keep up the good work
Actually, it's because usplash is spinning and using 100% CPU... it's really
apparent that even things like disk access is sluggish during boot (disk not
grinding nearly as fast).
I agree with everyone suggesting a fallback that I'd rather NOT see a
usplash than end up with a slow-as-molasses
Fixed by switching to bogl on amd64; usplash 0.4-32 is uploaded and
waiting for review and approval.
** Changed in: usplash (Ubuntu)
Assignee: (unassigned) = Tollef Fog Heen
Status: Confirmed = Fix Released
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
A graceful fallback would be appreciated, even if it is to not activate
the 'splash' option at install on this platform.
Booting with 'splash' takes 5 minutes here, when I remove 'splash' it
takes 56 seconds. I suspect that the usplash client functions have some
sort of a timeout which causes
Matthew, is there any hope of getting this fixed in the next few days?
If not, can we fallback to vga on the affected platforms?
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
On Notebook, fresh Edgy Beta1 install, no bootsplash. I have an ATI Mobility
7500.
After some seconds, the X Login magically appears :D
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Still with usplash 0.4-30 run with sudo usplash on amd64 with geforce 6800gt.
[ 519.223299] usplash[7803]: segfault at ff80 rip 2ae0ca9908e2
rsp 7fffe0255690 error 4
but it does automatically switch to console 1 and display the blinking cursor,
when I switched back to X it
Hi I have 2 questions related to this bug:
John, how did you exactly reproduced the problem ? [what arguments ?] Did you
run usplash from the console directly ? In my case this does not make it crash.
Do you manually issue usplash_write commands ? Which ones ?
All, why would the usplash
On 9/29/06, François Isabelle [EMAIL PROTECTED] wrote:
Hi I have 2 questions related to this bug:
John, how did you exactly reproduced the problem ? [what arguments ?] Did
you run usplash from the console directly ? In my case this does not make it
crash. Do you manually issue usplash_write
I got impatient and built bzr revision 90, but it still doesn't work. I
can't get a GDB backtrace though. Mabye I am being impatient or just
doing something wrong?
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Confirmed, bzr rev 90 still segfaults on amd64/nvidia. I've attached an
apport crash report on it, after unstripping the package. That should be
quite a deal of debugging fun :)
** Attachment added: apport crash report
http://librarian.launchpad.net/4540718/_sbin_usplash.0.crash
** Changed
x86emu makes me cry. Ok, looking into this.
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
A workaround for this has been committed to bzr, and will be released
after beta.
** Changed in: usplash (Ubuntu)
Status: Confirmed = Fix Committed
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: usplash (Ubuntu)
Target: ubuntu-6.10-beta = ubuntu-6.10
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Targetting for beta (and removing corresponding target from a duplicate)
** Changed in: usplash (Ubuntu)
Target: None = ubuntu-6.10-beta
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I've got similar issue as bug #61711 however dunno it's related or not:
I can't find any sign for segfault ... The problem also cause very slow
booting for me
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Attaching a backtrace with the debugging information from:
deb http://people.ubuntu.com/~pitti/ddebs edgy main universe
installed, I hope this is useful. I am running today's edgy, with the processor
being an
'AMD Turion(tm) 64 Mobile Technology ML-37' (from /proc/cpuinfo)
and an ati mobility
** Bug 61663 has been marked a duplicate of this bug
** Bug 60135 has been marked a duplicate of this bug
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Marking as critical. A significant number of users run the hardware
(amd64 + nvidia) to have this problem, and many users won't know what to
do - how to get to a working desktop.
** Changed in: usplash (Ubuntu)
Importance: Untriaged = Critical
--
[edgy] usplash segfaults
...however, the bug doesn't prevent them from getting a working desktop,
it just looks confusing.
** Changed in: usplash (Ubuntu)
Importance: Critical = Medium
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I still have no splash screen even when running from Live cd using the
nv35 driver or the nvidia driver. this is as of 16/08/06. This is on
an amd 64 bit edgy and the live cd is knot3 amd 64bit
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing list
I confirm the segmentation fault on AMD64 dual core with Nvidia 7600 GS.
Video card :
01:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce 7600 GS]
(rev a1)
Usplash version : 0.4-24
dmesg output :
[ 24.217928] usplash[886]: segfault at ffab rip 2ad46cd61622
rsp
Sorry, I'll attach it this time. It seems if you forget the attachment
Description, it asks you for it, but it also clears the file box.
** Attachment added: valgrind log
http://librarian.launchpad.net/4168085/valgrind.log.9210.gz
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
I ran usplash 0.4-18 through valgrind, I had to do it as root, but it
didn't seem to crash. Here is my log anyway.
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Bug 59234 has been marked a duplicate of this bug
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Although the resulting binary still segfaults on my machine, here a fix
for the FTBFS that works for me.
** Attachment added: Trivial fix for the FTBFS
http://librarian.launchpad.net/4159748/build.patch
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing
It appears that the package now FTBFS. From the buildlog
(http://librarian.launchpad.net/4135904/buildlog_ubuntu-edgy-
amd64.usplash_0.4-16_FAILEDTOBUILD.txt.gz)
/usr/bin/ld: svgalib/staticlib/libvgagl.a(grlib.o): relocation R_X86_64_32
against `currentcontext' can not be used when making a
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks! This patch worked for me, but I had to fix it to use relative
paths. I attached my corrected version.
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
@Michael Bienia:
Where exactly do I have to put this -fPIC?
Thanks.
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I've attached a diff with the changes I made to compile the package.
I'm not sure if these are the correct places to add -fPIC but it worked for me.
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
usplash 0.4-15 works for me on my amd64 box but I had to compile my own
package as the official build for amd64 failed due to some missing
-fPIC.
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I can confirm this too, using usplash 0.4-12 on AMD64, with a nvidia
card. The drivers are the nv ones. My GDB output it slightly
different:
(gdb) run
Starting program: /sbin/usplash
(no debugging symbols found)
Program received signal SIGSEGV, Segmentation fault.
0x00402ec6 in ?? ()
The relevant output from lspci for my graphics card is:
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R350 [Radeon
9800 Pro]
01:00.1 Display controller: ATI Technologies Inc Radeon R350 [Radeon 9800 Pro]
(Secondary)
--
[edgy] usplash segfaults
https://launchpad.net/bugs/56587
41 matches
Mail list logo
