Debian Bug report logs - #757152
python-pyatspi: Should depond on at-spi2-core OR qt-at-spi

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Matijs van Zuijlen <matijs@matijs.net>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: python-pyatspi: Should depond on at-spi2-core OR qt-at-spi

Date: Tue, 05 Aug 2014 21:11:31 +0200

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 to pull in part of the other.

The original bug report #749523 mentions depending on
at-spi2-core|qt-at-spi, which would allow the user to pick the most
appropriate choice. I think this would be a better solution than
depending on both packages.

I suppose another option would be to create separate
python-pyatspi-gnome and python-pyatspi-kde packages.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-pyatspi depends on:
ii  gir1.2-atspi-2.0  2.12.0-2
ii  libatk-adaptor    2.12.1-1+b1
ii  libgail-common    2.24.24-1
ii  python            2.7.8-1
ii  python-gi         3.12.1-1+b1

python-pyatspi recommends no packages.

python-pyatspi suggests no packages.

-- no debconf information

Message #10 received at 757152@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>

To: Matijs van Zuijlen <matijs@matijs.net>, 757152@bugs.debian.org

Subject: Re: Bug#757152: python-pyatspi: Should depond on at-spi2-core OR qt-at-spi

Date: Wed, 6 Aug 2014 02:18:40 +0200

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 the other.

It makes a lot of sense for a user to be told that e.g. kedit is nice,
and try to install and run it from his gnome desktop, or vice-versa with
gedit.

Or taking other more convincing examples, it makes a lot of sense for a
user to install and use vlc (just like he used to use it on Windows...)
on a Gnome desktop, or gimp (just like he used to use it on Windows...)
on a KDE dekstop.

> I suppose another option would be to create separate
> python-pyatspi-gnome and python-pyatspi-kde packages.

Average users have no idea what qt/kde vs gtk means (in particular blind
people who can not even see the difference...), and thus they won't know
which one they would have to install a particular package in order to
get access to some software.

Actually, qt-at-spi even happens to depend on at-spi2-core in the end,
so the question is about the additional packages brought by qt-at-spi.
The raw figure is, starting from a bare system without even the standard
task, plus at-spi2-core, 38MiB brought by installing qt-at-spi. But that
includes fontconfig, libice6 and other such stuff that will typically
be brought by a gnome destkop. Measuring only the extra qt libs gives
only 25MiB.  Is that saving really worth the pain of a user wondering
why this or that application is not accessible at all?

Samuel

Message #15 received at 757152@bugs.debian.org (full text, mbox, reply):

From: Gonzalo Bermúdez <gonzalob@gonz0.com.ar>

To: Debian Bug Tracking System <757152@bugs.debian.org>

Subject: Re: python-pyatspi: Should depond on at-spi2-core OR qt-at-spi

Date: Mon, 11 Aug 2014 00:30:03 -0300

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 Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-pyatspi depends on:
ii  gir1.2-atspi-2.0  2.12.0-2
ii  libatk-adaptor    2.12.1-1+b1
ii  libgail-common    2.24.24-1
ii  python            2.7.8-1
ii  python-gi         3.12.1-1+b1

python-pyatspi recommends no packages.

python-pyatspi suggests no packages.

-- no debconf information

Message #20 received at 757152@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>

To: Gonzalo Bermúdez <gonzalob@gonz0.com.ar>, 757152@bugs.debian.org

Subject: Re: Bug#757152: python-pyatspi: Should depond on at-spi2-core OR qt-at-spi

Date: Mon, 11 Aug 2014 11:43:26 +0200

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 python-pyatspi is about having
screen reading support through at-spi2, which is completely independent
from the actual desktop being used.

> and then there's gnome-core for gnome.

I don't see the relation with the issue being discussed.

Gnome has a gnome-accessibility package, which simply depends on the
gnome-ish accessibility tools (magnifier, on-screen keyboard, etc.).
Same remark as above.

> Wouldn't it make sense for those packages to actually decide which
> of the two is actually used within a given system?

Again, people don't even really realize whether they are using a
gnome or KDE application is being used. So they *need* that both be
accessible, thus the dependency on whatever it takes to make both
accessible. And if openoffice needed a java bridge to get accessible
(like it does on windows), we would also have made depended on by
python-pyatspi.

