Bug#862008: crashes, segmentation fault
I am looking at the line of code which caused the crash and it is the same line of code as in the bug I reported. So you might have been doing something different, but it appears to be the same bug which needs to be fixed in AT-SPI2. --joanie On 05/07/2017 09:14 AM, Mika Hanhijärvi wrote: > > > If it is the same bug then I have to say I did not close any application > when Orca crashed. I also did not do anythything particularly fast. I am > not 100% sure what I Was doing but If I remember correctly I just > switched between virtual Gnome desktops which did have some application > windows open. > > > > > On 05/07/2017 03:45 PM, Joanmarie Diggs wrote: >> That is this AT-SPI2 bug: >> https://bugzilla.gnome.org/show_bug.cgi?id=767074 >> >> --joanie >> >> On 05/07/2017 08:00 AM, Mika Hanhijärvi wrote: >>> Package: gnome-orca >>> Version: 3.22.2-3 >>> Severity: grave >>> >>> Orca seems to sometime crash suddenly without any warning. This is >>> not good >>> because blind users like me have to rely on screen reader working >>> reliably. >>> This, or similar, problem also existed before the latest update to >>> Orca in >>> Debian Stretch, so I do not know if this has anything to do with the >>> latest >>> Orca update. >>> >>> There are these lines in the /var/log/syslog >>> >>> May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal >>> Python error: >>> Segmentation fault >>> May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack >>> (most recent >>> call first): >>> May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: File >>> "/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184 >>> in >>> May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: File >>> "/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in >>> _queuePrintln >>> May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: File >>> "/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in >>> _dequeue >>> May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: File >>> "/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start >>> May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: File >>> "/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start >>> May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: File >>> "/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main >>> May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: File >>> "/usr/bin/orca", line 269 in main >>> May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: File >>> "/usr/bin/orca", line 272 in >>> >>> >>> >>> >>> -- System Information: >>> Debian Release: 9.0 >>>APT prefers testing >>>APT policy: (500, 'testing') >>> Architecture: amd64 >>> (x86_64) >>> Foreign Architectures: i386 >>> >>> Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) >>> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) >>> Shell: /bin/sh linked to /bin/dash >>> Init: systemd (via /run/systemd/system) >>> >>> Versions of packages gnome-orca depends on: >>> ii gir1.2-glib-2.01.50.0-1+b1 >>> ii gir1.2-gtk-3.0 3.22.11-1 >>> ii gir1.2-pango-1.0 1.40.5-1 >>> ii gir1.2-wnck-3.03.20.1-3 >>> ii gsettings-desktop-schemas 3.22.0-1 >>> ii python3-brlapi 5.4-7 >>> ii python3-cairo 1.10.0+dfsg-5+b1 >>> ii python3-gi 3.22.0-2 >>> ii python3-louis 3.0.0-3 >>> ii python3-pyatspi2.20.3+dfsg-1 >>> ii python3-speechd0.8.6-4 >>> pn python3:any >>> ii speech-dispatcher 0.8.6-4 >>> >>> Versions of packages gnome-orca recommends: >>> ii libgail-common 2.24.31-2 >>> ii xbrlapi 5.4-7 >>> >>> gnome-orca suggests no packages. >>> >>> -- no debconf information >>> >>> > >
Bug#862008: crashes, segmentation fault
That is this AT-SPI2 bug: https://bugzilla.gnome.org/show_bug.cgi?id=767074 --joanie On 05/07/2017 08:00 AM, Mika Hanhijärvi wrote: > Package: gnome-orca > Version: 3.22.2-3 > Severity: grave > > Orca seems to sometime crash suddenly without any warning. This is not good > because blind users like me have to rely on screen reader working reliably. > This, or similar, problem also existed before the latest update to Orca in > Debian Stretch, so I do not know if this has anything to do with the latest > Orca update. > > There are these lines in the /var/log/syslog > > May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Fatal Python > error: > Segmentation fault > May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: Stack (most recent > call first): > May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: File > "/usr/lib/python3/dist-packages/pyatspi/Accessibility.py", line 184 in > > May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: File > "/usr/lib/python3/dist-packages/orca/event_manager.py", line 256 in > _queuePrintln > May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: File > "/usr/lib/python3/dist-packages/orca/event_manager.py", line 329 in _dequeue > May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: File > "/usr/lib/python3/dist-packages/pyatspi/registry.py", line 155 in start > May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: File > "/usr/lib/python3/dist-packages/orca/orca.py", line 561 in start > May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: File > "/usr/lib/python3/dist-packages/orca/orca.py", line 712 in main > May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: File > "/usr/bin/orca", line 269 in main > May 7 11:21:12 miksuhlaptop2 orca-autostart.desktop[3579]: File > "/usr/bin/orca", line 272 in > > > > > -- System Information: > Debian Release: 9.0 > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 > (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages gnome-orca depends on: > ii gir1.2-glib-2.01.50.0-1+b1 > ii gir1.2-gtk-3.0 3.22.11-1 > ii gir1.2-pango-1.0 1.40.5-1 > ii gir1.2-wnck-3.03.20.1-3 > ii gsettings-desktop-schemas 3.22.0-1 > ii python3-brlapi 5.4-7 > ii python3-cairo 1.10.0+dfsg-5+b1 > ii python3-gi 3.22.0-2 > ii python3-louis 3.0.0-3 > ii python3-pyatspi2.20.3+dfsg-1 > ii python3-speechd0.8.6-4 > pn python3:any > ii speech-dispatcher 0.8.6-4 > > Versions of packages gnome-orca recommends: > ii libgail-common 2.24.31-2 > ii xbrlapi 5.4-7 > > gnome-orca suggests no packages. > > -- no debconf information > >
Bug#859262: Re: freezes Orca screen reader
On 05/02/2017 03:26 PM, Paul Gevers wrote: > @Joanmarie, did you get any feedback on the Orca list? Nope. I take that to mean all is well. --joanie
Bug#859262: Re: freezes Orca screen reader
Thanks Paul. >From your output I see you clicked on the Apply button in Synaptic, a bunch of events from DEAD accessible objects resulted, that Orca kept processing events, presented the window you Alt+Tabbed into, etc. Having said that, if memory serves me, even before the changes I made, Orca kept processing events, and probably would have presented the window you Alt+Tabbed into. In other words, I don't know if, from the user's perspective, anything has changed. But it appears that I've done all I can do in Orca (i.e. handling the exceptions it's getting from AT-SPI2 as a result of querying Synaptic for information via AT-SPI2). --joanie On 04/30/2017 02:38 PM, Paul Gevers wrote: > Hi Joanmarie, > > On Sat, 29 Apr 2017 11:51:28 -0400 Joanmarie Diggs <jdi...@igalia.com> > wrote: >> I've asked on the Orca list for testing, and we have enough users that >> use master and respond quite quickly to calls for testing, that we >> should know soon enough. > > As you have seen, I already created a Debian package with your commits > included. Please find attached a debug log generated while running > Synaptic with this new Orca package (3.22.2 based) and verify that it > looks like intended now. > > @all reading this bug, feedback is welcome. > > Paul > > P.S. I'll probably start working on getting Orca to produce sound on my > laptop soon, so that I can actually test what I am doing ;) >
Bug#859262: Re: freezes Orca screen reader
On 04/29/2017 10:55 AM, Paul Gevers wrote: > And to prepare for fixes of the package in Debian (which is 3.22.2 and > will be extremely hard convince the release managers to update in this > stage due to the freeze), which fixes would we need to backport to fix > the issues identified so far? - commit ea02cc2d268348c22ffe8c23099f6b023d4c90a7 Author: Joanmarie Diggs <jdi...@igalia.com> Date: Sat Apr 29 11:38:17 2017 -0400 Handle yet another Atspi "The process appears to be hung" exception commit 382c5408afc7dd25f9b477a5e30c50ba917155c0 Author: Joanmarie Diggs <jdi...@igalia.com> Date: Sat Apr 29 11:28:17 2017 -0400 Add check for dead accessibles before attempting to generate presentation commit d51f87a7f000d099da98247dc7ca337b2b5483be Author: Joanmarie Diggs <jdi...@igalia.com> Date: Fri Apr 28 15:35:39 2017 -0400 Handle another Atspi "The process appears to be hung" exception commit edbfafbd89409bfb1e4a4e3a9339c0b2de7435d6 Author: Joanmarie Diggs <jdi...@igalia.com> Date: Thu Apr 27 06:35:11 2017 -0400 Return immediately in isLayoutOnly() if obj is dead - Note that 382c540 may need to be reverted. Hopefully not. But rather than playing endless whac-a-mole with Atspi errors resulting from whatever it is Synaptic is doing, I am sanity checking much earlier on in the process. There is the possibility that doing so will cause other badly-behaved apps to not be presented. :-/ I've asked on the Orca list for testing, and we have enough users that use master and respond quite quickly to calls for testing, that we should know soon enough. I believe I've already said this, but I'll say it again: Getting to the bottom of the Synaptic and/or AT-SPI problem(s) should be done. (Something I'm afraid I don't have time for. Sorry!) --joanie
Bug#859262: Re: freezes Orca screen reader
So I just handled the value-related "The process appears to be hung" exception. I saw that you also had the name-related exception. But the line number suggests to me that you don't have another change I made, namely to return immediately in isLayoutOnly() if obj is dead. I'm not positive, but I'm hopeful that check will prevent the name-related exception. (And if not, I'd like to know that.) Therefore, before you try to log other issues, would you mind pulling master or the gnome-3-24 branch so you have the latest? Thanks again! --joanie On 04/28/2017 03:08 PM, Paul Gevers wrote: > Hi, > > On 23-04-17 19:27, Paul Gevers wrote: >> On 23-04-17 15:32, Joanmarie Diggs wrote: >>> That segfault is an AT-SPI2 bug. And apparently an elusive one. >>> https://bugzilla.gnome.org/show_bug.cgi?id=767074 >> >> Just to get things straight, do you mean here that you do or that you >> don't believe this segfault has anything to do with the current bug? > > Pending an answer :) > >> If not, I can try getting logs until I am not hit by this segfault AND >> there is something more in the log than the already known issue. > > Not sure if there is anything interesting in the log, but I have a new > one where orca didn't crash. Does that help? > > Paul >
Bug#859262: Re: freezes Orca screen reader
It identifies an unhandled exception which I can handle. Again, that may or may not magically make Orca present synaptic. Thanks for the log! --joanie On 04/28/2017 03:08 PM, Paul Gevers wrote: > Hi, > > On 23-04-17 19:27, Paul Gevers wrote: >> On 23-04-17 15:32, Joanmarie Diggs wrote: >>> That segfault is an AT-SPI2 bug. And apparently an elusive one. >>> https://bugzilla.gnome.org/show_bug.cgi?id=767074 >> >> Just to get things straight, do you mean here that you do or that you >> don't believe this segfault has anything to do with the current bug? > > Pending an answer :) > >> If not, I can try getting logs until I am not hit by this segfault AND >> there is something more in the log than the already known issue. > > Not sure if there is anything interesting in the log, but I have a new > one where orca didn't crash. Does that help? > > Paul >
Bug#859262: Re: freezes Orca screen reader
That segfault is an AT-SPI2 bug. And apparently an elusive one. https://bugzilla.gnome.org/show_bug.cgi?id=767074 On 04/23/2017 04:46 AM, Paul Gevers wrote: > Hi Joanmarie, > > Yesterday, I send you a log while Synaptic had not much to do, because I > ran it earlier the same day (so maybe the original issue wasn't there). > Today I tried again, hoping that there were updates to apply, which > there were. orca segfaulted on me. Please see the attached stack trace. > Maybe it tells more than the one of yesterday. > > paul@testavoira ~/tmp $ orca > /usr/lib/python3/dist-packages/pyatspi/Accessibility.py:184: Warning: > g_object_unref: assertion 'G_IS_OBJECT (object)' failed > Atspi.Event.host_application = property(fget=lambda x: > x.source.get_application()) > Segmentation fault > paul@testavoira ~/tmp $ > > For people normally running orca, would it get automatically restarted, > such that it would appear to hang, will in reality it was restarting? Or > is it more likely I experienced another bug, maybe related to debugging? > Or maybe the behavior is slightly different between the Debian version > and my (newer) version of orca. > > Paul >
Bug#859262: Fwd: Re: Bug#859262: Re: freezes Orca screen reader
Thanks! From a quick glance, Orca isn't frozen. Orca is still getting and processing accessibility events even after that error. But it's getting those events from defunct accessible objects, objects with ROLE_INVALID, etc. I'll take a longer look next week and handle the currently-unhandled error. But the problem may persist. Orca cannot bring defunct/invalid objects back from the dead; it can only try to gracefully step around their bodies. Thus getting to the bottom of the Synaptic and/or AT-SPI2 issues needs to occur. I'd be curious to know what happens if, when the Synaptic issue occurs, you Alt+Tab into another accessible application. Does Orca present your interactions with that app? Thanks again! --joanie On 04/22/2017 03:25 PM, Paul Gevers wrote: > Resending with Thunderbird mail.strictly_mime set to true, because your > host refused my message. I hope this one reaches you. Reply-To set to > the bug. > > Paul > > > Forwarded Message > Subject: Re: Bug#859262: Re: freezes Orca screen reader > Date: Sat, 22 Apr 2017 21:07:08 +0200 > From: Paul Gevers <elb...@debian.org> > To: Joanmarie Diggs <jdi...@igalia.com>, 859...@bugs.debian.org > > Hi Joanmarie, > > On 19-04-17 22:35, Joanmarie Diggs wrote: >> Please send me a full debug.out, captured from Orca master or Orca >> 3.24.x (i.e. current stable). Instructions here: >> https://wiki.gnome.org/Projects/Orca/Debugging > > I hope the attached log contains enough information for you to work it out. > > Mind you, my Orca setup isn't speaking (as can be seen from the top of > the log), but I think it captures the same error as reported in this bug > already. > > I created a Debian package for the 3.24 version which I build on > debomatic¹ for this purpose. > > Paul > > ¹ > http://debomatic-amd64.debian.net/distribution#unstable/gnome-orca/3.24.0-1 >
Bug#859262: Re: freezes Orca screen reader
On 04/19/2017 04:28 PM, Samuel Thibault wrote: > Niels Thykier, on mer. 19 avril 2017 20:19:00 +, wrote: >> Time to hunt for some dbus experts who can tell us why a process might >> fail to respond to a ping. > > Well, the application could simply be busy doing other stuff, like > processing huge packages lists for synaptic. And that's not a reason > for Orca to freeze, for me that's the most important bug to fix: Orca > shouldn't rely on applications behaving correctly. Orca knows better than to do that. ;) There may be yet another bad behavior that it's failing to handle. Please send me a full debug.out, captured from Orca master or Orca 3.24.x (i.e. current stable). Instructions here: https://wiki.gnome.org/Projects/Orca/Debugging Thanks. --joanie
