[impdev] Bad alloc error when starting SL viewer

[redapple]

Sorry! I didn't install the proprietary nvidia graphics driver.
With the proprietary driver kokua 3.4.5 64b starts and works.
Email: redapple at linuxmagier.de
WWW: http://redapple.linuxmagier.de
Jabber-ID: redapple at jabber.piratenpartei.de



2013/2/20 redapple <redapple at linuxmagier.de>:
> It seems to be a problem with a general ubuntu update.
> I get the same error message on LUBUNTU 64bit with Kokua 3.4.5 64Bit
> and Imprudence 1.3.2 64bit.
>
> Email: redapple at linuxmagier.de
> WWW: http://redapple.linuxmagier.de
> Jabber-ID: redapple at jabber.piratenpartei.de
>
>
>
> 2013/2/20 Nicky Perian <nickyperian at yahoo.com>:
>>  There seems to be a rash of problems related to KDE and the oxygen+gtk
>> theme. Try to use another theme and see if it works.
>> Since this is affecting all viewers it might be from an update/upgrade of
>> Kubuntu. And that is a wild guess.
>> Nicky
>>
>> ________________________________
>> From: redapple <redapple at linuxmagier.de>
>> To: impdev at lists.imprudenceviewer.org
>> Sent: Wednesday, February 20, 2013 6:54 AM
>> Subject: [impdev] Bad alloc error when starting SL viewer
>>
>> Hi impdev,
>> I am unable to start ANY SL viewer on Kubuntu 32Bit AND 64Bit.
>> I get the following errormessage with Kokua, Imprudence and even the
>> Original Second Life viewer:
>>
>> ----
>> libGL error: failed to load driver: r600
>> libGL error: Try again with LIBGL_DEBUG=verbose for more details.
>> libGL error: failed to load driver: swrast
>> libGL error: Try again with LIBGL_DEBUG=verbose for more details.
>> The program 'do-not-directly-run-imprudence-bin' received an X Window
>> System error.
>> This probably reflects a bug in the program.
>> The error was 'BadAlloc (insufficient resources for operation)'.
>>   (Details: serial 30 error_code 11 request_code 154 minor_code 3)
>>   (Note to programmers: normally, X errors are reported asynchronously;
>>   that is, you will receive the error a while after causing it.
>>   To debug your program, run it with the --sync command line
>>   option to change this behavior. You can then get a meaningful
>>   backtrace from your debugger if you break on the gdk_x_error() function.)
>> unexpected shutdown
>> ----
>>
>> What can I do or needs to be done? Do I need to install a special
>> driver package or something?
>>
>> Dan
>>
>> Email: redapple at linuxmagier.de
>> WWW: http://redapple.linuxmagier.de
>> Jabber-ID: redapple at jabber.piratenpartei.de
>> _______________________________________________
>> ImpDev mailing list
>> ImpDev at lists.imprudenceviewer.org
>> http://lists.imprudenceviewer.org/listinfo.cgi/impdev-imprudenceviewer.org
>>
>>