[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mesa (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079011
Tit
John Harrington, thank you for reporting this and helping make Ubuntu
better.
As per https://wiki.ubuntu.com/Releases, Ubuntu 12.10 reached EOL on May
16, 2014.
Is this reproducible with a supported release?
** Changed in: mesa (Ubuntu)
Importance: Undecided => Low
** Changed in: mesa (Ubunt
As nobody has been able to test this in flightgear, assuming it's the
same really-in-mesa problem. (It's also likely that this hardware
wouldn't run flightgear at a usable speed anyway.)
** Changed in: flightgear (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notificatio
Assigning a bug to yourself means intending to fix it, which given that
you "can;t do anything" was probably not what you meant.
If your system does not work, please file a new bug stating exactly what
is wrong: https://help.ubuntu.com/community/ReportingBugs
If you are looking for general help w
i can;t do anything with this os!
** Changed in: flightgear (Ubuntu)
Assignee: (unassigned) => sidlwebb (sidlwebb)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079011
Title:
stellarium asser
Thanks for looking into this for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079011
Title:
stellarium assert failure: nv10_state_fb.c:50: get_rt_format:
Assertion `0' failed.
To manage no
Sorry, upstream explicitly don't want bug reports for cards older than
nv30 (yours is nv18, current is ~nv120):
http://nouveau.freedesktop.org/wiki/MesaDrivers/
Changing the error message (at
http://sources.debian.net/src/mesa/10.3.2-1/src/mesa/drivers/dri/nouveau/nv10_render.c/#L104
) to somethin
The error occurs because nv10 (the driver used for this card) declares
VBO support (extension GL_ARB_vertex_buffer_object) but only supports
VBOs of int8, int16 and float (not double) types, and the application is
trying to draw data of type double. Given that the double type is part
of the OpenGL
See attached file for (gdb) frame 10, print *vbo, and print *exec output
** Attachment added: "frame10&vbo&exec.txt"
https://bugs.launchpad.net/ubuntu/+source/stellarium/+bug/1079011/+attachment/4267266/+files/frame10%26vbo%26exec.txt
--
You received this bug notification because you are a m
See attached file for (gdb) run and thread apply all bt full output
** Attachment added: "run&thread.txt"
https://bugs.launchpad.net/ubuntu/+source/stellarium/+bug/1079011/+attachment/4267263/+files/run%26thread.txt
--
You received this bug notification because you are a member of Ubuntu
Bug
See attached file for (gdb) frame 9, print *ctx, and print *nctx output
** Attachment added: "frame9&ctx&nctx.txt"
https://bugs.launchpad.net/ubuntu/+source/stellarium/+bug/1079011/+attachment/4267265/+files/frame9%26ctx%26nctx.txt
--
You received this bug notification because you are a memb
See attached file for glxinfo output
** Attachment added: "glxinfo.txt"
https://bugs.launchpad.net/ubuntu/+source/stellarium/+bug/1079011/+attachment/4267262/+files/glxinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
(Sorry about the repeated questions: that's the nature of debugging a
problem that only happens on hardware I don't have.)
That looks like either a bad GLcontext (at the error location it is only
looking at this internal structure, not the objects to be drawn), or an
attempt to use VBO (an OpenGL
Thanks for helping me with this. Here's the output:
stellarium:
../../../../../../../src/mesa/drivers/dri/nouveau/nv10_render.c:104:
get_hw_format: Assertion `0' failed.
Program received signal SIGABRT, Aborted.
0xb7fdcd30 in __kernel_vsyscall ()
(gdb) thread apply all bt full
Thread 5 (Thr
> stellarium:
> ../../../../../../../src/mesa/drivers/dri/nouveau/nv10_render.c:104:
> get_hw_format: Assertion `0' failed.
That also appears to mean "invalid format", so is probably the same bug.
> For whatever it's worth, I did the routine you described. The Stellarium
> startup screen appear
I have removed Ubuntu from this machine, so can't test under Ubuntu. I
am now running Sparky Linux (Debian testing). Stellarium still crashes
after displaying the startup screen, but I'm now getting this error
message:
stellarium:
../../../../../../../src/mesa/drivers/dri/nouveau/nv10_render.c:1
That message means "invalid/unsupported buffer format" (
http://sources.debian.net/src/mesa/10.3.2-1/src/mesa/drivers/dri/nouveau/nv10_state_fb.c
), and as it appears to refer to an internal nouveau buffer rather than
a passed-in texture, I suspect this is actually a mesa/nouveau bug.
As I do not
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079011
Title:
stellarium assert failure: nv10_state_fb.c:50: get_rt_format:
This doesn't only affect the stellarium package; it also affects
flightgear.
** Also affects: flightgear (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: stellarium (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079011
Title:
20 matches
Mail list logo
