pocketsphinx_0.8-1_amd64.changes ACCEPTED into unstable, unstable

2013-04-18 Thread Debian FTP Masters


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 02 Jan 2013 02:14:16 +0100
Source: pocketsphinx
Binary: pocketsphinx gstreamer0.10-pocketsphinx pocketsphinx-hmm-en-hub4wsj 
pocketsphinx-lm-en-hub4 pocketsphinx-hmm-zh-tdt pocketsphinx-lm-zh-hans-gigatdt 
pocketsphinx-lm-zh-hant-gigatdt pocketsphinx-hmm-en-tidigits 
libpocketsphinx-dev libpocketsphinx1 python-pocketsphinx python-pocketsphinx-dbg
Architecture: source amd64 all
Version: 0.8-1
Distribution: unstable
Urgency: low
Maintainer: Debian Accessibility Team debian-accessibility@lists.debian.org
Changed-By: Samuel Thibault sthiba...@debian.org
Description: 
 gstreamer0.10-pocketsphinx - Speech recognition tool - gstreamer plugin
 libpocketsphinx-dev - Speech recognition tool - front-end library development 
files
 libpocketsphinx1 - Speech recognition tool - front-end library
 pocketsphinx - Speech recognition tool
 pocketsphinx-hmm-en-hub4wsj - Speech recognition tool - front-end library 
development files
 pocketsphinx-hmm-en-tidigits - Speech recognition tool - front-end library 
development files
 pocketsphinx-hmm-zh-tdt - Speech recognition tool - front-end library 
development files
 pocketsphinx-lm-en-hub4 - Speech recognition tool - front-end library 
development files
 pocketsphinx-lm-zh-hans-gigatdt - Speech recognition tool - front-end library 
development files
 pocketsphinx-lm-zh-hant-gigatdt - Speech recognition tool - front-end library 
development files
 python-pocketsphinx - Speech recognition tool - python bindings
 python-pocketsphinx-dbg - Speech recognition tool - python bindings