What *actual* issue do you want to solve here?

(except disk space -I've shown that it's neglectible by nowadays'
standards- or KDE vs Gnome troll)

Samuel

Message #27 received at 757152@bugs.debian.org (full text, mbox, reply):

From: Ильяс Гасанов <torso.nafi@gmail.com>

To: Samuel Thibault <sthibault@debian.org>, 757152@bugs.debian.org

Subject: Re: Bug#757152: python-pyatspi: Should depond on at-spi2-core OR qt-at-spi

Date: Sat, 16 Aug 2014 00:52:58 +0400

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 automatically be fetched and installed aside. Kind of a dirty
hack, but it seems fine at least from my perspective. I guess the same
could be stated about at-spi2-core dependences on glib/gtk packages.

Best regards,
--
Ilyas Gasanov

Message #32 received at 757152@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>

To: Ильяс Гасанов <torso.nafi@gmail.com>, 757152@bugs.debian.org

Subject: Re: Bug#757152: python-pyatspi: Should depond on at-spi2-core OR qt-at-spi

Date: Tue, 19 Aug 2014 01:49:13 +0200

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 kind of things with the maintainer of at-spi1
in the past, and the answer was a clear "come on, it's really small
dependencies by nowadays' standards, and not using them would mean
reimplementing convenience functions such as utf-8 handling, list
handling, etc.".  So this is mostly a no-go.

> Personally I can't imagine any way in which it could actually be used
> without having any qt applications to launch.

Sure, but python-pyatspi can't know whether there are some qt
applications or not.

> However, when an average user installs said software, these libs would
> automatically be fetched and installed aside. Kind of a dirty hack,
> but it seems fine at least from my perspective.

Again, what is the *actual* gain of introducing such hack? Saving 25MiB
worth of disk space, really?

Samuel

Message #39 received at 757152@bugs.debian.org (full text, mbox, reply):

From: Vlad Orlov <monsta@inbox.ru>

To: 757152@bugs.debian.org

Subject: Re: python-pyatspi: Should depond on at-spi2-core OR qt-at-spi

Date: Wed, 12 Nov 2014 11:06:21 +0300

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 caribou        Depends python-pyatspi      
i A python-pyatspi Depends qt-at-spi            
i A qt-at-spi      Depends libqtgui4 (>= 4:4.8~)

Message #44 received at 757152@bugs.debian.org (full text, mbox, reply):

From: Mrs Yeung Wong <arsilva@uem.br>

To: undisclosed-recipients:;

Subject: Business Project.‏

Date: Thu, 5 Mar 2015 02:24:09 -0300 (BRT)

[Message part 1 (text/plain, inline)]

I am Mrs Yeung Wong, pardon me for this unsolicited email. I am contacting you confidentially to discuss a secure business  project, I need your permission before I give details.

Regards,
Yeung
-- 
Esta mensagem foi verificada pelo sistema de antivirus e
 acredita-se estar livre de perigo.

[Message part 2 (text/html, inline)]

Message #49 received at 757152@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 757152@bugs.debian.org

Subject: Re: python-pyatspi: Should depond on at-spi2-core OR qt-at-spi

Date: Tue, 13 Oct 2015 14:24:22 +0200

[Message part 1 (text/plain, inline)]

On Tue, 05 Aug 2014 21:11:31 +0200 Matijs van Zuijlen
<matijs@matijs.net> wrote:
> 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 to pull in part of the other.
> 
> The original bug report #749523 mentions depending on
> at-spi2-core|qt-at-spi, which would allow the user to pick the most
> appropriate choice. I think this would be a better solution than
> depending on both packages.
> 
> I suppose another option would be to create separate
> python-pyatspi-gnome and python-pyatspi-kde packages.

Hi Samuel,

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.

Please consider moving the qt-at-spi dependency to some other package.
libqt-something might be a suitable place so it will be pulled in
automatically whenever a KDE/Qt app is installed.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #56 received at 757152@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>

To: Michael Biebl <biebl@debian.org>, 757152@bugs.debian.org

