From: Mgr. J. C. <ch...@ph...> - 2010-05-11 10:13:24
|
Dear ammazing professionals, I would like to very valuably ask You for programmers advice. I Am solving persistent issues while triing to use Ubuntu 9.10 Lucid on my IBM Thinkpat model 2668. During Lucid development cycle, very probably between end of January and half of February, some package development stage caused, that i AM getting crash of Gnome volume monitor when ever i Am booting from live USB or even after installation. The issues are not caused by The fact, that Orca is set to run automatically during startup. I found out, that The only one solution was to boot from official Ubuntu Lucid live CD or stick, activate The blindness profile at The boot screen and run installer instead of Gnome. But this approach stopped to work for me during a development cycle and now is unusable. It is very interesting issue and is only presented on IBM Thinkpat notebook model 2668. I even tried to remove pulseaudio by using apt-get purge pulse audio, i even tried to remove Alsa, apt-get purge alsa, but error message is still persisting. I only found out, that error is never occurring, if Blindness profile is not set. I AM afraid, that error is caused by some special Pulseaudio setting, which is being used if blindness profile has been set at The first boot screen. I mean by The blindness profile screen reader choice in The accessibility menu at The first boot screen. GDU volume monitor can not be simply removed, it is The part of Gnome. Would somebody try to help me please? |