Re: [orca-list] GNOME Broken again on my System - WTF!



I found some maybe interesting junk in the Xorg.0.log this morning complaining about being unable to load modesetting and fbdev. I honestly hate the way x.org server can be so fragile at times. I think I ran into problems with this a while back and I ended up re-building my whole system in in order to fix this. I sure hope I don't have to do that again; I mean really. I wonder about downgrading x.org server; that was a recent change; wonder how things might work then. I'll have to look the next time I get home and have some time to muck around with my system:(.



On Mon, Aug 25, 2014 at 8:39 AM, B. Henry <burt1iband gmail com> wrote:
I don't know about  your pulse issues at all.
If you run script, or pipe stdout on tty12 where you run startx to a file, what does it show when you start gnome?
On the surface of things it seems like a temporary fix/work around would be to try rolling back the xorg updates and or
the kernel.
I've had no issues with 3.16,
There were quite a few changes/improvements to gpu support inclluding accelleration, and some audio driver stuff as well,
so depending on your hardware maybe something effects you with this kernel. I had one kernel update cause me problems
maybe 6 months ago, think it ws one of the 3.13 kernels, but may have been 3.14 I suppose. I rolled the kernel back and
all was well. Maybe two updates later I tried the new kernel version, and all was well. In fairness I only tried to startx
a couple of times, and did not investigate things at all before rolling back.
--
B.H.

On Mon, Aug 25, 2014 at 12:31:29AM -0700, Steve Holmes wrote:
> This may seem like a long story but I haven't run Orca for several
> days but after my most recent Arch Linux pacman update to kernel
> 3.16.1 and recent changes to xorg server, I seem to have major
> problems getting Orca or gnome for that matter to work now. First off
> Pulse is raising its ugly head again and screwing everything up so I
> took it out of the way for now and configured speech-dispatcher to use
> alsa as its audio output module. So now I have speech-dispatcher and
> emacspeak working again. However, when I start gnome with the startx
> command from tty12 on my system, Orca reads OK but I get a message
> saying something like "An error was encountered and all extensions
> were stopped. Only button available then is "Logout" I have to read
> these messages with flat review of Orca. I don't see any obvious
> errors and when I go into journalctl -r to read any system wide
> errors, I can't find anything that tells me anything I didn't know
> yesterday.
>
> If I re-enable pulseaudio by making the binary executable again and
> config speechd to use pulse, then running startx attempts to run the
> xorg environment but I get total silence. I hit space onece and that
> logged me out. This makes me think it is getting the same error but
> since pulse is fucked up[, I cannot confirm this error message
>
> This all seemed to work a few days ago and Orca versions don't seem to
> make any difference. I tried orca-3.12.2 and a git build of
> orca-3.13.90 something I built the other night.
>
> Any idea what may be broken here? do I have to rebuild my system to
> figure this out; I hope answer to this last question is no.:).
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> https://mail.gnome.org/mailman/listinfo/orca-list
> Visit http://live.gnome.org/Orca for more information on Orca.
> The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> Log bugs and feature requests at http://bugzilla.gnome.org
> Find out how to help at http://live.gnome.org/Orca/HowCanIHelp



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]