Subject: Re: Bug#757152: python-pyatspi: Should depond on at-spi2-core OR qt-at-spi

Date: Tue, 13 Oct 2015 14:30:27 +0200

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 MiB really a problem?!

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.

Samuel

Message #63 received at 757152@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Samuel Thibault <sthibault@debian.org>, 757152@bugs.debian.org

Subject: Re: Bug#757152: python-pyatspi: Should depond on at-spi2-core OR qt-at-spi

Date: Tue, 13 Oct 2015 14:38:10 +0200

[Message part 1 (text/plain, inline)]

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 like a better approach.

You mentioned kedit as an example where you want to have qt-at-spi
installed. But does qt-at-spi actually work with KDE5/Qt5 ?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #72 received at 757152@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>

To: Michael Biebl <biebl@debian.org>

Cc: 757152@bugs.debian.org

Subject: Re: Bug#757152: python-pyatspi: Should depond on at-spi2-core OR qt-at-spi

Date: Tue, 17 Nov 2015 18:21:51 +0100

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 dependency to say libqtgui4 or
> libqtcore4 (i.e. something from Qt4) looks like a better approach.

This is now done in the qt4-x11 package, so I will drop the qt-at-spi
dependency from python-pyatspi.

> You mentioned kedit as an example where you want to have qt-at-spi
> installed. But does qt-at-spi actually work with KDE5/Qt5 ?

qt-at-spi is for Qt4. While typing kedit, I actually thought kate.

Samuel

Message #77 received at 757152@bugs.debian.org (full text, mbox, reply):

From: Ritesh Raj Sarraf <rrs@debian.org>

To: Debian Bug Tracking System <757152@bugs.debian.org>

Subject: Re: python-pyatspi: Should depond on at-spi2-core OR qt-at-spi

Date: Sun, 22 Nov 2015 21:57:12 +0530

Package: python-pyatspi
Version: 2.18.0+dfsg-1
Followup-For: Bug #757152

I'm also curious to know if KDE5/Qt5 apps really support the at-spi
bridge.

>From what I've checked so far, it only works for the old KDE4/Qt4 apps.

Perhaps someone from the Debian KDE team could confirm that.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python-pyatspi depends on:
ii  at-spi2-core      2.18.3-1
ii  gir1.2-atspi-2.0  2.18.3-1
ii  libatk-adaptor    2.18.1-1
ii  libgail-common    2.24.28-1
ii  python            2.7.9-1
ii  python-gi         3.18.2-2
ii  qt-at-spi         0.4.0-3

python-pyatspi recommends no packages.

python-pyatspi suggests no packages.

-- no debconf information

Message #82 received at 757152@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>

To: Ritesh Raj Sarraf <rrs@debian.org>, 757152@bugs.debian.org

Subject: Re: Bug#757152: python-pyatspi: Should depond on at-spi2-core OR qt-at-spi

Date: Sun, 22 Nov 2015 19:49:06 +0100

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.

Samuel

Message #87 received at 757152@bugs.debian.org (full text, mbox, reply):

From: Ritesh Raj Sarraf <rrs@debian.org>

To: Samuel Thibault <sthibault@debian.org>, 757152@bugs.debian.org

Cc: debian-qt-kde@lists.debian.org

Subject: Re: Bug#757152: python-pyatspi: Should depond on at-spi2-core OR qt-at-spi

Date: Mon, 23 Nov 2015 17:11:46 +0530

[Message part 1 (text/plain, inline)]

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 seem to be working, at
least on Debian. Perhaps the Debian KDE Team (CCed) can confirm if it
is supposed to work with KDE5/Qt5, or not.


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System

[signature.asc (application/pgp-signature, inline)]

Message #92 received at 757152@bugs.debian.org (full text, mbox, reply):

From: Ritesh Raj Sarraf <rrs@researchut.com>

To: Samuel Thibault <sthibault@debian.org>, 757152@bugs.debian.org

Cc: debian-qt-kde@lists.debian.org

Subject: Re: Bug#757152: python-pyatspi: Should depond on at-spi2-core OR qt-at-spi

Date: Mon, 23 Nov 2015 21:30:49 +0530