Closes: 697152
Changes: 
 pocketsphinx (0.8-1) unstable; urgency=low
 .
   * Initial release (Closes: #697152)
Checksums-Sha1: 
 7cc4478735a21c71b8a77ac507d2fe1ebcd33014 2870 pocketsphinx_0.8-1.dsc
 d9efdd0baddd2e47c2ba559caaca62ffa0c0eede 23781837 pocketsphinx_0.8.orig.tar.gz
 755df80d21753a70f6c6e21e6815134df2633480 4541 pocketsphinx_0.8-1.debian.tar.gz
 68f4cf45582885ddbcd8c38131cf55636915a439 1030474 pocketsphinx_0.8-1_amd64.deb
 61db301282f67481f600873f0203339e791f058e 19226 
gstreamer0.10-pocketsphinx_0.8-1_amd64.deb
 3b52fc8fa0dfe4d3de0a8d889d1a6ec570a41c4f 2670126 
pocketsphinx-hmm-en-hub4wsj_0.8-1_all.deb
 8eef1a1544d77f88727fa11628f6521c473a307a 5267372 
pocketsphinx-lm-en-hub4_0.8-1_all.deb
 b1a652825e1330979288801223946b062c290b62 2197492 
pocketsphinx-hmm-zh-tdt_0.8-1_all.deb
 0335b6e603285a4769e14aa2763e295c333cd92f 3750332 
pocketsphinx-lm-zh-hans-gigatdt_0.8-1_all.deb
 f5b17cd99e3d4e8a1b2df7929657f160f0d858ac 3748202 
pocketsphinx-lm-zh-hant-gigatdt_0.8-1_all.deb
 9e991433572ba79282739dcd97bc520d29c32075 351138 
pocketsphinx-hmm-en-tidigits_0.8-1_all.deb
 36bb6ceb661f4d49e9566fb07790539a3d3d337c 163558 
libpocketsphinx-dev_0.8-1_amd64.deb
 036aea699e9ab3e0454066a5e79efa1edb77beec 127086 
libpocketsphinx1_0.8-1_amd64.deb
 ffb8664588ed5e0ad5fb7a8228b5260d146ecf4c 74744 
python-pocketsphinx_0.8-1_amd64.deb
 03213161ab3c3448d545f7028725e86ab33830e0 91284 
python-pocketsphinx-dbg_0.8-1_amd64.deb
Checksums-Sha256: 
 bbaa0fca3456307fa6a041a3ae1333fb78cdafa88d3248fee2ef25c59dde5996 2870 
pocketsphinx_0.8-1.dsc
 874c4c083d91c8ff26a2aec250b689e537912ff728923c141c4dac48662cce7a 23781837 
pocketsphinx_0.8.orig.tar.gz
 eea8957f28f4a614d53da272c339fe71b117125838176d0e373993927900553f 4541 
pocketsphinx_0.8-1.debian.tar.gz
 83ed72e3a57dba3319f44b97a933ee82617ec8817d0c08a6f5d8e811cc2fabf4 1030474 
pocketsphinx_0.8-1_amd64.deb
 0aa69546f178f12d0d262f7c4d5acdc73d713d0cc8de908917a9ccbb36f2ca9b 19226 
gstreamer0.10-pocketsphinx_0.8-1_amd64.deb
 5d9b15f2c1b0a51dfaad2a519c42efb0a3677475886e1ebe6d2808a1c045450f 2670126 
pocketsphinx-hmm-en-hub4wsj_0.8-1_all.deb
 2500e1d1ad6447f8f30db33e7376b9689901a95361558b379c92814439d1145e 5267372 
pocketsphinx-lm-en-hub4_0.8-1_all.deb
 b6aa7399e6c6ce2612e916fa49bdee973612214fa71549258aaf8ca21f0cf1d5 2197492 
pocketsphinx-hmm-zh-tdt_0.8-1_all.deb
 21215c13f406654898dae68f73992032492b3534090cabfd4ff76fc7aa824011 3750332 
pocketsphinx-lm-zh-hans-gigatdt_0.8-1_all.deb
 78bdbbd970f449d92a98404dddef5d0574c0c796eb62f843dd96ff46e363252b 3748202 
pocketsphinx-lm-zh-hant-gigatdt_0.8-1_all.deb
 58c03dd2195f00d66e1a500e47e59d7750cf27ed44824af4f2d37fc0fa1795b3 351138 
pocketsphinx-hmm-en-tidigits_0.8-1_all.deb
 e0585c6bfdc205ce93e08da35b4cd2e121609a1315cbfad78fb1d7d775e3abed 163558 
libpocketsphinx-dev_0.8-1_amd64.deb
 7d858c545caf0bb9750336306aac556647e21d0a221e1b491a9585a73d950671 127086 
libpocketsphinx1_0.8-1_amd64.deb
 013e41de056d639ea86896c8e8b992efe75edf589b466e653931d265c7afb983 74744 
python-pocketsphinx_0.8-1_amd64.deb
 a731de0566af80d03fb3f2d6e13fd9638fab70f50a534a7ad6ef0edbaa7a35f0 91284 
python-pocketsphinx-dbg_0.8-1_amd64.deb
Files: 
 51471681406774573cf1d41840cf370e 2870 sound extra pocketsphinx_0.8-1.dsc
 9f6fb6277d57fb33d2c49d4184587d26 23781837 sound extra 
pocketsphinx_0.8.orig.tar.gz
 63f0ae070e39864196e720be8fd579bc 4541 sound extra 
pocketsphinx_0.8-1.debian.tar.gz
 

QT-ATSPI information in Debian Wiki

2013-04-18 Thread administrador

Hello all,

I use some QT Applications (such as VLC, skype and virtualbox) via 
qt-at-spi, but I can not find information about how to set QT-At-spi (I 
believe that it is not by default in a Debian Wheezy installation). Do 
you believe that would be possible add information about the Qt-At-spi 
and how to set your accessibility in the Debian Wiki?


I would do it, but my English level is not good. I translate the wiki 
accessibility pages into Spanish.


I found information at 
http://techbase.kde.org/Development/Tutorials/Accessibility/Screen_Reader_Setup


Greetings.
Manuel.


--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/ed6187cbc860562afc71bad830469...@geekdotnet.misite.mx



Re: Bug#704934: unblock: gnome-session/3.4.2.1-4 gdm3/3.4.1-7

2013-04-18 Thread Cyril Brulebois
Samuel Thibault sthiba...@debian.org (18/04/2013):
 Cyril Brulebois, le Thu 18 Apr 2013 00:06:05 +0200, a écrit :
  Not sure what to do with brltty yet (discovered it earlier today).
  AFAICT updating it in wheezy would be feasible without reuploading
  d-i, just by making sure it migrates (along with those two) before
  images are built.
 
 Yes.

Great. I'll handle the unblock/urgent request.

  Samuel, can you please confirm it's all we need/want on the a11y
  front before we put an final end to the d-i wheezy rc2
  preparation?
 
 There's unfortunately the finish-install update which was missing to
 enable gdm accessibility when having installed through speakup
 (Bug#705599).  And also the sound_events enabling for brltty, which
 I've appended to Bug#705530.

Please file a separate bug for the udeb (and let me know, even if I
happen to still be subscribed to debian-a11y@); we'll try and make
sure both finish-install and brltty get fixed for r1.


Mraw,
KiBi.


signature.asc
Description: Digital signature


Strange behaviour with orca

2013-04-18 Thread Sebastian Humenda
Hello,

after an action I cannot recall, orca does the following:
1. navigation in Iceweasel or even Firefox is impossible, except for tabbing
  links; the other screen-reader-specific navigation features (h for heading or
  even the arrow keys) don't work.
2. all features of orca do not work, I've e. g. tried orca-key + space or
  orca-key + tab.

I already removed the configuration and made a new one with orca -t, therefore
it is not that I have the wrong keyboard layout. I also purge the package and
reinstalled it with no luck.

Attached is also a debug log, maybe that helps.
Has anyone an idea?

Thanks
Sebastian
-- 
Web: http://www.crustulus.de   | Blog (eng / deu): http://www.crustulus.de/blog
Freies Latein-Deutsch-Wörterbuch: http://www.crustulus.de/freedict.de.html
FreeDict: Free multilingual dictionary databases - http://www.freedict.org


signature.asc
Description: Digital signature


Re: Strange behaviour with orca

2013-04-18 Thread Dave Hunt
I experience this sort of thing whenever I use GNOME 3.4.2 on this 
netbook that has an Atom cpu.  In my case, it's a crash of at-spi2-core. 
 earlier and later GNOME releases do not exhibit this behavior.


What GNOME version are you using on what processor?

You can get functionality back by logging out and back in, or by 
restarting the system; That is, assuming your issue is same as mine.



--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51704927.1040...@gmail.com



Re: Strange behaviour with orca

2013-04-18 Thread Sebastian Humenda
Hello Dave,

Dave Hunt schrieb am 18.04.2013, 15:27 -0400:
I experience this sort of thing whenever I use GNOME 3.4.2 on this
netbook that has an Atom cpu.  In my case, it's a crash of
at-spi2-core.  earlier and later GNOME releases do not exhibit this
Hm, I get this now regularly after every login / reboot of the system. „pgrep
at-spi” returns two pid's, so I guess it is running.

When the crash happened, is it also impossible for you to open the preferences
menu?

What GNOME version are you using on what processor?
I'm not sure which processor, but definitely no Atom, some Intel single-core.
I'm using Debian Unstable with GNOME 3.4 and Orca  3.4.2.

Sebastian
-- 
Web: http://www.crustulus.de   | Blog (eng / deu): http://www.crustulus.de/blog
Freies Latein-Deutsch-Wörterbuch: http://www.crustulus.de/freedict.de.html
FreeDict: Free multilingual dictionary databases - http://www.freedict.org


signature.asc
Description: Digital signature


Re: Strange behaviour with orca

2013-04-18 Thread Dave Hunt
MMHM, some other older Intel chip may have the problem with GNOME 3.4. 
Interestingly, I cannot seem to get the crash on an old Dell laptop 
having a Pentium MI single-core at 1 GHZ.


When I have the crash, no Orca binding works.  Also, Orca cannot track 
the cursor, even in things like gedit windows.  I didn't check which 
at-spi2 components were running, but the problem reporters in both 
Ubuntu 12.04 and Fedora 17 (both use that version of GNOME) flag 
at-spi2-core as the problem component.  I can get the crash to happen 
very quickly by visiting almost any youtube page and moving about.




Cheers,



Dave




--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51704e4a.7090...@gmail.com



Re: Strange behaviour with orca

2013-04-18 Thread Sebastian Humenda
Hi Dave,

Dave Hunt schrieb am 18.04.2013, 15:49 -0400:
When I have the crash, no Orca binding works.  Also, Orca cannot
track the cursor, even in things like gedit windows.  I didn't check
No, it seems that we are talking about different problems. First of all my
problem is there from the very beginning of the orca session and furthermore I
can read texts in Gedit as usual.

Best
Sebastian
-- 
Web: http://www.crustulus.de   | Blog (eng / deu): http://www.crustulus.de/blog
Freies Latein-Deutsch-Wörterbuch: http://www.crustulus.de/freedict.de.html
FreeDict: Free multilingual dictionary databases - http://www.freedict.org


signature.asc
Description: Digital signature


Re: Strange behaviour with orca

2013-04-18 Thread Sebastian Humenda
Hello again,

I've added a new user and started a GNOME session there. Voilà, it works again
like expected. It seems to me, that something in my personal at-spi-settings got
garbled, since I've already reconfigured orca.

Any ideas on this?
Sebastian
-- 
Web: http://www.crustulus.de   | Blog (eng / deu): http://www.crustulus.de/blog
Freies Latein-Deutsch-Wörterbuch: http://www.crustulus.de/freedict.de.html
FreeDict: Free multilingual dictionary databases - http://www.freedict.org


signature.asc
Description: Digital signature


Re: QT-ATSPI information in Debian Wiki

2013-04-18 Thread Samuel Thibault
Hello,

administra...@geekdotnet.misite.mx, le Thu 18 Apr 2013 08:52:25 -0500, a écrit :
 I use some QT Applications (such as VLC, skype and virtualbox) via
 qt-at-spi, but I can not find information about how to set QT-At-spi

I have just added the information on
http://wiki.debian.org/accessibility :

“For KDE accessibility, the qt-at-spi package needs to be installed,
and the QT_ACCESSIBILITY environment variable has to be set to 1.”

About Skype, note that IIRC it renders its own widgets by itself, so
that it will be completely inaccessible, even if it uses qt for some
other things.

Samuel


-- 
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130419001444.gl9...@type.youpi.perso.aquilenet.fr



Re: Bug#705599: finish-install: 07speakup needs to be updated for Wheezy and GNOME 3

2013-04-18 Thread Samuel Thibault
Raphael Hertzog, le Thu 18 Apr 2013 08:27:01 +0200, a écrit :
 1/ you're setting up dbus within d-i instead of letting it happen during
the first boot like on other installation scenarios

? I don't undesrstand this: it only sets up a temporary session just for
setting the value.

 2/ the multiple dbus-launch means that you start multiple dbus that are
left around during the installation (this goes against policy-rc.d
which disables daemons on purpose)

Right, I forgot to kill the daemon afterwards.

 3/ you change directly the user configuration instead of adjusting
the defaults (this one is debatable since supplementary users might
not want a11y enabled by default but this is a minor inconvenience)

Yes, thus Cc-ing debian-accessibility.  I'm not sure what we really
want.  Most often, users (other than the person who installed the system
with braille or speech) will not want accessibility being enabled.

On the other hand, just changing the default could be less surprising
than having a configured user.

But on the other hand again, having a file in
/usr/share/glib-2.0/schemas outside of dpkg's knowledge is not a good
thing either, and people will wonder how this script ended up there, and
not coming from a package.

 4/ if the system is reconfigured so that gsettings uses something else
than dconf as backend,

Urgl, so gsettings might be storing parameters another way, depending on
the system preference?  That, however is really a problem indeed.

Would it be possible to store a schema file somewhere in the user home?

Now, an issue is that while finish-install can be updated with a new
patch without rebuilding debian-installer, brltty can not, and rc2,
supposed to be used for 7.0.0, is already on its way.  Ideally we'd use
the same strategy for both the speakup and the brltty installations...

Samuel


-- 
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130419003649.gn9...@type.youpi.perso.aquilenet.fr