On Sun, 2015-11-22 at 19:49 +0100, Samuel Thibault wrote:
> Ritesh Raj Sarraf, on Sun 22 Nov 2015 21:57:12 +0530, wrote:
> > I'm also curious to know if KDE5/Qt5 apps really support the at-spi
> > bridge.
>
> Qt5 actually embeds its own at-spi bridge.
That was my impression too, but it does not
On Mon, 2015-11-23 at 17:34 +0100, Samuel Thibault wrote:
> It is working, at least basically. the
> ssh://git.debian.org/git/pkg-a11y/check-a11y tool shows that both qt4
> and qt5 applications are accessible at the same time.
>
Oh! Thanks for pointing that out Samuel. Those tests are working
Hello,
Ritesh Raj Sarraf, on Mon 23 Nov 2015 17:11:46 +0530, wrote:
> On Sun, 2015-11-22 at 19:49 +0100, Samuel Thibault wrote:
> > Ritesh Raj Sarraf, on Sun 22 Nov 2015 21:57:12 +0530, wrote:
> > > I'm also curious to know if KDE5/Qt5 apps really support the at-spi
> > > bridge.
> >
> > Qt5
I think there is a problem when both the frameworks are in use
together.
Nov 23 21:26:13 learner gnome-session[9951]: (gnome-shell:10216):
caribou-CRITICAL **: caribou_group_model_create_group_name: assertion
'group != NULL' failed
Nov 23 21:26:13 learner gnome-session[9951]: (gnome-shell:10216):
Hello,
Michael Biebl, on Tue 13 Oct 2015 14:38:10 +0200, wrote:
> Am 13.10.2015 um 14:30 schrieb Samuel Thibault:
> > Well, let's have a look at solution, but to me this is really religious
> > haircutting, and will most probably hurt people who need it.
>
> As said, I think moving the qt-at-spi
Michael Biebl, le Tue 13 Oct 2015 14:24:22 +0200, a écrit :
> this needs to be fixed. Otherwise I'll have to consider dropping
> gnome-orca from the default GNOME installation.
>
> Pulling in unused KDE and Qt libraries is not desirable on a default
> GNOME installation.
Is pulling a handful of
Am 13.10.2015 um 14:30 schrieb Samuel Thibault:
> Well, let's have a look at solution, but to me this is really religious
> haircutting, and will most probably hurt people who need it.
As said, I think moving the qt-at-spi dependency to say libqtgui4 or
libqtcore4 (i.e. something from Qt4) looks
Aha, looks like I've found the culprit responsible for Cinnamon indirectly
depending on Qt libs :-/
$ aptitude why libqtgui4
i cinnamon Depends caribou
i A caribouDepends python-pyatspi
i A python-pyatspi Depends qt-at-spi
i A qt-at-spi
Hello,
Ильяс Гасанов, le Sat 16 Aug 2014 00:52:58 +0400, a écrit :
Aren't there other options considerable - like, making qt-at-spi package
itself not depend on qt4 libs?
[...]
I guess the same could be stated about at-spi2-core dependences on
glib/gtk packages.
I had discussed about such
Hello,
Aren't there other options considerable - like, making qt-at-spi package
itself not depend on qt4 libs? Personally I can't imagine any way in
which it could actually be used without having any qt applications to
launch. However, when an average user installs said software, these libs
would
Hello,
Gonzalo Bermúdez, le Mon 11 Aug 2014 00:30:03 -0300, a écrit :
There's already a package named kdeaccessibility,
This package has very little to do with at-spi2 actually.
kdeaccessibility simply depends on the kde-ish accessibility tools
(magnifier, text to speech, etc.), while
Package: python-pyatspi
Version: 2.10.0+dfsg-1
Followup-For: Bug #757152
There's already a package named kdeaccessibility, and then there's gnome-core
for gnome. Wouldn't it make sense for those packages to actually decide which
of the two is actually used within a given system?
-- System
Package: python-pyatspi
Version: 2.10.0+dfsg-2
Severity: normal
This latest version of the python-pyatspi package depends on both
at-spi2-core and qt-at-spi, which each depend on part of gnome and kde,
respectively. In the common case, only one of these desktops is
installed and it makes no sense
Hello,
Matijs van Zuijlen, le Tue 05 Aug 2014 21:11:31 +0200, a écrit :
This latest version of the python-pyatspi package depends on both
at-spi2-core and qt-at-spi,
Yes, this is on purpose.
In the common case, only one of these desktops is installed and it
makes no sense to pull in part of
14 matches
Mail list logo