[Message part 1 (text/plain, inline)]

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):
caribou-CRITICAL **: caribou_keyboard_model_populate_group: assertion
'group != NULL' failed
Nov 23 21:26:13 learner org.gnome.Caribou.Daemon[9980]:
(caribou:16512): GLib-GObject-CRITICAL **: g_object_ref: assertion
'G_IS_OBJECT (object)' failed
Nov 23 21:26:13 learner dbus-daemon[9980]: Successfully activated
service 'org.gnome.Caribou.Daemon'
Nov 23 21:26:17 learner org.gnome.Caribou.Daemon[9980]: **
(caribou:16512): WARNING **: AT-SPI: Error in GetItems, sender=(null),
error=Did not receive a reply. Possible causes include: the remote
application did not send a reply, the message bus security policy
blocked the reply, the reply timeout expired, or the network connection
was broken.


To me this looks like caribou daemon, which is supposed to pop-up the
soft keyboard, is mesbehaving. This message was seen when running
kwrite (kde5) which obviously will trigger the textinput field to pop-
up caribou keyboard.


On Mon, 2015-11-23 at 17:11 +0530, Ritesh Raj Sarraf 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 actually embeds its own at-spi bridge.
> 
> That was my impression too, but it does not seem to be working, at
> least on Debian. Perhaps the Debian KDE Team (CCed) can confirm if it
> is supposed to work with KDE5/Qt5, or not.
> 
> 
-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."

[signature.asc (application/pgp-signature, inline)]

Message #97 received at 757152@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>

To: Ritesh Raj Sarraf <rrs@debian.org>

Cc: 757152@bugs.debian.org, debian-qt-kde@lists.debian.org

Subject: Re: Bug#757152: python-pyatspi: Should depond on at-spi2-core OR qt-at-spi

Date: Mon, 23 Nov 2015 17:34:57 +0100

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 actually embeds its own at-spi bridge.
> 
> That was my impression too, but it does not seem to be working, at
> least on Debian.

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.

> Perhaps the Debian KDE Team (CCed) can confirm if it
> is supposed to work with KDE5/Qt5, or not.

It is supposed to work (and much better than Qt4)

Samuel

Message #102 received at 757152@bugs.debian.org (full text, mbox, reply):

From: Ritesh Raj Sarraf <rrs@debian.org>

To: Samuel Thibault <sthibault@debian.org>

Cc: 757152@bugs.debian.org, debian-qt-kde@lists.debian.org

Subject: Re: Bug#757152: python-pyatspi: Should depond on at-spi2-core OR qt-at-spi

Date: Mon, 23 Nov 2015 22:32:21 +0530

[Message part 1 (text/plain, inline)]

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 fine.
But not when in general use.

> > Perhaps the Debian KDE Team (CCed) can confirm if it
> > is supposed to work with KDE5/Qt5, or not.
> 
> It is supposed to work (and much better than Qt4)


From the logs below, it looks like caribou is the cuplprit. :-(
It says that the daemon was activated, but no soft keyboard shows up.

Nov 23 22:27:25 learner dbus-daemon[9906]: Activating service
name='org.gnome.Caribou.Daemon'
Nov 23 22:27:25 learner gnome-session[9877]: (gnome-shell:10151):
caribou-CRITICAL **: caribou_group_model_create_group_name: assertion
'group != NULL' failed
Nov 23 22:27:25 learner gnome-session[9877]: (gnome-shell:10151):
caribou-CRITICAL **: caribou_keyboard_model_populate_group: assertion
'group != NULL' failed
Nov 23 22:27:25 learner org.gnome.Caribou.Daemon[9906]:
(caribou:18991): GLib-GObject-CRITICAL **: g_object_ref: assertion
'G_IS_OBJECT (object)' failed
Nov 23 22:27:25 learner dbus-daemon[9906]: Successfully activated
service 'org.gnome.Caribou.Daemon'
Nov 23 22:27:52 learner dbus-daemon[9906]: Activating service
name='org.gnome.Caribou.Daemon'
Nov 23 22:27:52 learner systemd[1]: Starting Laptop Mode Tools -
Battery Polling Service...
Nov 23 22:27:52 learner systemd[1]: Reloading Laptop Mode Tools.
Nov 23 22:27:52 learner systemd[1]: Started Laptop Mode Tools - Battery
Polling Service.
Nov 23 22:27:52 learner gnome-session[9877]: (gnome-shell:10151):
caribou-CRITICAL **: caribou_group_model_create_group_name: assertion
'group != NULL' failed
Nov 23 22:27:52 learner gnome-session[9877]: (gnome-shell:10151):
caribou-CRITICAL **: caribou_keyboard_model_populate_group: assertion
'group != NULL' failed
Nov 23 22:27:52 learner org.gnome.Caribou.Daemon[9906]:
(caribou:19015): GLib-GObject-CRITICAL **: g_object_ref: assertion
'G_IS_OBJECT (object)' failed
Nov 23 22:27:52 learner dbus-daemon[9906]: Successfully activated
service 'org.gnome.Caribou.Daemon'
Nov 23 22:27:52 learner laptop-mode[19073]: Laptop mode
Nov 23 22:27:52 learner laptop_mode[19017]: Laptop mode
Nov 23 22:27:52 learner laptop-mode[19074]: enabled, active [unchanged]
Nov 23 22:27:52 learner laptop_mode[19017]: enabled, active [unchanged]
Nov 23 22:27:52 learner systemd[1]: Reloaded Laptop Mode Tools.
Nov 23 22:27:55 learner dbus-daemon[9906]: Activating service
name='org.gnome.Caribou.Daemon'
Nov 23 22:27:55 learner gnome-session[9877]: (gnome-shell:10151):
caribou-CRITICAL **: caribou_group_model_create_group_name: assertion
'group != NULL' failed
Nov 23 22:27:55 learner gnome-session[9877]: (gnome-shell:10151):
caribou-CRITICAL **: caribou_keyboard_model_populate_group: assertion
'group != NULL' failed
Nov 23 22:27:55 learner org.gnome.Caribou.Daemon[9906]:
(caribou:19090): GLib-GObject-CRITICAL **: g_object_ref: assertion
'G_IS_OBJECT (object)' failed
Nov 23 22:27:55 learner dbus-daemon[9906]: Successfully activated
service 'org.gnome.Caribou.Daemon'

 
-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System

[signature.asc (application/pgp-signature, inline)]

Message #107 received at 757152-close@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>

To: 757152-close@bugs.debian.org

Subject: Bug#757152: fixed in pyatspi 2.18.0+dfsg-2

Date: Sun, 29 Nov 2015 17:20:34 +0000

Source: pyatspi
Source-Version: 2.18.0+dfsg-2

We believe that the bug you reported is fixed in the latest version of
pyatspi, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 757152@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Samuel Thibault <sthibault@debian.org> (supplier of updated pyatspi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 29 Nov 2015 18:00:10 +0100
Source: pyatspi
Binary: python-pyatspi python-pyatspi2 python3-pyatspi python3-pyatspi2
Architecture: source all
Version: 2.18.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team <debian-accessibility@lists.debian.org>
Changed-By: Samuel Thibault <sthibault@debian.org>
Description:
 python-pyatspi - Assistive Technology Service Provider Interface - Python bindings
 python-pyatspi2 - Transitional package for assistive technology Python bindings
 python3-pyatspi - Assistive Technology Service Provider Interface - Python3 binding
 python3-pyatspi2 - Transitional package for assistive technology Python3 bindings
Closes: 757152
Changes:
 pyatspi (2.18.0+dfsg-2) unstable; urgency=medium
 .
   * control: Do not depend on qt-at-spi any more, now that libqtgui4 recommends
   it. Closes: Bug#757152.
Checksums-Sha1:
 4203b5a2af520175a13f48cca80dec7203db6cf5 2223 pyatspi_2.18.0+dfsg-2.dsc
 f4fea7744b7f665236b53cac62fb18068e7cdded 5169 pyatspi_2.18.0+dfsg-2.debian.tar.bz2
 926a3f47a21cc3d55d55b186b47c8a6c4373c2cd 3974 python-pyatspi2_2.18.0+dfsg-2_all.deb
 5af2ddab4843a2fcaf5bbece8ed38a315a481654 38590 python-pyatspi_2.18.0+dfsg-2_all.deb
 5d9f87ef5c4a53119fac7c7eb3384363b2e9ca10 3974 python3-pyatspi2_2.18.0+dfsg-2_all.deb
 5d52a9d65f7f08ae3c0e7480fa6ff90980d859cd 34134 python3-pyatspi_2.18.0+dfsg-2_all.deb
Checksums-Sha256:
 acf868a714d2eaa58e7c31be40b2071c3a8e15614329d7f85aa9fe5bd7d0ac7c 2223 pyatspi_2.18.0+dfsg-2.dsc
 4785bfef3626f241019d58aa7ce88077f9e661dcf86090369ce8900622bafaa6 5169 pyatspi_2.18.0+dfsg-2.debian.tar.bz2
 93165de8f5b8b02b500291675e1cf122bcc1be9285bc7a45e77d609fa93e94d2 3974 python-pyatspi2_2.18.0+dfsg-2_all.deb
 adec0f9cd1e6d2c31a88dc5f914d2d93f2ffc7a40a69cf5e170e19381ddb34ff 38590 python-pyatspi_2.18.0+dfsg-2_all.deb
 ad13012c088cfca906280f17cdcba9d826eb6b115fffd01b88e4cce080e64fb4 3974 python3-pyatspi2_2.18.0+dfsg-2_all.deb
 3d2d924610b143c6a7b166bbcb2f34b840b15ac9726eb06bd692870b5d82c89e 34134 python3-pyatspi_2.18.0+dfsg-2_all.deb
Files:
 b68564691f450365c98a758b2270a1f5 2223 python optional pyatspi_2.18.0+dfsg-2.dsc
 32f38f877985faab0357f17d5c5022e0 5169 python optional pyatspi_2.18.0+dfsg-2.debian.tar.bz2
 798fc2511503e68d9e6ed567929fb807 3974 oldlibs extra python-pyatspi2_2.18.0+dfsg-2_all.deb
 d103abed976ef344fcf8a7311982fbf4 38590 python optional python-pyatspi_2.18.0+dfsg-2_all.deb
 d19e7161378d6d5b33d27e8c29f96873 3974 oldlibs extra python3-pyatspi2_2.18.0+dfsg-2_all.deb
 9ef99cf84e5a1db4edf9d7d0e4cc34f2 34134 python optional python3-pyatspi_2.18.0+dfsg-2_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJWWy9nAAoJEAdNJfYUJ+jA1TsP/AoDqBE1/7XGbSkm7/zngeZL
3dAa5pYRoA/96YoGyLJIB6u71UHsqY9vv8cQ2W/TW9u0Z/1qmTFE0qDPd38/bxH1
vzeSfVtEX+Sf14N9IY4CpU0MaRQtbz4Kjz7tK3/OJ4UJyPP2kuDx2oqusUoUHUZ9
fS6ihigmoUH2QXwb5iDi+QxgdCctQ/M5Ew8w4xuzy1tPLECCvht8X2//rv5+yRs0
BcSRXvWy/QUUc5Pw4kmb1EYWt8lyD3SCBQ+7SpJN8PnZ4ekpJVFWwaeupstCV+Xg
NTAYoO5qu/v6zAqd948HfsO07gghHlCJmkBH6sIiFUY5foM/bHvJN/KN1f3UL1ZC
Be2ONtM1IVd3osrGfklfUbfgHtNZ1lW8VE1dst85vJr7LAIdCpBATQgjB+XL3Zun
wCuskRlJMIp2DEjkH0Oj/S+x0AZA0AnGUlcMQWWpAg/pbY6o8EV7oqjGxnk4q0z9
lWYCQzs6GcFnQILTTWe5Vy9Lt5utCB0MUzhNX2V3Am3NYgRJpLybfZq5aGOQfa7P
IjcUpiausFLX1qCBSFyr50H7vcTNU/15xrvpyjOjuGQbxoURyWKnOH0aS8FlF2m7
/31Z/3vtTOogqqbYVAlLQrigOJ6WMQqGiFDuaq8FTd425mvQSqJyE06znVPteH9Z
Z6+bXcPSduuD4gOycZDi
=VusA
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.