From kb8aey at verizon.net Tue Jan 2 18:32:44 2007 From: kb8aey at verizon.net (mike coulombe) Date: Tue, 02 Jan 2007 12:32:44 -0600 (CST) Subject: trouble with live cd Message-ID: <0JB9004PQ7IHLHVL@vms040.mailsrvcs.net> Hi, has anyone tried the latest live CD. I downloaded the CD of feisty today and it loads fine. However after doing the orca setup and then logging out and back in by using ctrl alt and backspace nothing works. I am no longer able to run orca and I don't think the keyboard is working. I tried this again by logging out with out running orca. This time like before I didn't get the music when the desktop came up, but I was able to run orca do the setup. When I logged out and back in like before it didn't speak. Are there problems with the current live CD. Thanks Mike. X-Antivirus: avast! (VPS 0666-1, 12/31/2006), Outbound message X-Antivirus-Status: Clean From softy.lofty.ilp at btinternet.com Tue Jan 2 20:48:43 2007 From: softy.lofty.ilp at btinternet.com (Ian Pascoe) Date: Tue, 2 Jan 2007 20:48:43 -0000 Subject: Accessibility with System Admin Tools Message-ID: Hi All I seem to remember from a posting back during last summer that it was proposed that work should be done on Ubuntu's Admin tools to increase their accessibility - has this started or been done? I have just used the Update Manager, and the verbal responses back , if I were just relying on these, are poor - I have some partial sight left so could at least work out what was happening on the screen with a lot of concentration. The problems encountered were: 1. Up to the Check button screen, the verbal responses were available and usable. Once this button had been clicked, the verbal responses were negligible. When the screen pane changed there was sometimes a verbal response but cut off before it was intelligible. Also tabbing around the screen produced no responses although I am fairly sure that the focus changed. 2. During the update I could not get Orca to talk to me at all - admittedly this was only by trying launching the Gnome main menus - Alt + f1 - which although displayed, did not produce any verbal commentary. 3. Update manager did not respond at all after the update was completed 4. Once focus returned back to the main desktop Orca appeared to be working fine again. Obviously I cannot test this again until there are further updates available. The system I have is Ubuntu 6.10 last updated on 22/12/06 prior to today - with almost the same results as described above. I think that it may have been more responsive at that time but that was a little while ago! I am predominately a MS user, and dabble with Ubuntu when I get chance, so I don't know my way around Ubuntu quite as good as I should, but I am learning fast! Any help and / or guidance is appreciated. Ian -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 2496 bytes Desc: not available URL: From William.Walker at Sun.COM Wed Jan 3 14:16:09 2007 From: William.Walker at Sun.COM (Willie Walker) Date: Wed, 03 Jan 2007 09:16:09 -0500 Subject: Accessibility with System Admin Tools In-Reply-To: References: Message-ID: <1167833769.4676.68.camel@ubuntu> > I seem to remember from a posting back during last summer that it was > proposed that work should be done on Ubuntu's Admin tools to increase their > accessibility - has this started or been done? The work to make this happen is on going for GNOME 2.18 and requires modification to several components. In the meantime, one way around this issue is to enable the root account, and to allow the root user to login to gnome. This can be accomplished as follows: 1) Set a password on the root account: sudo passwd root 2) Next, edit /etc/gdm/gdm.conf-custom and add the following line under the [security] section: AllowRoot=true Reboot your system. Now, log in as root via a text console, and run orca --setup. You're all done. When you want to administer your system using GUI administration tools, you can now login to gnome as root and run orca. For GNOME 2.18, I hope the situation will be much better. Hope this helps, Will From William.Walker at Sun.COM Wed Jan 3 14:52:22 2007 From: William.Walker at Sun.COM (Willie Walker) Date: Wed, 03 Jan 2007 09:52:22 -0500 Subject: has speakup been added In-Reply-To: <20061220221450.GA10111@mail.hittsjunk.net> References: <0JAK00JUQU3T71A7@vms046.mailsrvcs.net> <20061220221450.GA10111@mail.hittsjunk.net> Message-ID: <1167835942.4676.101.camel@ubuntu> Hi Kenny: > The version in Feisty isn't the latest, but it works fine. I'm using it > now since gnome-terminal will crash if I use Orca's review keys. I haven't seen this on GNOME 2.16 or Ubuntu Egdy. Is the crash you are seeing only with Feisty, or have you seen it elsewhere? Will From churst35 at verizon.net Thu Jan 4 00:09:28 2007 From: churst35 at verizon.net (Cody Hurst) Date: Wed, 03 Jan 2007 19:09:28 -0500 Subject: Orca Accessibility with System Admin Tools In-Reply-To: <1167833769.4676.68.camel@ubuntu> References: <1167833769.4676.68.camel@ubuntu> Message-ID: <1167869369.23692.27.camel@ubuntu3> Hello, Actually there is an even easier way I have found. I stole it from the idea of installing ubuntu. Rather than enabling the root account, open a shell, switch to root (sudo su), killall orca, and then launch orca. This will start orca as root. you won't have speech just yet, so press ctrl+shift+t and type sudo su again so you become root. if you know the command or program name of a program that needs to run as root type it and press enter and orca will begin speaking the application. for example: terminal tab one sudo su password: ******* orca then orca launches terminal tab two sudo su password: ********* gdmsetup then gdm starts this is only example you could have launched something else. when you want to go back to user just press the ctrl+pgup keys in the terminal (additional fn for laptops) and press control c and that will kill orca rerun orca by pressing alt+f2 and typing orca and you're back to where you started... Cody On Wed, 2007-01-03 at 09:16 -0500, Willie Walker wrote: > > I seem to remember from a posting back during last summer that it was > > proposed that work should be done on Ubuntu's Admin tools to increase their > > accessibility - has this started or been done? > > The work to make this happen is on going for GNOME 2.18 and requires > modification to several components. In the meantime, one way around > this issue is to enable the root account, and to allow the root user to > login to gnome. This can be accomplished as follows: > > 1) Set a password on the root account: > > sudo passwd root > > 2) Next, edit /etc/gdm/gdm.conf-custom and add the following line > under the [security] section: > > AllowRoot=true > > Reboot your system. Now, log in as root via a text console, and run orca > --setup. You're all done. When you want to administer your system > using GUI administration tools, you can now login to gnome as root and > run orca. > > For GNOME 2.18, I hope the situation will be much better. > > Hope this helps, > > Will > > > _______________________________________________ > Orca-list mailing list > Orca-list at gnome.org > http://mail.gnome.org/mailman/listinfo/orca-list From themuso at themuso.com Thu Jan 4 00:30:50 2007 From: themuso at themuso.com (Luke Yelavich) Date: Thu, 4 Jan 2007 11:30:50 +1100 Subject: has speakup been added In-Reply-To: <20061220221450.GA10111@mail.hittsjunk.net> References: <0JAK00JUQU3T71A7@vms046.mailsrvcs.net> <20061220221450.GA10111@mail.hittsjunk.net> Message-ID: <20070104003049.GA11455@linden.yelavich.home> On Thu, Dec 21, 2006 at 09:14:50AM EST, Kenny Hitt wrote: > Hi. > > Speakup is already in the Ubuntu kernel. I don't know when it was > added, but it was in the kernel when I first installed Edgy back in > September. > > The version in Feisty isn't the latest, but it works fine. I'm using it > now since gnome-terminal will crash if I use Orca's review keys. As of a day or so ago, there is newer speakup code in the Ubuntu kernel. This code is from cvs as of a week or so ago. -- Luke Yelavich GPG key: 0xD06320CE (http://www.themuso.com/themuso-gpg-key.txt) Email & MSN: themuso at themuso.com Jabber: themuso at jabber.org.au -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From alpuzz at gmail.com Thu Jan 4 20:26:07 2007 From: alpuzz at gmail.com (Al Puzzuoli) Date: Thu, 4 Jan 2007 15:26:07 -0500 Subject: Installation, sudo accessibility, etc? Message-ID: <03f901c7303e$91cff8a0$6901a8c0@thinkpad> Hi folks, Just wondering where things stand in terms of Feisty and access to admin tools, in particular, the installer? I am aware that some work has been done at the desktop level to make this a possibility, see: http://bugzilla.gnome.org/show_bug.cgi?id=163132 However as things stand right now, this fix in and of itself is not a complete solution. The problem is that in order for this functionality to be enabled, an orbitrc file containing certain values needs to be created in the home directory of the root user. Granted, there are ways of getting around this issue, as described in the Ubuntu installation wiki;but in order to appeal to as large a user base as possible, the installer really needs to be accessible simply by running it from its desktop icon. I know that the Ubuntu team, along with the Gnome community has been working hard to make this sort of access a reality, and we're almost there! Has thought been given as to how it will be handled in Feisty? Perhaps the necessary orbitrc file could be added to the root user account by default on the live cd, or failing that, an option, accessible via the normal user account's preferences gui could turn it on as needed? Thanks, --Al -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kwatson at smed.yi.org Fri Jan 5 16:06:21 2007 From: Kwatson at smed.yi.org (Keith Watson) Date: Fri, 5 Jan 2007 11:06:21 -0500 Subject: Feisty and Speakup dectalk driver Message-ID: <20070105160621.GA21493@smed.yi.org> Folks, I just joined the bleeding edge and upgraded to feisty. Guess what, I am already bleeding. When attempting to load the speakup_dectlk module I get the following error: FATAL: Error inserting speakup_dectlk (/lib/modules/2.6.20-3-386/kernel/ubuntu/misc/speakup/speakup_dectlk.ko): No such device I rebooted the system and echo'd something to ttyS0 and it echo'd fine. I attempted to reload the module and got the same error. I then tried to echo something to ttyS0 and got an i/o error. Rebooted and could echo once again. I loaded my ltlk module and all was well. Any suggestions? Keith -- Among the major impediments to discovery are not the ignorant but those with illusions of knowledge. - B. Alan Wallace From josh at techlab.cviatlanta.org Sat Jan 6 07:17:28 2007 From: josh at techlab.cviatlanta.org (Joshua Lambert) Date: Sat, 6 Jan 2007 02:17:28 -0500 (EST) Subject: using espeak instead of festival Message-ID: Would it be possible to switch from festival to the espeak software synth on the live cd? Festival and gnome-speech are two performance killers, and festival is huge. Meanwhile, espeak is small, fast, and very understandable. There is a speech-dispatcher backend for orca to allow orca to recognize speech-dispatcher. Seriously, when I use the ubuntu cd with my 2ghz processor, there is a noticeable delay between the time I press the arrow keys in a menu and the speech output. On the other hand, using the orca/speech-dispatcher/espeak combination on my hd installation, speech is fast and responsive. Btw, festival also yields slow responsiveness on the hd. Cheers, Josh From henrik at ubuntu.com Sat Jan 6 11:35:38 2007 From: henrik at ubuntu.com (Henrik Nilsen Omma) Date: Sat, 06 Jan 2007 12:35:38 +0100 Subject: using espeak instead of festival In-Reply-To: References: Message-ID: <459F898A.2020700@ubuntu.com> Hi Joshua, We are looking at doing this, though it depends on writing a gnome-speech driver for espeak (the speech dispatcher solution is still too incomplete). See: https://wiki.ubuntu.com/Accessibility/Specs/MultilingualSpeechSynthesis Henrik Joshua Lambert wrote: > Would it be possible to switch from festival to the espeak software synth > on the live cd? Festival and gnome-speech are two performance killers, > and festival is huge. Meanwhile, espeak is small, fast, and very > understandable. There is a speech-dispatcher backend for orca to allow > orca to recognize speech-dispatcher. Seriously, when I use the ubuntu cd > with my 2ghz processor, there is a noticeable delay between the time I > press the arrow keys in a menu and the speech output. On the other hand, > using the orca/speech-dispatcher/espeak combination on my hd installation, > speech is fast and responsive. Btw, festival also yields slow > responsiveness on the hd. > Cheers, > Josh > > > From William.Walker at Sun.COM Mon Jan 8 13:53:02 2007 From: William.Walker at Sun.COM (Willie Walker) Date: Mon, 08 Jan 2007 08:53:02 -0500 Subject: [Fwd: Announcing Orca v2.17.5] Message-ID: <1168264382.4726.17.camel@ubuntu> FYI... -------------- next part -------------- An embedded message was scrubbed... From: Willie Walker Subject: Announcing Orca v2.17.5 Date: Sun, 07 Jan 2007 15:16:22 -0500 Size: 10654 URL: From kenny at hittsjunk.net Mon Jan 8 15:26:46 2007 From: kenny at hittsjunk.net (Kenny Hitt) Date: Mon, 8 Jan 2007 09:26:46 -0600 Subject: gnome-terminal crash in Feisty Message-ID: <20070108152646.GA25560@mail.hittsjunk.net> Hi. I am having a strange problem using gnome-terminal in Feisty. Gnome-terminal crashes with no error dialog. Then it crashes, all terminal sessions close. The crash is random, but it seems to happen when I use a Orca review key. Gnome-terminal is at version 2.16.1-0ubuntu1 Libvte9 is at version 1:0.15.0-0ubuntu1 The only other information I can provide is my .xsession-errors file. If there's anything I can do to provide more information, please let me know and I'll do it. Thanks in advance. Kenny -------------- next part -------------- /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "kenny" /etc/gdm/Xsession: Beginning session setup... Xlib: extension "XEVIE" missing on display ":0.0". Bonobo accessibility support initialized GTK Accessibility Module initialized SESSION_MANAGER=local/spot:/tmp/.ICE-unix/4838 GTK Accessibility Module initialized ** (gnome-session:4838): WARNING **: Host name lookup failure on localhost. GTK Accessibility Module initialized GTK Accessibility Module initialized Bonobo accessibility support initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized Initializing gnome-mount extension GTK Accessibility Module initialized Bonobo accessibility support initialized ** (gnome-cups-icon:4964): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:4964): WARNING **: IPP request failed with status 1280 GTK Accessibility Module initialized Bonobo accessibility support initialized evolution-alarm-notify-Message: Setting timeout for 52787 1168300800 1168248013 evolution-alarm-notify-Message: Mon Jan 8 18:00:00 2007 evolution-alarm-notify-Message: Mon Jan 8 03:20:13 2007 GTK Accessibility Module initialized ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 (gnome-panel:4932): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24 anykey anykey anykey anykey anykey anykey ** (gnome-cups-icon:4964): WARNING **: Could not start the printer tray icon, because the CUPS server could not be contacted. anykey anykey anykey anykey GTK Accessibility Module initialized Bonobo accessibility support initialized anykey anykey anykey anykey anykey Window manager warning: Log level 8: atk_relation_set_get_n_relations: assertion `ATK_IS_RELATION_SET (set)' failed anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey (gnome-terminal:5383): Vte-WARNING **: No handler for control sequence `device-control-string' defined. anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey GLib-ERROR **: gmem.c:135: failed to allocate 4294962046 bytes aborting... Traceback (most recent call last): File "/var/lib/python-support/python2.4/orca/input_event.py", line 178, in processInputEvent consumed = self._function(script, inputEvent) File "/var/lib/python-support/python2.4/orca/default.py", line 2912, in reviewCurrentLine self._reviewCurrentLine(inputEvent, clickCount) File "/var/lib/python-support/python2.4/orca/default.py", line 2925, in _reviewCurrentLine context = self.getFlatReviewContext() File "/var/lib/python-support/python2.4/orca/default.py", line 2685, in getFlatReviewContext self.flatReviewContext = self.flatReviewContextClass(self) File "/var/lib/python-support/python2.4/orca/flat_review.py", line 393, in __init__ self.lines = self.clusterZonesByLine(self.getShowingZones(obj)) File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones zones.extend(self.getShowingZones(child)) File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones zones.extend(self.getShowingZones(child)) File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones zones.extend(self.getShowingZones(child)) File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones zones.extend(self.getShowingZones(child)) File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones zones.extend(self.getShowingZones(child)) File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones zones.extend(self.getShowingZones(child)) File "/var/lib/python-support/python2.4/orca/flat_review.py", line 946, in getShowingZones return self.getZonesFromAccessible(root, root.extents) File "/var/lib/python-support/python2.4/orca/flat_review.py", line 762, in getZonesFromAccessible zones = self.getZonesFromText(accessible, cliprect) File "/var/lib/python-support/python2.4/orca/flat_review.py", line 644, in getZonesFromText atspi.Accessibility.TEXT_BOUNDARY_LINE_START) COMM_FAILURE anykey anykey From Padraig.Obriain at Sun.COM Mon Jan 8 15:48:37 2007 From: Padraig.Obriain at Sun.COM (Padraig O'Briain) Date: Mon, 08 Jan 2007 15:48:37 +0000 Subject: gnome-terminal crash in Feisty In-Reply-To: <20070108152646.GA25560@mail.hittsjunk.net> References: <20070108152646.GA25560@mail.hittsjunk.net> Message-ID: <45A267D5.1040401@sun.com> I think that a stack trace for gnome-terminal process will be necessary. Padraig Kenny Hitt wrote: > Hi. > > I am having a strange problem using gnome-terminal in Feisty. > Gnome-terminal crashes with no error dialog. Then it crashes, all > terminal sessions close. The crash is random, but it seems to happen > when I use a Orca review key. > > Gnome-terminal is at version 2.16.1-0ubuntu1 > Libvte9 is at version 1:0.15.0-0ubuntu1 > > The only other information I can provide is my .xsession-errors file. > If there's anything I can do to provide more information, please let me > know and I'll do it. > > Thanks in advance. > Kenny > > > ------------------------------------------------------------------------ > > /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp > /etc/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "kenny" > /etc/gdm/Xsession: Beginning session setup... > Xlib: extension "XEVIE" missing on display ":0.0". > Bonobo accessibility support initialized > GTK Accessibility Module initialized > SESSION_MANAGER=local/spot:/tmp/.ICE-unix/4838 > GTK Accessibility Module initialized > > ** (gnome-session:4838): WARNING **: Host name lookup failure on localhost. > GTK Accessibility Module initialized > GTK Accessibility Module initialized > Bonobo accessibility support initialized > Bonobo accessibility support initialized > GTK Accessibility Module initialized > Bonobo accessibility support initialized > GTK Accessibility Module initialized > GTK Accessibility Module initialized > Bonobo accessibility support initialized > GTK Accessibility Module initialized > Bonobo accessibility support initialized > Initializing gnome-mount extension > GTK Accessibility Module initialized > Bonobo accessibility support initialized > > ** (gnome-cups-icon:4964): WARNING **: IPP request failed with status 1280 > > ** (gnome-cups-icon:4964): WARNING **: IPP request failed with status 1280 > GTK Accessibility Module initialized > Bonobo accessibility support initialized > evolution-alarm-notify-Message: Setting timeout for 52787 1168300800 1168248013 > evolution-alarm-notify-Message: Mon Jan 8 18:00:00 2007 > > evolution-alarm-notify-Message: Mon Jan 8 03:20:13 2007 > > GTK Accessibility Module initialized > ** Message: drive = 0 > ** Message: volume = 0 > ** Message: drive = 0 > ** Message: volume = 0 > ** Message: drive = 0 > ** Message: volume = 0 > ** Message: drive = 0 > ** Message: volume = 0 > ** Message: drive = 0 > ** Message: volume = 0 > ** Message: drive = 0 > ** Message: volume = 0 > > (gnome-panel:4932): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24 > anykey > anykey > anykey > anykey > anykey > anykey > > ** (gnome-cups-icon:4964): WARNING **: Could not start the printer tray icon, because the CUPS server could not be contacted. > anykey > anykey > anykey > anykey > GTK Accessibility Module initialized > Bonobo accessibility support initialized > anykey > anykey > anykey > anykey > anykey > Window manager warning: Log level 8: atk_relation_set_get_n_relations: assertion `ATK_IS_RELATION_SET (set)' failed > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > > (gnome-terminal:5383): Vte-WARNING **: No handler for control sequence `device-control-string' defined. > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > > GLib-ERROR **: gmem.c:135: failed to allocate 4294962046 bytes > aborting... > Traceback (most recent call last): > File "/var/lib/python-support/python2.4/orca/input_event.py", line 178, in processInputEvent > consumed = self._function(script, inputEvent) > File "/var/lib/python-support/python2.4/orca/default.py", line 2912, in reviewCurrentLine > self._reviewCurrentLine(inputEvent, clickCount) > File "/var/lib/python-support/python2.4/orca/default.py", line 2925, in _reviewCurrentLine > context = self.getFlatReviewContext() > File "/var/lib/python-support/python2.4/orca/default.py", line 2685, in getFlatReviewContext > self.flatReviewContext = self.flatReviewContextClass(self) > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 393, in __init__ > self.lines = self.clusterZonesByLine(self.getShowingZones(obj)) > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones > zones.extend(self.getShowingZones(child)) > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones > zones.extend(self.getShowingZones(child)) > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones > zones.extend(self.getShowingZones(child)) > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones > zones.extend(self.getShowingZones(child)) > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones > zones.extend(self.getShowingZones(child)) > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones > zones.extend(self.getShowingZones(child)) > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 946, in getShowingZones > return self.getZonesFromAccessible(root, root.extents) > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 762, in getZonesFromAccessible > zones = self.getZonesFromText(accessible, cliprect) > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 644, in getZonesFromText > atspi.Accessibility.TEXT_BOUNDARY_LINE_START) > COMM_FAILURE > anykey > anykey > > ------------------------------------------------------------------------ > > _______________________________________________ > gnome-accessibility-list mailing list > gnome-accessibility-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list > From bethko at gmail.com Mon Jan 8 16:12:21 2007 From: bethko at gmail.com (Beth Koenig) Date: Mon, 8 Jan 2007 08:12:21 -0800 Subject: espeak and orca In-Reply-To: <0JAB009Z2QH56E03@vms048.mailsrvcs.net> References: <0JAB009Z2QH56E03@vms048.mailsrvcs.net> Message-ID: <8ac229cc0701080812q16072434r5245a9d7efbb3311@mail.gmail.com> I need this info ASAP also. Festival is driving me up a wall and is WAY too slow. So instructions on how to get espeak on Orca would be great. Also does anyone know where to find a binary of brlapi 4.1? I am having problems getting my Braille Lite 2000 to work and I know it's not brltty as I have been using it for years. It's not the braille Lite either. Thanks, Beth Koenig bethko at gmail.com On 12/15/06, mike coulombe wrote: > Hi, has anyone gotten espeek to work with orca. > If so how do I go about doing this. > Mike. > X-Antivirus: avast! (VPS 0659-0, 12/15/2006), Outbound message > X-Antivirus-Status: Clean > > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > -- Beth Koenig bethko at gmail.com Director of Deaf Blind Services Orange County Deaf Advocacy Center http://www.deafadvocacy.org/dbs Health, safety, and productivity are the cornerstones of independence. At the Orange County Deaf Advocacy Center we provide the training and services necessary for the deaf and disabled to achieve equally and independence in all areas of life. Orange County Deaf Advocacy Center Donate: https://www.networkforgood.org/donate/MakeDonation2.aspx?ORGID2=330806007&PcaItemId=400 From henrik at ubuntu.com Mon Jan 8 16:56:04 2007 From: henrik at ubuntu.com (Henrik Nilsen Omma) Date: Mon, 08 Jan 2007 17:56:04 +0100 Subject: espeak and orca In-Reply-To: <8ac229cc0701080812q16072434r5245a9d7efbb3311@mail.gmail.com> References: <0JAB009Z2QH56E03@vms048.mailsrvcs.net> <8ac229cc0701080812q16072434r5245a9d7efbb3311@mail.gmail.com> Message-ID: <45A277A4.4010207@ubuntu.com> Beth Koenig wrote: > I need this info ASAP also. Festival is driving me up a wall and is > WAY too slow. So instructions on how to get espeak on Orca would be > great. Also does anyone know where to find a binary of brlapi 4.1? I > am having problems getting my Braille Lite 2000 to work and I know > it's not brltty as I have been using it for years. It's not the > braille Lite either. > > You currently need speech-dispatcher to use eSpeak with Orca, and there are some instructions here: http://live.gnome.org/Orca/SpeechDispatcher Gilles is working on a gnome-speech driver for eSpeak though which will be a more robust solution (until SD and Orca support matures anyway). We are currently evaluating whay technical solutions to use for the future so we are *very* interested in feedback about peoples user experiences. * What is the exact problem with Festival, the speed of speech of lack of responsiveness? * For those who have eSpeak working (which option did you use the experimental Orca support or the gnome-speech->SD bridge?) -- how is it working? Any issues? * When we have the gnome-speech eSpeak driver working how does that compare with the other setups? etc. Henrik From kenny at hittsjunk.net Mon Jan 8 19:04:03 2007 From: kenny at hittsjunk.net (Kenny Hitt) Date: Mon, 8 Jan 2007 13:04:03 -0600 Subject: espeak and orca In-Reply-To: <45A277A4.4010207@ubuntu.com> References: <0JAB009Z2QH56E03@vms048.mailsrvcs.net> <8ac229cc0701080812q16072434r5245a9d7efbb3311@mail.gmail.com> <45A277A4.4010207@ubuntu.com> Message-ID: <20070108190403.GB25934@mail.hittsjunk.net> Hi. The problem I have with festival is it's slow responsiveness. Normally, I use espeak with the speech-dispatcher gnome-speech driver. This driver doesn't support the read to end command, so I either switch to festival when I want to read an entire document, or use the direct speech-dispatcher backend for Orca. Kenny On Mon, Jan 08, 2007 at 05:56:04PM +0100, Henrik Nilsen Omma wrote: > You currently need speech-dispatcher to use eSpeak with Orca, and there > are some instructions here: http://live.gnome.org/Orca/SpeechDispatcher > > Gilles is working on a gnome-speech driver for eSpeak though which will > be a more robust solution (until SD and Orca support matures anyway). > > We are currently evaluating whay technical solutions to use for the > future so we are *very* interested in feedback about peoples user > experiences. > > * What is the exact problem with Festival, the speed of speech of lack > of responsiveness? > * For those who have eSpeak working (which option did you use the > experimental Orca support or the gnome-speech->SD bridge?) -- how is it > working? Any issues? > * When we have the gnome-speech eSpeak driver working how does that > compare with the other setups? > > etc. > > Henrik > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility From krister at kristersplace.ws Mon Jan 8 21:30:03 2007 From: krister at kristersplace.ws (Krister Ekstrom) Date: Mon, 08 Jan 2007 22:30:03 +0100 Subject: espeak and orca In-Reply-To: <45A277A4.4010207@ubuntu.com> References: <0JAB009Z2QH56E03@vms048.mailsrvcs.net> <8ac229cc0701080812q16072434r5245a9d7efbb3311@mail.gmail.com> <45A277A4.4010207@ubuntu.com> Message-ID: <1168291803.18447.6.camel@krister-desktop> On Mon, 2007-01-08 at 17:56 +0100, Henrik Nilsen Omma wrote: > * For those who have eSpeak working (which option did you use the > experimental Orca support or the gnome-speech->SD bridge?) -- how is > it > working? Any issues? > Well it's working quite ok, i'd say. The only issues i have as of now is that i can't seem to use document reading (numeric plus) because Orca is only reading one line and then stops, but i think it has to do with the lack of indexing somewhere. I think it's a known issue. Other than that, i haven't had any noticable problems. I'm running the Speech dispatcher solution. -- /Krister From krister at kristersplace.ws Mon Jan 8 21:40:50 2007 From: krister at kristersplace.ws (Krister Ekstrom) Date: Mon, 08 Jan 2007 22:40:50 +0100 Subject: espeak and orca In-Reply-To: <20070108190403.GB25934@mail.hittsjunk.net> References: <0JAB009Z2QH56E03@vms048.mailsrvcs.net> <8ac229cc0701080812q16072434r5245a9d7efbb3311@mail.gmail.com> <45A277A4.4010207@ubuntu.com> <20070108190403.GB25934@mail.hittsjunk.net> Message-ID: <1168292450.18447.12.camel@krister-desktop> On Mon, 2007-01-08 at 13:04 -0600, Kenny Hitt wrote: > Normally, I use espeak with the speech-dispatcher gnome-speech driver. > This driver doesn't support the read to end command, so I either > switch > to festival when I want to read an entire document, or use the direct > speech-dispatcher backend for Orca. > Can you actually use both drivers at the same time? I thought it was > one or the other and installing them both would mean conflict. How > does one choose between them? I guess they get visible in the orca > prefs in some way, right? -- /Krister From kenny at hittsjunk.net Mon Jan 8 21:45:54 2007 From: kenny at hittsjunk.net (Kenny Hitt) Date: Mon, 8 Jan 2007 15:45:54 -0600 Subject: espeak and orca In-Reply-To: <1168292450.18447.12.camel@krister-desktop> References: <0JAB009Z2QH56E03@vms048.mailsrvcs.net> <8ac229cc0701080812q16072434r5245a9d7efbb3311@mail.gmail.com> <45A277A4.4010207@ubuntu.com> <20070108190403.GB25934@mail.hittsjunk.net> <1168292450.18447.12.camel@krister-desktop> Message-ID: <20070108214554.GC25934@mail.hittsjunk.net> Hi. Yes, they are both available in the Orca preferences. Both aren't being used at the same time, but you can switch any time you want. Kenny On Mon, Jan 08, 2007 at 10:40:50PM +0100, Krister Ekstrom wrote: > On Mon, 2007-01-08 at 13:04 -0600, Kenny Hitt wrote: > > Normally, I use espeak with the speech-dispatcher gnome-speech driver. > > This driver doesn't support the read to end command, so I either > > switch > > to festival when I want to read an entire document, or use the direct > > speech-dispatcher backend for Orca. > > Can you actually use both drivers at the same time? I thought it was > > one or the other and installing them both would mean conflict. How > > does one choose between them? I guess they get visible in the orca > > prefs in some way, right? > -- > /Krister > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility From kenny at hittsjunk.net Mon Jan 8 22:09:01 2007 From: kenny at hittsjunk.net (Kenny Hitt) Date: Mon, 8 Jan 2007 16:09:01 -0600 Subject: gnome-terminal crash in Feisty In-Reply-To: <45A267D5.1040401@sun.com> References: <20070108152646.GA25560@mail.hittsjunk.net> <45A267D5.1040401@sun.com> Message-ID: <20070108220901.GA26328@mail.hittsjunk.net> Hi. Thanks to help from Luke, I was able to get the following from gdb. Program received signal SIGABRT, Aborted. [Switching to Thread -1226291520 (LWP 15468)] 0xb7fba410 in ?? () (gdb) bt #0 0xb7fba410 in ?? () #1 0xbfa25e6c in ?? () #2 0x00000006 in ?? () #3 0x00003c6c in ?? () #4 0xb759cdf0 in raise () from /lib/tls/i686/cmov/libc.so.6 #5 0xb759e641 in abort () from /lib/tls/i686/cmov/libc.so.6 #6 0xb76eb4b2 in g_logv () from /usr/lib/libglib-2.0.so.0 #7 0xb76eb4e9 in g_log () from /usr/lib/libglib-2.0.so.0 #8 0xb76ea0b9 in g_malloc () from /usr/lib/libglib-2.0.so.0 #9 0xb7dedbe7 in ?? () from /usr/lib/libvte.so.9 #10 0xffffffd2 in ?? () #11 0xb7e70ae8 in ?? () from /usr/lib/libvte.so.9 #12 0x00000000 in ?? () I noticed gdb didn't find debug symbols for some of the libs linked to gnome-terminal. Is this enough info, or do I need to do more? Kenny On Mon, Jan 08, 2007 at 03:48:37PM +0000, Padraig O'Briain wrote: > I think that a stack trace for gnome-terminal process will be necessary. > > Padraig > > Kenny Hitt wrote: > > Hi. > > > > I am having a strange problem using gnome-terminal in Feisty. > > Gnome-terminal crashes with no error dialog. Then it crashes, all > > terminal sessions close. The crash is random, but it seems to happen > > when I use a Orca review key. > > > > Gnome-terminal is at version 2.16.1-0ubuntu1 > > Libvte9 is at version 1:0.15.0-0ubuntu1 > > > > The only other information I can provide is my .xsession-errors file. > > If there's anything I can do to provide more information, please let me > > know and I'll do it. > > > > Thanks in advance. > > Kenny > > > > > > ------------------------------------------------------------------------ > > > > /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp > > /etc/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "kenny" > > /etc/gdm/Xsession: Beginning session setup... > > Xlib: extension "XEVIE" missing on display ":0.0". > > Bonobo accessibility support initialized > > GTK Accessibility Module initialized > > SESSION_MANAGER=local/spot:/tmp/.ICE-unix/4838 > > GTK Accessibility Module initialized > > > > ** (gnome-session:4838): WARNING **: Host name lookup failure on localhost. > > GTK Accessibility Module initialized > > GTK Accessibility Module initialized > > Bonobo accessibility support initialized > > Bonobo accessibility support initialized > > GTK Accessibility Module initialized > > Bonobo accessibility support initialized > > GTK Accessibility Module initialized > > GTK Accessibility Module initialized > > Bonobo accessibility support initialized > > GTK Accessibility Module initialized > > Bonobo accessibility support initialized > > Initializing gnome-mount extension > > GTK Accessibility Module initialized > > Bonobo accessibility support initialized > > > > ** (gnome-cups-icon:4964): WARNING **: IPP request failed with status 1280 > > > > ** (gnome-cups-icon:4964): WARNING **: IPP request failed with status 1280 > > GTK Accessibility Module initialized > > Bonobo accessibility support initialized > > evolution-alarm-notify-Message: Setting timeout for 52787 1168300800 1168248013 > > evolution-alarm-notify-Message: Mon Jan 8 18:00:00 2007 > > > > evolution-alarm-notify-Message: Mon Jan 8 03:20:13 2007 > > > > GTK Accessibility Module initialized > > ** Message: drive = 0 > > ** Message: volume = 0 > > ** Message: drive = 0 > > ** Message: volume = 0 > > ** Message: drive = 0 > > ** Message: volume = 0 > > ** Message: drive = 0 > > ** Message: volume = 0 > > ** Message: drive = 0 > > ** Message: volume = 0 > > ** Message: drive = 0 > > ** Message: volume = 0 > > > > (gnome-panel:4932): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24 > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > > > ** (gnome-cups-icon:4964): WARNING **: Could not start the printer tray icon, because the CUPS server could not be contacted. > > anykey > > anykey > > anykey > > anykey > > GTK Accessibility Module initialized > > Bonobo accessibility support initialized > > anykey > > anykey > > anykey > > anykey > > anykey > > Window manager warning: Log level 8: atk_relation_set_get_n_relations: assertion `ATK_IS_RELATION_SET (set)' failed > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > > > (gnome-terminal:5383): Vte-WARNING **: No handler for control sequence `device-control-string' defined. > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > > > GLib-ERROR **: gmem.c:135: failed to allocate 4294962046 bytes > > aborting... > > Traceback (most recent call last): > > File "/var/lib/python-support/python2.4/orca/input_event.py", line 178, in processInputEvent > > consumed = self._function(script, inputEvent) > > File "/var/lib/python-support/python2.4/orca/default.py", line 2912, in reviewCurrentLine > > self._reviewCurrentLine(inputEvent, clickCount) > > File "/var/lib/python-support/python2.4/orca/default.py", line 2925, in _reviewCurrentLine > > context = self.getFlatReviewContext() > > File "/var/lib/python-support/python2.4/orca/default.py", line 2685, in getFlatReviewContext > > self.flatReviewContext = self.flatReviewContextClass(self) > > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 393, in __init__ > > self.lines = self.clusterZonesByLine(self.getShowingZones(obj)) > > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones > > zones.extend(self.getShowingZones(child)) > > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones > > zones.extend(self.getShowingZones(child)) > > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones > > zones.extend(self.getShowingZones(child)) > > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones > > zones.extend(self.getShowingZones(child)) > > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones > > zones.extend(self.getShowingZones(child)) > > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones > > zones.extend(self.getShowingZones(child)) > > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 946, in getShowingZones > > return self.getZonesFromAccessible(root, root.extents) > > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 762, in getZonesFromAccessible > > zones = self.getZonesFromText(accessible, cliprect) > > File "/var/lib/python-support/python2.4/orca/flat_review.py", line 644, in getZonesFromText > > atspi.Accessibility.TEXT_BOUNDARY_LINE_START) > > COMM_FAILURE > > anykey > > anykey > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > gnome-accessibility-list mailing list > > gnome-accessibility-list at gnome.org > > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list > > > > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility From Padraig.Obriain at Sun.COM Tue Jan 9 07:48:07 2007 From: Padraig.Obriain at Sun.COM (Padraig O'Briain) Date: Tue, 09 Jan 2007 07:48:07 +0000 Subject: gnome-terminal crash in Feisty In-Reply-To: <20070108220901.GA26328@mail.hittsjunk.net> References: <20070108152646.GA25560@mail.hittsjunk.net> <45A267D5.1040401@sun.com> <20070108220901.GA26328@mail.hittsjunk.net> Message-ID: <45A348B7.2000001@sun.com> We need to know what the calls in libvte are. Padraig Kenny Hitt wrote: > Hi. > > Thanks to help from Luke, I was able to get the following from gdb. > > Program received signal SIGABRT, Aborted. > [Switching to Thread -1226291520 (LWP 15468)] > 0xb7fba410 in ?? () > (gdb) bt > #0 0xb7fba410 in ?? () > #1 0xbfa25e6c in ?? () > #2 0x00000006 in ?? () > #3 0x00003c6c in ?? () > #4 0xb759cdf0 in raise () from /lib/tls/i686/cmov/libc.so.6 > #5 0xb759e641 in abort () from /lib/tls/i686/cmov/libc.so.6 > #6 0xb76eb4b2 in g_logv () from /usr/lib/libglib-2.0.so.0 > #7 0xb76eb4e9 in g_log () from /usr/lib/libglib-2.0.so.0 > #8 0xb76ea0b9 in g_malloc () from /usr/lib/libglib-2.0.so.0 > #9 0xb7dedbe7 in ?? () from /usr/lib/libvte.so.9 > #10 0xffffffd2 in ?? () > #11 0xb7e70ae8 in ?? () from /usr/lib/libvte.so.9 > #12 0x00000000 in ?? () > > > I noticed gdb didn't find debug symbols for some of the libs linked to > gnome-terminal. Is this enough info, or do I need to do more? > > Kenny > > On Mon, Jan 08, 2007 at 03:48:37PM +0000, Padraig O'Briain wrote: > >> I think that a stack trace for gnome-terminal process will be necessary. >> >> Padraig >> >> Kenny Hitt wrote: >> >>> Hi. >>> >>> I am having a strange problem using gnome-terminal in Feisty. >>> Gnome-terminal crashes with no error dialog. Then it crashes, all >>> terminal sessions close. The crash is random, but it seems to happen >>> when I use a Orca review key. >>> >>> Gnome-terminal is at version 2.16.1-0ubuntu1 >>> Libvte9 is at version 1:0.15.0-0ubuntu1 >>> >>> The only other information I can provide is my .xsession-errors file. >>> If there's anything I can do to provide more information, please let me >>> know and I'll do it. >>> >>> Thanks in advance. >>> Kenny >>> >>> >>> ------------------------------------------------------------------------ >>> >>> /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp >>> /etc/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "kenny" >>> /etc/gdm/Xsession: Beginning session setup... >>> Xlib: extension "XEVIE" missing on display ":0.0". >>> Bonobo accessibility support initialized >>> GTK Accessibility Module initialized >>> SESSION_MANAGER=local/spot:/tmp/.ICE-unix/4838 >>> GTK Accessibility Module initialized >>> >>> ** (gnome-session:4838): WARNING **: Host name lookup failure on localhost. >>> GTK Accessibility Module initialized >>> GTK Accessibility Module initialized >>> Bonobo accessibility support initialized >>> Bonobo accessibility support initialized >>> GTK Accessibility Module initialized >>> Bonobo accessibility support initialized >>> GTK Accessibility Module initialized >>> GTK Accessibility Module initialized >>> Bonobo accessibility support initialized >>> GTK Accessibility Module initialized >>> Bonobo accessibility support initialized >>> Initializing gnome-mount extension >>> GTK Accessibility Module initialized >>> Bonobo accessibility support initialized >>> >>> ** (gnome-cups-icon:4964): WARNING **: IPP request failed with status 1280 >>> >>> ** (gnome-cups-icon:4964): WARNING **: IPP request failed with status 1280 >>> GTK Accessibility Module initialized >>> Bonobo accessibility support initialized >>> evolution-alarm-notify-Message: Setting timeout for 52787 1168300800 1168248013 >>> evolution-alarm-notify-Message: Mon Jan 8 18:00:00 2007 >>> >>> evolution-alarm-notify-Message: Mon Jan 8 03:20:13 2007 >>> >>> GTK Accessibility Module initialized >>> ** Message: drive = 0 >>> ** Message: volume = 0 >>> ** Message: drive = 0 >>> ** Message: volume = 0 >>> ** Message: drive = 0 >>> ** Message: volume = 0 >>> ** Message: drive = 0 >>> ** Message: volume = 0 >>> ** Message: drive = 0 >>> ** Message: volume = 0 >>> ** Message: drive = 0 >>> ** Message: volume = 0 >>> >>> (gnome-panel:4932): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24 >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> >>> ** (gnome-cups-icon:4964): WARNING **: Could not start the printer tray icon, because the CUPS server could not be contacted. >>> anykey >>> anykey >>> anykey >>> anykey >>> GTK Accessibility Module initialized >>> Bonobo accessibility support initialized >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> Window manager warning: Log level 8: atk_relation_set_get_n_relations: assertion `ATK_IS_RELATION_SET (set)' failed >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> >>> (gnome-terminal:5383): Vte-WARNING **: No handler for control sequence `device-control-string' defined. >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> >>> GLib-ERROR **: gmem.c:135: failed to allocate 4294962046 bytes >>> aborting... >>> Traceback (most recent call last): >>> File "/var/lib/python-support/python2.4/orca/input_event.py", line 178, in processInputEvent >>> consumed = self._function(script, inputEvent) >>> File "/var/lib/python-support/python2.4/orca/default.py", line 2912, in reviewCurrentLine >>> self._reviewCurrentLine(inputEvent, clickCount) >>> File "/var/lib/python-support/python2.4/orca/default.py", line 2925, in _reviewCurrentLine >>> context = self.getFlatReviewContext() >>> File "/var/lib/python-support/python2.4/orca/default.py", line 2685, in getFlatReviewContext >>> self.flatReviewContext = self.flatReviewContextClass(self) >>> File "/var/lib/python-support/python2.4/orca/flat_review.py", line 393, in __init__ >>> self.lines = self.clusterZonesByLine(self.getShowingZones(obj)) >>> File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones >>> zones.extend(self.getShowingZones(child)) >>> File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones >>> zones.extend(self.getShowingZones(child)) >>> File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones >>> zones.extend(self.getShowingZones(child)) >>> File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones >>> zones.extend(self.getShowingZones(child)) >>> File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones >>> zones.extend(self.getShowingZones(child)) >>> File "/var/lib/python-support/python2.4/orca/flat_review.py", line 995, in getShowingZones >>> zones.extend(self.getShowingZones(child)) >>> File "/var/lib/python-support/python2.4/orca/flat_review.py", line 946, in getShowingZones >>> return self.getZonesFromAccessible(root, root.extents) >>> File "/var/lib/python-support/python2.4/orca/flat_review.py", line 762, in getZonesFromAccessible >>> zones = self.getZonesFromText(accessible, cliprect) >>> File "/var/lib/python-support/python2.4/orca/flat_review.py", line 644, in getZonesFromText >>> atspi.Accessibility.TEXT_BOUNDARY_LINE_START) >>> COMM_FAILURE >>> anykey >>> anykey >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> gnome-accessibility-list mailing list >>> gnome-accessibility-list at gnome.org >>> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list >>> >>> >> -- >> Ubuntu-accessibility mailing list >> Ubuntu-accessibility at lists.ubuntu.com >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility >> > _______________________________________________ > gnome-accessibility-list mailing list > gnome-accessibility-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list > From kenny at hittsjunk.net Tue Jan 9 13:31:25 2007 From: kenny at hittsjunk.net (Kenny Hitt) Date: Tue, 9 Jan 2007 07:31:25 -0600 Subject: building libvte9 with debug symbols Message-ID: <20070109133125.GA29065@mail.hittsjunk.net> Hi. I'm having a really bad crash with gnome-terminal. In order to figure out the problem, I need a version of libvte with debugging symbols. Could someone please point me to information on how to modify the Ubuntu package to create a dbg version? I've used apt-get source libvte9 to get the Ubuntu source. I've looked at debian/rules, but I don't see any obvious way to stop the build process from stripping the binary. Thanks in advance. Kenny From henrik at ubuntu.com Tue Jan 9 14:01:21 2007 From: henrik at ubuntu.com (Henrik Nilsen Omma) Date: Tue, 09 Jan 2007 15:01:21 +0100 Subject: building libvte9 with debug symbols In-Reply-To: <20070109133125.GA29065@mail.hittsjunk.net> References: <20070109133125.GA29065@mail.hittsjunk.net> Message-ID: <45A3A031.1020706@ubuntu.com> This wiki page claims that debugging packages are available for all Edgy packages, not sure about Feisty. Martin? https://wiki.ubuntu.com/DebuggingProgramCrash It also shows you how to build them. Henrik Kenny Hitt wrote: > Hi. > > I'm having a really bad crash with gnome-terminal. In order to figure > out the problem, I need a version of libvte with debugging symbols. > > Could someone please point me to information on how to modify the Ubuntu > package to create a dbg version? I've used > > apt-get source libvte9 > > to get the Ubuntu source. I've looked at debian/rules, but I don't see > any obvious way to stop the build process from stripping the binary. > > Thanks in advance. > Kenny > > > From kenny at hittsjunk.net Tue Jan 9 15:02:03 2007 From: kenny at hittsjunk.net (Kenny Hitt) Date: Tue, 9 Jan 2007 09:02:03 -0600 Subject: gnome-terminal crash in Feisty In-Reply-To: <45A348B7.2000001@sun.com> References: <20070108152646.GA25560@mail.hittsjunk.net> <45A267D5.1040401@sun.com> <20070108220901.GA26328@mail.hittsjunk.net> <45A348B7.2000001@sun.com> Message-ID: <20070109150203.GA29274@mail.hittsjunk.net> Hi. On Tue, Jan 09, 2007 at 07:48:07AM +0000, Padraig O'Briain wrote: > We need to know what the calls in libvte are. > > Padraig > Is this better? Let me know what else I need to send, and I'll be happy to get it. Kenny Program received signal SIGABRT, Aborted. [Switching to Thread -1227127104 (LWP 17968)] 0xb7efc410 in ?? () (gdb) bt #0 0xb7efc410 in ?? () #1 0xbf8182cc in ?? () #2 0x00000006 in ?? () #3 0x00004630 in ?? () #4 0xb74d0df0 in raise () from /lib/tls/i686/cmov/libc.so.6 #5 0xb74d2641 in abort () from /lib/tls/i686/cmov/libc.so.6 #6 0xb761f64a in g_logv () from /usr/lib/libglib-2.0.so.0 #7 0xb761f689 in g_log () from /usr/lib/libglib-2.0.so.0 #8 0xb761e249 in g_malloc () from /usr/lib/libglib-2.0.so.0 #9 0xb7d2b1aa in vte_terminal_accessible_get_text (text=0x83d56a0, start_offset=807, end_offset=808) at /home/kenny/src/vte/vte-0.15.0/./src/vteaccess.c:982 #10 0xb7d2b64d in vte_terminal_accessible_get_text_somewhere (text=0x83d56a0, offset=807, boundary_type=ATK_TEXT_BOUNDARY_LINE_START, direction=direction_current, start_offset=0xbf818a24, end_offset=0xbf818a20) at /home/kenny/src/vte/vte-0.15.0/./src/vteaccess.c:1164 #11 0xb7d2b7ad in vte_terminal_accessible_get_text_at_offset (text=0x83d56a0, offset=807, boundary_type=ATK_TEXT_BOUNDARY_LINE_START, start_offset=0xbf818a24, end_offset=0xbf818a20) at /home/kenny/src/vte/vte-0.15.0/./src/vteaccess.c:1212 #12 0xb79146ed in atk_text_get_text_at_offset () from /usr/lib/libatk-1.0.so.0 #13 0xb6bfed41 in ?? () from /usr/lib/libspi.so.0 #14 0x083d56a0 in ?? () #15 0x00000327 in ?? () #16 0x00000005 in ?? () #17 0xbf818a24 in ?? () #18 0xbf818a20 in ?? () #19 0x00000004 in ?? () #20 0xb776d7ab in link_connection_writev () from /usr/lib/libORBit-2.so.0 #21 0xb6bf4acf in _ORBIT_skel_small_Accessibility_Text_getTextAtOffset () from /usr/lib/libspi.so.0 #22 0xb7760797 in ?? () from /usr/lib/libORBit-2.so.0 #23 0x084b4904 in ?? () #24 0xbf818b90 in ?? () #25 0xbf818b70 in ?? () #26 0xbf818c08 in ?? () #27 0xbf818d1c in ?? () #28 0xb6bfecc1 in ?? () from /usr/lib/libspi.so.0 #29 0xbf818aa8 in ?? () #30 0xb7766905 in ORBit_OAObject_invoke () from /usr/lib/libORBit-2.so.0 Backtrace stopped: frame did not save the PC From kb8aey at verizon.net Tue Jan 9 15:21:25 2007 From: kb8aey at verizon.net (mike coulombe) Date: Tue, 09 Jan 2007 09:21:25 -0600 (CST) Subject: package manager need info Message-ID: <0JBL00K4OXBPDH35@vms048.mailsrvcs.net> Hi, I just wondered if any work is being done to make the package manager and the users and groups accessible from the gnome desktop. Users and groups used to be accessible in edgy but it no longer is. Other things like the update manager seem to at least be partly usable from the desktop now. Mike. From Padraig.Obriain at Sun.COM Tue Jan 9 15:30:51 2007 From: Padraig.Obriain at Sun.COM (Padraig O'Briain) Date: Tue, 09 Jan 2007 15:30:51 +0000 Subject: gnome-terminal crash in Feisty In-Reply-To: <20070109150203.GA29274@mail.hittsjunk.net> References: <20070108152646.GA25560@mail.hittsjunk.net> <45A267D5.1040401@sun.com> <20070108220901.GA26328@mail.hittsjunk.net> <45A348B7.2000001@sun.com> <20070109150203.GA29274@mail.hittsjunk.net> Message-ID: <45A3B52B.2040800@sun.com> The number of bytes which g_malloc() is trying to allocate would be useful. If the number if normal then it suggest that you have run out of virtual memory. If it is abnormal it suggest a bug in the code. Padraig Kenny Hitt wrote: > Hi. > > On Tue, Jan 09, 2007 at 07:48:07AM +0000, Padraig O'Briain wrote: > >> We need to know what the calls in libvte are. >> >> Padraig >> >> > > Is this better? Let me know what else I need to send, and I'll be happy > to get it. > > Kenny > > Program received signal SIGABRT, Aborted. > [Switching to Thread -1227127104 (LWP 17968)] > 0xb7efc410 in ?? () > (gdb) bt > #0 0xb7efc410 in ?? () > #1 0xbf8182cc in ?? () > #2 0x00000006 in ?? () > #3 0x00004630 in ?? () > #4 0xb74d0df0 in raise () from /lib/tls/i686/cmov/libc.so.6 > #5 0xb74d2641 in abort () from /lib/tls/i686/cmov/libc.so.6 > #6 0xb761f64a in g_logv () from /usr/lib/libglib-2.0.so.0 > #7 0xb761f689 in g_log () from /usr/lib/libglib-2.0.so.0 > #8 0xb761e249 in g_malloc () from /usr/lib/libglib-2.0.so.0 > #9 0xb7d2b1aa in vte_terminal_accessible_get_text > (text=0x83d56a0, > start_offset=807, end_offset=808) > at > /home/kenny/src/vte/vte-0.15.0/./src/vteaccess.c:982 > #10 0xb7d2b64d in > vte_terminal_accessible_get_text_somewhere > (text=0x83d56a0, > offset=807, > boundary_type=ATK_TEXT_BOUNDARY_LINE_START, > direction=direction_current, > start_offset=0xbf818a24, > end_offset=0xbf818a20) > at > /home/kenny/src/vte/vte-0.15.0/./src/vteaccess.c:1164 > #11 0xb7d2b7ad in > vte_terminal_accessible_get_text_at_offset > (text=0x83d56a0, > offset=807, > boundary_type=ATK_TEXT_BOUNDARY_LINE_START, > start_offset=0xbf818a24, > end_offset=0xbf818a20) > at > /home/kenny/src/vte/vte-0.15.0/./src/vteaccess.c:1212 > #12 0xb79146ed in > atk_text_get_text_at_offset > () from > /usr/lib/libatk-1.0.so.0 > #13 0xb6bfed41 in ?? () > from /usr/lib/libspi.so.0 > #14 0x083d56a0 in ?? () > #15 0x00000327 in ?? () > #16 0x00000005 in ?? () > #17 0xbf818a24 in ?? () > #18 0xbf818a20 in ?? () > #19 0x00000004 in ?? () > #20 0xb776d7ab in > link_connection_writev () > from > /usr/lib/libORBit-2.so.0 > #21 0xb6bf4acf in > _ORBIT_skel_small_Accessibility_Text_getTextAtOffset > () > from > /usr/lib/libspi.so.0 > #22 0xb7760797 in ?? () > from > /usr/lib/libORBit-2.so.0 > #23 0x084b4904 in ?? () > #24 0xbf818b90 in ?? () > #25 0xbf818b70 in ?? () > #26 0xbf818c08 in ?? () > #27 0xbf818d1c in ?? () > #28 0xb6bfecc1 in ?? () > from > /usr/lib/libspi.so.0 > #29 0xbf818aa8 in ?? () > #30 0xb7766905 in > ORBit_OAObject_invoke > () from > /usr/lib/libORBit-2.so.0 > Backtrace stopped: > frame did not save the > PC > _______________________________________________ > gnome-accessibility-list mailing list > gnome-accessibility-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list > From kenny at hittsjunk.net Tue Jan 9 16:20:38 2007 From: kenny at hittsjunk.net (Kenny Hitt) Date: Tue, 9 Jan 2007 10:20:38 -0600 Subject: gnome-terminal crash in Feisty In-Reply-To: <45A3B52B.2040800@sun.com> References: <20070108152646.GA25560@mail.hittsjunk.net> <45A267D5.1040401@sun.com> <20070108220901.GA26328@mail.hittsjunk.net> <45A348B7.2000001@sun.com> <20070109150203.GA29274@mail.hittsjunk.net> <45A3B52B.2040800@sun.com> Message-ID: <20070109162038.GB29402@mail.hittsjunk.net> Hi. On Tue, Jan 09, 2007 at 03:30:51PM +0000, Padraig O'Briain wrote: > The number of bytes which g_malloc() is trying to allocate would be useful. > If the number if normal then it suggest that you have run out of virtual > memory. If it is abnormal it suggest a bug in the code. > > Padraig > The system still has 230 meg of unused swap space according to top. Will I need to install the debug version of glib to get this info, or should I use some gdb command? Thanks for all your help in solving this problem. Kenny From kenny at hittsjunk.net Tue Jan 9 17:34:57 2007 From: kenny at hittsjunk.net (Kenny Hitt) Date: Tue, 9 Jan 2007 11:34:57 -0600 Subject: gnome-terminal crash in Feisty In-Reply-To: <20070109162038.GB29402@mail.hittsjunk.net> References: <20070108152646.GA25560@mail.hittsjunk.net> <45A267D5.1040401@sun.com> <20070108220901.GA26328@mail.hittsjunk.net> <45A348B7.2000001@sun.com> <20070109150203.GA29274@mail.hittsjunk.net> <45A3B52B.2040800@sun.com> <20070109162038.GB29402@mail.hittsjunk.net> Message-ID: <20070109173456.GA29714@mail.hittsjunk.net> Replying to myself since I deleted the other messages in the thread. I used tee to capture the output of the gdb session since the output was causing problems for vim when I used speakup's cut and paste. I installed the dbg versions of glib, atk, and at-spi. Hopefully this log will provide enough info. If more is needed, let me know. Kenny -------------- next part -------------- GNU gdb 6.6-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". Attaching to program: /usr/bin/gnome-terminal, process 4841 Reading symbols from /usr/lib/liblaunchpad-integration.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/liblaunchpad-integration.so.0 Reading symbols from /usr/lib/libglade-2.0.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libglade-2.0.so.0 Reading symbols from /usr/lib/libgnomeui-2.so.0... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libgnomeui-2.so.0 Reading symbols from /usr/lib/libgnome-2.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgnome-2.so.0 Reading symbols from /usr/lib/libbonobo-2.so.0... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libbonobo-2.so.0 Reading symbols from /usr/lib/libbonobo-activation.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libbonobo-activation.so.4 Reading symbols from /usr/lib/libstartup-notification-1.so.0... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libstartup-notification-1.so.0 Reading symbols from /usr/lib/libvte.so.9...done. Loaded symbols for /usr/lib/libvte.so.9 Reading symbols from /usr/lib/libgtk-x11-2.0.so.0...done. Loaded symbols for /usr/lib/libgtk-x11-2.0.so.0 Reading symbols from /usr/lib/libgdk-x11-2.0.so.0...done. Loaded symbols for /usr/lib/libgdk-x11-2.0.so.0 Reading symbols from /usr/lib/libatk-1.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libatk-1.0.so.0.1310.1...done. done. Loaded symbols for /usr/lib/libatk-1.0.so.0 Reading symbols from /usr/lib/libgdk_pixbuf-2.0.so.0...done. Loaded symbols for /usr/lib/libgdk_pixbuf-2.0.so.0 Reading symbols from /usr/lib/libXrender.so.1...done. Loaded symbols for /usr/lib/libXrender.so.1 Reading symbols from /usr/lib/libX11.so.6...done. Loaded symbols for /usr/lib/libX11.so.6 Reading symbols from /usr/lib/libgnomevfs-2.so.0...done. Loaded symbols for /usr/lib/libgnomevfs-2.so.0 Reading symbols from /usr/lib/libgconf-2.so.4...done. Loaded symbols for /usr/lib/libgconf-2.so.4 Reading symbols from /lib/libpopt.so.0...done. Loaded symbols for /lib/libpopt.so.0 Reading symbols from /usr/lib/libORBit-2.so.0...done. Loaded symbols for /usr/lib/libORBit-2.so.0 Reading symbols from /lib/tls/i686/cmov/libpthread.so.0...done. [Thread debugging using libthread_db enabled] [New Thread -1226762560 (LWP 4841)] [New Thread -1251951728 (LWP 4849)] Loaded symbols for /lib/tls/i686/cmov/libpthread.so.0 Reading symbols from /lib/tls/i686/cmov/libm.so.6...done. Loaded symbols for /lib/tls/i686/cmov/libm.so.6 Reading symbols from /usr/lib/libpango-1.0.so.0...done. Loaded symbols for /usr/lib/libpango-1.0.so.0 Reading symbols from /usr/lib/libgobject-2.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libgobject-2.0.so.0.1200.7...done. done. Loaded symbols for /usr/lib/libgobject-2.0.so.0 Reading symbols from /usr/lib/libglib-2.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libglib-2.0.so.0.1200.7...done. done. Loaded symbols for /usr/lib/libglib-2.0.so.0 Reading symbols from /lib/tls/i686/cmov/libc.so.6...done. Loaded symbols for /lib/tls/i686/cmov/libc.so.6 Reading symbols from /usr/lib/libpangocairo-1.0.so.0...done. Loaded symbols for /usr/lib/libpangocairo-1.0.so.0 Reading symbols from /usr/lib/libfontconfig.so.1...done. Loaded symbols for /usr/lib/libfontconfig.so.1 Reading symbols from /usr/lib/libXext.so.6...done. Loaded symbols for /usr/lib/libXext.so.6 Reading symbols from /usr/lib/libXinerama.so.1...done. Loaded symbols for /usr/lib/libXinerama.so.1 Reading symbols from /usr/lib/libXi.so.6...done. Loaded symbols for /usr/lib/libXi.so.6 Reading symbols from /usr/lib/libXrandr.so.2...done. Loaded symbols for /usr/lib/libXrandr.so.2 Reading symbols from /usr/lib/libXcursor.so.1...done. Loaded symbols for /usr/lib/libXcursor.so.1 Reading symbols from /usr/lib/libXfixes.so.3...done. Loaded symbols for /usr/lib/libXfixes.so.3 Reading symbols from /usr/lib/libcairo.so.2...done. Loaded symbols for /usr/lib/libcairo.so.2 Reading symbols from /usr/lib/libgmodule-2.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libgmodule-2.0.so.0.1200.7...done. done. Loaded symbols for /usr/lib/libgmodule-2.0.so.0 Reading symbols from /lib/tls/i686/cmov/libdl.so.2...done. Loaded symbols for /lib/tls/i686/cmov/libdl.so.2 Reading symbols from /usr/lib/libxml2.so.2...done. Loaded symbols for /usr/lib/libxml2.so.2 Reading symbols from /usr/lib/libbonoboui-2.so.0...done. Loaded symbols for /usr/lib/libbonoboui-2.so.0 Reading symbols from /usr/lib/libgnomecanvas-2.so.0...done. Loaded symbols for /usr/lib/libgnomecanvas-2.so.0 Reading symbols from /usr/lib/libart_lgpl_2.so.2...done. Loaded symbols for /usr/lib/libart_lgpl_2.so.2 Reading symbols from /usr/lib/libpangoft2-1.0.so.0...done. Loaded symbols for /usr/lib/libpangoft2-1.0.so.0 Reading symbols from /usr/lib/libgthread-2.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libgthread-2.0.so.0.1200.7...done. done. Loaded symbols for /usr/lib/libgthread-2.0.so.0 Reading symbols from /usr/lib/libgnome-keyring.so.0...done. Loaded symbols for /usr/lib/libgnome-keyring.so.0 Reading symbols from /usr/lib/libjpeg.so.62...done. Loaded symbols for /usr/lib/libjpeg.so.62 Reading symbols from /usr/lib/libSM.so.6...done. Loaded symbols for /usr/lib/libSM.so.6 Reading symbols from /usr/lib/libICE.so.6...done. Loaded symbols for /usr/lib/libICE.so.6 Reading symbols from /usr/lib/libesd.so.0...done. Loaded symbols for /usr/lib/libesd.so.0 Reading symbols from /usr/lib/libaudiofile.so.0...done. Loaded symbols for /usr/lib/libaudiofile.so.0 Reading symbols from /usr/lib/libORBitCosNaming-2.so.0...done. Loaded symbols for /usr/lib/libORBitCosNaming-2.so.0 Reading symbols from /usr/lib/libXft.so.2...done. Loaded symbols for /usr/lib/libXft.so.2 Reading symbols from /usr/lib/libpangoxft-1.0.so.0...done. Loaded symbols for /usr/lib/libpangoxft-1.0.so.0 Reading symbols from /usr/lib/libpangox-1.0.so.0...done. Loaded symbols for /usr/lib/libpangox-1.0.so.0 Reading symbols from /lib/libncurses.so.5...done. Loaded symbols for /lib/libncurses.so.5 Reading symbols from /usr/lib/libXau.so.6...done. Loaded symbols for /usr/lib/libXau.so.6 Reading symbols from /usr/lib/libXdmcp.so.6...done. Loaded symbols for /usr/lib/libXdmcp.so.6 Reading symbols from /usr/lib/libdbus-glib-1.so.2...done. Loaded symbols for /usr/lib/libdbus-glib-1.so.2 Reading symbols from /usr/lib/libdbus-1.so.3...done. Loaded symbols for /usr/lib/libdbus-1.so.3 Reading symbols from /usr/lib/libgnutls.so.13...done. Loaded symbols for /usr/lib/libgnutls.so.13 Reading symbols from /usr/lib/libavahi-glib.so.1...done. Loaded symbols for /usr/lib/libavahi-glib.so.1 Reading symbols from /usr/lib/libavahi-common.so.3...done. Loaded symbols for /usr/lib/libavahi-common.so.3 Reading symbols from /usr/lib/libavahi-client.so.3...done. Loaded symbols for /usr/lib/libavahi-client.so.3 Reading symbols from /lib/tls/i686/cmov/libresolv.so.2...done. Loaded symbols for /lib/tls/i686/cmov/libresolv.so.2 Reading symbols from /lib/libselinux.so.1...done. Loaded symbols for /lib/libselinux.so.1 Reading symbols from /lib/tls/i686/cmov/libutil.so.1...done. Loaded symbols for /lib/tls/i686/cmov/libutil.so.1 Reading symbols from /lib/tls/i686/cmov/librt.so.1...done. Loaded symbols for /lib/tls/i686/cmov/librt.so.1 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /usr/lib/libfreetype.so.6...done. Loaded symbols for /usr/lib/libfreetype.so.6 Reading symbols from /usr/lib/libz.so.1...done. Loaded symbols for /usr/lib/libz.so.1 Reading symbols from /usr/lib/libexpat.so.1...done. Loaded symbols for /usr/lib/libexpat.so.1 Reading symbols from /usr/lib/libpng12.so.0...done. Loaded symbols for /usr/lib/libpng12.so.0 Reading symbols from /usr/lib/libasound.so.2...done. Loaded symbols for /usr/lib/libasound.so.2 Reading symbols from /lib/tls/i686/cmov/libnsl.so.1...done. Loaded symbols for /lib/tls/i686/cmov/libnsl.so.1 Reading symbols from /usr/lib/libtasn1.so.3...done. Loaded symbols for /usr/lib/libtasn1.so.3 Reading symbols from /usr/lib/libgcrypt.so.11...done. Loaded symbols for /usr/lib/libgcrypt.so.11 Reading symbols from /usr/lib/libgpg-error.so.0...done. Loaded symbols for /usr/lib/libgpg-error.so.0 Reading symbols from /lib/libsepol.so.1...done. Loaded symbols for /lib/libsepol.so.1 Reading symbols from /usr/lib/X11/locale/common/xlcUTF8Load.so.2...done. Loaded symbols for /usr/lib/X11/locale/common/xlcUTF8Load.so.2 Reading symbols from /lib/tls/i686/cmov/libnss_compat.so.2...done. Loaded symbols for /lib/tls/i686/cmov/libnss_compat.so.2 Reading symbols from /lib/tls/i686/cmov/libnss_nis.so.2...done. Loaded symbols for /lib/tls/i686/cmov/libnss_nis.so.2 Reading symbols from /lib/tls/i686/cmov/libnss_files.so.2...done. Loaded symbols for /lib/tls/i686/cmov/libnss_files.so.2 Reading symbols from /usr/lib/gtk-2.0/modules/libgail.so...done. Loaded symbols for /usr/lib/gtk-2.0/modules/libgail.so Reading symbols from /usr/lib/libgailutil.so.18...done. Loaded symbols for /usr/lib/libgailutil.so.18 Reading symbols from /usr/lib/gtk-2.0/modules/libatk-bridge.so...done. Loaded symbols for /usr/lib/gtk-2.0/modules/libatk-bridge.so Reading symbols from /usr/lib/libspi.so.0...Reading symbols from /usr/lib/debug/usr/lib/libspi.so.0.10.11...done. done. Loaded symbols for /usr/lib/libspi.so.0 Reading symbols from /usr/lib/libXtst.so.6...done. Loaded symbols for /usr/lib/libXtst.so.6 Reading symbols from /usr/lib/gtk-2.0/modules/libgail-gnome.so...done. Loaded symbols for /usr/lib/gtk-2.0/modules/libgail-gnome.so Reading symbols from /usr/lib/libpanel-applet-2.so.0...done. Loaded symbols for /usr/lib/libpanel-applet-2.so.0 Reading symbols from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so...done. Loaded symbols for /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so Reading symbols from /usr/lib/gtk-2.0/2.10.0/engines/libubuntulooks.so...done. Loaded symbols for /usr/lib/gtk-2.0/2.10.0/engines/libubuntulooks.so Reading symbols from /usr/lib/gconv/ISO8859-1.so...done. Loaded symbols for /usr/lib/gconv/ISO8859-1.so Reading symbols from /usr/lib/pango/1.6.0/modules/pango-basic-fc.so...done. Loaded symbols for /usr/lib/pango/1.6.0/modules/pango-basic-fc.so 0xb7f55410 in ?? () (gdb) continue Continuing. Program received signal SIGABRT, Aborted. [Switching to Thread -1226762560 (LWP 4841)] 0xb7f55410 in ?? () (gdb) bt #0 0xb7f55410 in ?? () #1 0xbf9fff8c in ?? () #2 0x00000006 in ?? () #3 0x000012e9 in ?? () #4 0xb7529df0 in raise () from /lib/tls/i686/cmov/libc.so.6 #5 0xb752b641 in abort () from /lib/tls/i686/cmov/libc.so.6 #6 0xb767864a in IA__g_logv (log_domain=, log_level=G_LOG_LEVEL_ERROR, format=0xb76a2b6c "%s: failed to allocate %lu bytes", args1=0xbfa0056c "\030.j������\005") at gmessages.c:497 #7 0xb7678689 in IA__g_log (log_domain=0xb769bfe6 "GLib", log_level=G_LOG_LEVEL_ERROR, format=0xb76a2b6c "%s: failed to allocate %lu bytes") at gmessages.c:517 #8 0xb7677249 in IA__g_malloc (n_bytes=4294967257) at gmem.c:135 #9 0xb7d841aa in vte_terminal_accessible_get_text (text=0x83d56a0, start_offset=560, end_offset=561) at /home/kenny/src/vte/vte-0.15.0/./src/vteaccess.c:982 #10 0xb7d8464d in vte_terminal_accessible_get_text_somewhere (text=0x83d56a0, offset=560, boundary_type=ATK_TEXT_BOUNDARY_LINE_START, direction=direction_current, start_offset=0xbfa006e4, end_offset=0xbfa006e0) at /home/kenny/src/vte/vte-0.15.0/./src/vteaccess.c:1164 #11 0xb7d847ad in vte_terminal_accessible_get_text_at_offset (text=0x83d56a0, offset=560, boundary_type=ATK_TEXT_BOUNDARY_LINE_START, start_offset=0xbfa006e4, end_offset=0xbfa006e0) at /home/kenny/src/vte/vte-0.15.0/./src/vteaccess.c:1212 #12 0xb796d6ed in atk_text_get_text_at_offset (text=0x83d56a0, offset=560, boundary_type=ATK_TEXT_BOUNDARY_LINE_START, start_offset=0xbfa006e4, end_offset=0xbfa006e0) at atktext.c:386 #13 0xb6c57d41 in impl_getTextAtOffset (servant=0x84b4904, offset=560, type=Accessibility_TEXT_BOUNDARY_LINE_START, startOffset=0xbfa007b0, endOffset=0xbfa00790, ev=0xbfa009dc) at text.c:128 #14 0xb6c4dacf in _ORBIT_skel_small_Accessibility_Text_getTextAtOffset ( _o_servant=0x84b4904, _o_retval=0xbfa00850, _o_args=0xbfa00830, _o_ctx=0xbfa008c8, _o_ev=0xbfa009dc, _impl_getTextAtOffset=0xb6c57cc1 ) at Accessibility-common.c:700 #15 0xb77b9797 in ?? () from /usr/lib/libORBit-2.so.0 #16 0x084b4904 in ?? () #17 0xbfa00850 in ?? () #18 0xbfa00830 in ?? () #19 0xbfa008c8 in ?? () #20 0xbfa009dc in ?? () #21 0xb6c57cc1 in impl_getTextAfterOffset (servant=0x84a6508, offset=-1080031152, type=3214936112, startOffset=0xbfa008c8, endOffset=0xbfa00948, ev=0xbfa009dc) at text.c:110 #22 0xb77bf905 in ORBit_OAObject_invoke () from /usr/lib/libORBit-2.so.0 #23 0xb77aca1c in ORBit_small_invoke_adaptor () from /usr/lib/libORBit-2.so.0 #24 0xb77bd5a6 in ?? () from /usr/lib/libORBit-2.so.0 #25 0x084a6508 in ?? () #26 0x084d9600 in ?? () #27 0xb6c66ae0 in Accessibility_Text__imethods () from /usr/lib/libspi.so.0 #28 0xbfa00948 in ?? () #29 0xbfa009dc in ?? () #30 0xb77dad90 in ?? () from /usr/lib/libORBit-2.so.0 #31 0xbfa00948 in ?? () #32 0xb76d51ec in ?? () from /usr/lib/libglib-2.0.so.0 #33 0x084d9600 in ?? () #34 0xbfa00950 in ?? () #35 0x080d35cc in ?? () #36 0xb777a451 in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0 #37 0xb77bdc52 in ?? () from /usr/lib/libORBit-2.so.0 #38 0x084a6508 in ?? () #39 0x084fe734 in ?? () #40 0x00000000 in ?? () (gdb) quit The program is running. Quit anyway (and detach it)? (y or n) (gdb) continue Continuing. Program terminated with signal SIGABRT, Aborted. The program no longer exists. (gdb) quit From freddymartinez9 at gmail.com Tue Jan 9 19:40:11 2007 From: freddymartinez9 at gmail.com (Freddy Martinez) Date: Tue, 9 Jan 2007 19:40:11 +0000 Subject: package manager need info In-Reply-To: <0JBL00K4OXBPDH35@vms048.mailsrvcs.net> References: <0JBL00K4OXBPDH35@vms048.mailsrvcs.net> Message-ID: What do you mean making it accessible from the desktop? I'm not sure what that means, so I can't really answer that question. Let me know, thanks. On 1/9/07, mike coulombe wrote: > > Hi, I just wondered if any work is being done to make the package manager > and the users and groups accessible from the gnome desktop. > Users and groups used to be accessible in edgy but it no longer is. > Other things like the update manager seem to at least be partly usable > from the desktop now. > Mike. > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > -- Freddy Martinez Kubuntu. GNU / Linux for human beings. www.chi.ubuntu-us.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From Padraig.Obriain at Sun.COM Wed Jan 10 08:10:56 2007 From: Padraig.Obriain at Sun.COM (Padraig O'Briain) Date: Wed, 10 Jan 2007 08:10:56 +0000 Subject: gnome-terminal crash in Feisty In-Reply-To: <20070109173456.GA29714@mail.hittsjunk.net> References: <20070108152646.GA25560@mail.hittsjunk.net> <45A267D5.1040401@sun.com> <20070108220901.GA26328@mail.hittsjunk.net> <45A348B7.2000001@sun.com> <20070109150203.GA29274@mail.hittsjunk.net> <45A3B52B.2040800@sun.com> <20070109162038.GB29402@mail.hittsjunk.net> <20070109173456.GA29714@mail.hittsjunk.net> Message-ID: <45A49F90.40801@sun.com> #8 0xb7677249 in IA__g_malloc (n_bytes=4294967257) at gmem.c:135 This shows that the number of bytes is wrong. I suggest logging a bug againt vte. I would be helpful if we knew what the text was. Kenny Hitt wrote: > Replying to myself since I deleted the other messages in the thread. > > I used tee to capture the output of the gdb session since the output was > causing problems for vim when I used speakup's cut and paste. > > I installed the dbg versions of glib, atk, and at-spi. Hopefully this > log will provide enough info. > > If more is needed, let me know. > > Kenny > > > ------------------------------------------------------------------------ > > GNU gdb 6.6-debian > Copyright (C) 2006 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i486-linux-gnu"... > (no debugging symbols found) > Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". > Attaching to program: /usr/bin/gnome-terminal, process 4841 > Reading symbols from /usr/lib/liblaunchpad-integration.so.0...(no debugging symbols found)...done. > Loaded symbols for /usr/lib/liblaunchpad-integration.so.0 > Reading symbols from /usr/lib/libglade-2.0.so.0...(no debugging symbols found)...done. > Loaded symbols for /usr/lib/libglade-2.0.so.0 > Reading symbols from /usr/lib/libgnomeui-2.so.0... > (no debugging symbols found)...done. > Loaded symbols for /usr/lib/libgnomeui-2.so.0 > Reading symbols from /usr/lib/libgnome-2.so.0...(no debugging symbols found)...done. > Loaded symbols for /usr/lib/libgnome-2.so.0 > Reading symbols from /usr/lib/libbonobo-2.so.0... > (no debugging symbols found)...done. > Loaded symbols for /usr/lib/libbonobo-2.so.0 > Reading symbols from /usr/lib/libbonobo-activation.so.4...(no debugging symbols found)...done. > Loaded symbols for /usr/lib/libbonobo-activation.so.4 > Reading symbols from /usr/lib/libstartup-notification-1.so.0... > (no debugging symbols found)...done. > Loaded symbols for /usr/lib/libstartup-notification-1.so.0 > Reading symbols from /usr/lib/libvte.so.9...done. > Loaded symbols for /usr/lib/libvte.so.9 > Reading symbols from /usr/lib/libgtk-x11-2.0.so.0...done. > Loaded symbols for /usr/lib/libgtk-x11-2.0.so.0 > Reading symbols from /usr/lib/libgdk-x11-2.0.so.0...done. > Loaded symbols for /usr/lib/libgdk-x11-2.0.so.0 > Reading symbols from /usr/lib/libatk-1.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libatk-1.0.so.0.1310.1...done. > done. > Loaded symbols for /usr/lib/libatk-1.0.so.0 > Reading symbols from /usr/lib/libgdk_pixbuf-2.0.so.0...done. > Loaded symbols for /usr/lib/libgdk_pixbuf-2.0.so.0 > Reading symbols from /usr/lib/libXrender.so.1...done. > Loaded symbols for /usr/lib/libXrender.so.1 > Reading symbols from /usr/lib/libX11.so.6...done. > Loaded symbols for /usr/lib/libX11.so.6 > Reading symbols from /usr/lib/libgnomevfs-2.so.0...done. > Loaded symbols for /usr/lib/libgnomevfs-2.so.0 > Reading symbols from /usr/lib/libgconf-2.so.4...done. > Loaded symbols for /usr/lib/libgconf-2.so.4 > Reading symbols from /lib/libpopt.so.0...done. > Loaded symbols for /lib/libpopt.so.0 > Reading symbols from /usr/lib/libORBit-2.so.0...done. > Loaded symbols for /usr/lib/libORBit-2.so.0 > Reading symbols from /lib/tls/i686/cmov/libpthread.so.0...done. > [Thread debugging using libthread_db enabled] > [New Thread -1226762560 (LWP 4841)] > [New Thread -1251951728 (LWP 4849)] > Loaded symbols for /lib/tls/i686/cmov/libpthread.so.0 > Reading symbols from /lib/tls/i686/cmov/libm.so.6...done. > Loaded symbols for /lib/tls/i686/cmov/libm.so.6 > Reading symbols from /usr/lib/libpango-1.0.so.0...done. > Loaded symbols for /usr/lib/libpango-1.0.so.0 > Reading symbols from /usr/lib/libgobject-2.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libgobject-2.0.so.0.1200.7...done. > done. > Loaded symbols for /usr/lib/libgobject-2.0.so.0 > Reading symbols from /usr/lib/libglib-2.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libglib-2.0.so.0.1200.7...done. > done. > Loaded symbols for /usr/lib/libglib-2.0.so.0 > Reading symbols from /lib/tls/i686/cmov/libc.so.6...done. > Loaded symbols for /lib/tls/i686/cmov/libc.so.6 > Reading symbols from /usr/lib/libpangocairo-1.0.so.0...done. > Loaded symbols for /usr/lib/libpangocairo-1.0.so.0 > Reading symbols from /usr/lib/libfontconfig.so.1...done. > Loaded symbols for /usr/lib/libfontconfig.so.1 > Reading symbols from /usr/lib/libXext.so.6...done. > Loaded symbols for /usr/lib/libXext.so.6 > Reading symbols from /usr/lib/libXinerama.so.1...done. > Loaded symbols for /usr/lib/libXinerama.so.1 > Reading symbols from /usr/lib/libXi.so.6...done. > Loaded symbols for /usr/lib/libXi.so.6 > Reading symbols from /usr/lib/libXrandr.so.2...done. > Loaded symbols for /usr/lib/libXrandr.so.2 > Reading symbols from /usr/lib/libXcursor.so.1...done. > Loaded symbols for /usr/lib/libXcursor.so.1 > Reading symbols from /usr/lib/libXfixes.so.3...done. > Loaded symbols for /usr/lib/libXfixes.so.3 > Reading symbols from /usr/lib/libcairo.so.2...done. > Loaded symbols for /usr/lib/libcairo.so.2 > Reading symbols from /usr/lib/libgmodule-2.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libgmodule-2.0.so.0.1200.7...done. > done. > Loaded symbols for /usr/lib/libgmodule-2.0.so.0 > Reading symbols from /lib/tls/i686/cmov/libdl.so.2...done. > Loaded symbols for /lib/tls/i686/cmov/libdl.so.2 > Reading symbols from /usr/lib/libxml2.so.2...done. > Loaded symbols for /usr/lib/libxml2.so.2 > Reading symbols from /usr/lib/libbonoboui-2.so.0...done. > Loaded symbols for /usr/lib/libbonoboui-2.so.0 > Reading symbols from /usr/lib/libgnomecanvas-2.so.0...done. > Loaded symbols for /usr/lib/libgnomecanvas-2.so.0 > Reading symbols from /usr/lib/libart_lgpl_2.so.2...done. > Loaded symbols for /usr/lib/libart_lgpl_2.so.2 > Reading symbols from /usr/lib/libpangoft2-1.0.so.0...done. > Loaded symbols for /usr/lib/libpangoft2-1.0.so.0 > Reading symbols from /usr/lib/libgthread-2.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libgthread-2.0.so.0.1200.7...done. > done. > Loaded symbols for /usr/lib/libgthread-2.0.so.0 > Reading symbols from /usr/lib/libgnome-keyring.so.0...done. > Loaded symbols for /usr/lib/libgnome-keyring.so.0 > Reading symbols from /usr/lib/libjpeg.so.62...done. > Loaded symbols for /usr/lib/libjpeg.so.62 > Reading symbols from /usr/lib/libSM.so.6...done. > Loaded symbols for /usr/lib/libSM.so.6 > Reading symbols from /usr/lib/libICE.so.6...done. > Loaded symbols for /usr/lib/libICE.so.6 > Reading symbols from /usr/lib/libesd.so.0...done. > Loaded symbols for /usr/lib/libesd.so.0 > Reading symbols from /usr/lib/libaudiofile.so.0...done. > Loaded symbols for /usr/lib/libaudiofile.so.0 > Reading symbols from /usr/lib/libORBitCosNaming-2.so.0...done. > Loaded symbols for /usr/lib/libORBitCosNaming-2.so.0 > Reading symbols from /usr/lib/libXft.so.2...done. > Loaded symbols for /usr/lib/libXft.so.2 > Reading symbols from /usr/lib/libpangoxft-1.0.so.0...done. > Loaded symbols for /usr/lib/libpangoxft-1.0.so.0 > Reading symbols from /usr/lib/libpangox-1.0.so.0...done. > Loaded symbols for /usr/lib/libpangox-1.0.so.0 > Reading symbols from /lib/libncurses.so.5...done. > Loaded symbols for /lib/libncurses.so.5 > Reading symbols from /usr/lib/libXau.so.6...done. > Loaded symbols for /usr/lib/libXau.so.6 > Reading symbols from /usr/lib/libXdmcp.so.6...done. > Loaded symbols for /usr/lib/libXdmcp.so.6 > Reading symbols from /usr/lib/libdbus-glib-1.so.2...done. > Loaded symbols for /usr/lib/libdbus-glib-1.so.2 > Reading symbols from /usr/lib/libdbus-1.so.3...done. > Loaded symbols for /usr/lib/libdbus-1.so.3 > Reading symbols from /usr/lib/libgnutls.so.13...done. > Loaded symbols for /usr/lib/libgnutls.so.13 > Reading symbols from /usr/lib/libavahi-glib.so.1...done. > Loaded symbols for /usr/lib/libavahi-glib.so.1 > Reading symbols from /usr/lib/libavahi-common.so.3...done. > Loaded symbols for /usr/lib/libavahi-common.so.3 > Reading symbols from /usr/lib/libavahi-client.so.3...done. > Loaded symbols for /usr/lib/libavahi-client.so.3 > Reading symbols from /lib/tls/i686/cmov/libresolv.so.2...done. > Loaded symbols for /lib/tls/i686/cmov/libresolv.so.2 > Reading symbols from /lib/libselinux.so.1...done. > Loaded symbols for /lib/libselinux.so.1 > Reading symbols from /lib/tls/i686/cmov/libutil.so.1...done. > Loaded symbols for /lib/tls/i686/cmov/libutil.so.1 > Reading symbols from /lib/tls/i686/cmov/librt.so.1...done. > Loaded symbols for /lib/tls/i686/cmov/librt.so.1 > Reading symbols from /lib/ld-linux.so.2...done. > Loaded symbols for /lib/ld-linux.so.2 > Reading symbols from /usr/lib/libfreetype.so.6...done. > Loaded symbols for /usr/lib/libfreetype.so.6 > Reading symbols from /usr/lib/libz.so.1...done. > Loaded symbols for /usr/lib/libz.so.1 > Reading symbols from /usr/lib/libexpat.so.1...done. > Loaded symbols for /usr/lib/libexpat.so.1 > Reading symbols from /usr/lib/libpng12.so.0...done. > Loaded symbols for /usr/lib/libpng12.so.0 > Reading symbols from /usr/lib/libasound.so.2...done. > Loaded symbols for /usr/lib/libasound.so.2 > Reading symbols from /lib/tls/i686/cmov/libnsl.so.1...done. > Loaded symbols for /lib/tls/i686/cmov/libnsl.so.1 > Reading symbols from /usr/lib/libtasn1.so.3...done. > Loaded symbols for /usr/lib/libtasn1.so.3 > Reading symbols from /usr/lib/libgcrypt.so.11...done. > Loaded symbols for /usr/lib/libgcrypt.so.11 > Reading symbols from /usr/lib/libgpg-error.so.0...done. > Loaded symbols for /usr/lib/libgpg-error.so.0 > Reading symbols from /lib/libsepol.so.1...done. > Loaded symbols for /lib/libsepol.so.1 > Reading symbols from /usr/lib/X11/locale/common/xlcUTF8Load.so.2...done. > Loaded symbols for /usr/lib/X11/locale/common/xlcUTF8Load.so.2 > Reading symbols from /lib/tls/i686/cmov/libnss_compat.so.2...done. > Loaded symbols for /lib/tls/i686/cmov/libnss_compat.so.2 > Reading symbols from /lib/tls/i686/cmov/libnss_nis.so.2...done. > Loaded symbols for /lib/tls/i686/cmov/libnss_nis.so.2 > Reading symbols from /lib/tls/i686/cmov/libnss_files.so.2...done. > Loaded symbols for /lib/tls/i686/cmov/libnss_files.so.2 > Reading symbols from /usr/lib/gtk-2.0/modules/libgail.so...done. > Loaded symbols for /usr/lib/gtk-2.0/modules/libgail.so > Reading symbols from /usr/lib/libgailutil.so.18...done. > Loaded symbols for /usr/lib/libgailutil.so.18 > Reading symbols from /usr/lib/gtk-2.0/modules/libatk-bridge.so...done. > Loaded symbols for /usr/lib/gtk-2.0/modules/libatk-bridge.so > Reading symbols from /usr/lib/libspi.so.0...Reading symbols from /usr/lib/debug/usr/lib/libspi.so.0.10.11...done. > done. > Loaded symbols for /usr/lib/libspi.so.0 > Reading symbols from /usr/lib/libXtst.so.6...done. > Loaded symbols for /usr/lib/libXtst.so.6 > Reading symbols from /usr/lib/gtk-2.0/modules/libgail-gnome.so...done. > Loaded symbols for /usr/lib/gtk-2.0/modules/libgail-gnome.so > Reading symbols from /usr/lib/libpanel-applet-2.so.0...done. > Loaded symbols for /usr/lib/libpanel-applet-2.so.0 > Reading symbols from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so...done. > Loaded symbols for /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so > Reading symbols from /usr/lib/gtk-2.0/2.10.0/engines/libubuntulooks.so...done. > Loaded symbols for /usr/lib/gtk-2.0/2.10.0/engines/libubuntulooks.so > Reading symbols from /usr/lib/gconv/ISO8859-1.so...done. > Loaded symbols for /usr/lib/gconv/ISO8859-1.so > Reading symbols from /usr/lib/pango/1.6.0/modules/pango-basic-fc.so...done. > Loaded symbols for /usr/lib/pango/1.6.0/modules/pango-basic-fc.so > 0xb7f55410 in ?? () > (gdb) continue > Continuing. > > Program received signal SIGABRT, Aborted. > [Switching to Thread -1226762560 (LWP 4841)] > 0xb7f55410 in ?? () > (gdb) bt > #0 0xb7f55410 in ?? () > #1 0xbf9fff8c in ?? () > #2 0x00000006 in ?? () > #3 0x000012e9 in ?? () > #4 0xb7529df0 in raise () from /lib/tls/i686/cmov/libc.so.6 > #5 0xb752b641 in abort () from /lib/tls/i686/cmov/libc.so.6 > #6 0xb767864a in IA__g_logv (log_domain=, > log_level=G_LOG_LEVEL_ERROR, > format=0xb76a2b6c "%s: failed to allocate %lu bytes", > args1=0xbfa0056c "\030.j������\005") at gmessages.c:497 > #7 0xb7678689 in IA__g_log (log_domain=0xb769bfe6 "GLib", > log_level=G_LOG_LEVEL_ERROR, > format=0xb76a2b6c "%s: failed to allocate %lu bytes") at gmessages.c:517 > #8 0xb7677249 in IA__g_malloc (n_bytes=4294967257) at gmem.c:135 > #9 0xb7d841aa in vte_terminal_accessible_get_text (text=0x83d56a0, > start_offset=560, end_offset=561) > at /home/kenny/src/vte/vte-0.15.0/./src/vteaccess.c:982 > #10 0xb7d8464d in vte_terminal_accessible_get_text_somewhere (text=0x83d56a0, > offset=560, boundary_type=ATK_TEXT_BOUNDARY_LINE_START, > direction=direction_current, start_offset=0xbfa006e4, > end_offset=0xbfa006e0) > at /home/kenny/src/vte/vte-0.15.0/./src/vteaccess.c:1164 > #11 0xb7d847ad in vte_terminal_accessible_get_text_at_offset (text=0x83d56a0, > offset=560, boundary_type=ATK_TEXT_BOUNDARY_LINE_START, > start_offset=0xbfa006e4, end_offset=0xbfa006e0) > at /home/kenny/src/vte/vte-0.15.0/./src/vteaccess.c:1212 > #12 0xb796d6ed in atk_text_get_text_at_offset (text=0x83d56a0, offset=560, > boundary_type=ATK_TEXT_BOUNDARY_LINE_START, start_offset=0xbfa006e4, > end_offset=0xbfa006e0) at atktext.c:386 > #13 0xb6c57d41 in impl_getTextAtOffset (servant=0x84b4904, offset=560, > type=Accessibility_TEXT_BOUNDARY_LINE_START, startOffset=0xbfa007b0, > endOffset=0xbfa00790, ev=0xbfa009dc) at text.c:128 > #14 0xb6c4dacf in _ORBIT_skel_small_Accessibility_Text_getTextAtOffset ( > _o_servant=0x84b4904, _o_retval=0xbfa00850, _o_args=0xbfa00830, > _o_ctx=0xbfa008c8, _o_ev=0xbfa009dc, > _impl_getTextAtOffset=0xb6c57cc1 ) > at Accessibility-common.c:700 > #15 0xb77b9797 in ?? () from /usr/lib/libORBit-2.so.0 > #16 0x084b4904 in ?? () > #17 0xbfa00850 in ?? () > #18 0xbfa00830 in ?? () > #19 0xbfa008c8 in ?? () > #20 0xbfa009dc in ?? () > #21 0xb6c57cc1 in impl_getTextAfterOffset (servant=0x84a6508, > offset=-1080031152, type=3214936112, startOffset=0xbfa008c8, > endOffset=0xbfa00948, ev=0xbfa009dc) at text.c:110 > #22 0xb77bf905 in ORBit_OAObject_invoke () from /usr/lib/libORBit-2.so.0 > #23 0xb77aca1c in ORBit_small_invoke_adaptor () from /usr/lib/libORBit-2.so.0 > #24 0xb77bd5a6 in ?? () from /usr/lib/libORBit-2.so.0 > #25 0x084a6508 in ?? () > #26 0x084d9600 in ?? () > #27 0xb6c66ae0 in Accessibility_Text__imethods () from /usr/lib/libspi.so.0 > #28 0xbfa00948 in ?? () > #29 0xbfa009dc in ?? () > #30 0xb77dad90 in ?? () from /usr/lib/libORBit-2.so.0 > #31 0xbfa00948 in ?? () > #32 0xb76d51ec in ?? () from /usr/lib/libglib-2.0.so.0 > #33 0x084d9600 in ?? () > #34 0xbfa00950 in ?? () > #35 0x080d35cc in ?? () > #36 0xb777a451 in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0 > #37 0xb77bdc52 in ?? () from /usr/lib/libORBit-2.so.0 > #38 0x084a6508 in ?? () > #39 0x084fe734 in ?? () > #40 0x00000000 in ?? () > (gdb) quit > The program is running. Quit anyway (and detach it)? (y or n) (gdb) continue > Continuing. > > Program terminated with signal SIGABRT, Aborted. > The program no longer exists. > (gdb) quit > > ------------------------------------------------------------------------ > > _______________________________________________ > gnome-accessibility-list mailing list > gnome-accessibility-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list > From Li.Yuan at Sun.COM Wed Jan 10 11:00:08 2007 From: Li.Yuan at Sun.COM (Li Yuan) Date: Wed, 10 Jan 2007 19:00:08 +0800 Subject: gnome-terminal crash in Feisty In-Reply-To: <45A49F90.40801@sun.com> References: <20070108152646.GA25560@mail.hittsjunk.net> <45A267D5.1040401@sun.com> <20070108220901.GA26328@mail.hittsjunk.net> <45A348B7.2000001@sun.com> <20070109150203.GA29274@mail.hittsjunk.net> <45A3B52B.2040800@sun.com> <20070109162038.GB29402@mail.hittsjunk.net> <20070109173456.GA29714@mail.hittsjunk.net> <45A49F90.40801@sun.com> Message-ID: <1168426808.6227.6.camel@match> Yes, I think it is vte's problem. I saw (start_offset=560, end_offset=561). It is strange, end-start should be a reasonable positive value, not that big (4294967257). Li On Wed, 2007-01-10 at 08:10 +0000, Padraig O'Briain wrote: > #8 0xb7677249 in IA__g_malloc (n_bytes=4294967257) at gmem.c:135 > > This shows that the number of bytes is wrong. > > I suggest logging a bug againt vte. > > I would be helpful if we knew what the text was. > > > Kenny Hitt wrote: > > Replying to myself since I deleted the other messages in the thread. > > > > I used tee to capture the output of the gdb session since the output was > > causing problems for vim when I used speakup's cut and paste. > > > > I installed the dbg versions of glib, atk, and at-spi. Hopefully this > > log will provide enough info. > > > > If more is needed, let me know. > > > > Kenny > > > > > > ------------------------------------------------------------------------ > > > > GNU gdb 6.6-debian > > Copyright (C) 2006 Free Software Foundation, Inc. > > GDB is free software, covered by the GNU General Public License, and you are > > welcome to change it and/or distribute copies of it under certain conditions. > > Type "show copying" to see the conditions. > > There is absolutely no warranty for GDB. Type "show warranty" for details. > > This GDB was configured as "i486-linux-gnu"... > > (no debugging symbols found) > > Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". > > Attaching to program: /usr/bin/gnome-terminal, process 4841 > > Reading symbols from /usr/lib/liblaunchpad-integration.so.0...(no debugging symbols found)...done. > > Loaded symbols for /usr/lib/liblaunchpad-integration.so.0 > > Reading symbols from /usr/lib/libglade-2.0.so.0...(no debugging symbols found)...done. > > Loaded symbols for /usr/lib/libglade-2.0.so.0 > > Reading symbols from /usr/lib/libgnomeui-2.so.0... > > (no debugging symbols found)...done. > > Loaded symbols for /usr/lib/libgnomeui-2.so.0 > > Reading symbols from /usr/lib/libgnome-2.so.0...(no debugging symbols found)...done. > > Loaded symbols for /usr/lib/libgnome-2.so.0 > > Reading symbols from /usr/lib/libbonobo-2.so.0... > > (no debugging symbols found)...done. > > Loaded symbols for /usr/lib/libbonobo-2.so.0 > > Reading symbols from /usr/lib/libbonobo-activation.so.4...(no debugging symbols found)...done. > > Loaded symbols for /usr/lib/libbonobo-activation.so.4 > > Reading symbols from /usr/lib/libstartup-notification-1.so.0... > > (no debugging symbols found)...done. > > Loaded symbols for /usr/lib/libstartup-notification-1.so.0 > > Reading symbols from /usr/lib/libvte.so.9...done. > > Loaded symbols for /usr/lib/libvte.so.9 > > Reading symbols from /usr/lib/libgtk-x11-2.0.so.0...done. > > Loaded symbols for /usr/lib/libgtk-x11-2.0.so.0 > > Reading symbols from /usr/lib/libgdk-x11-2.0.so.0...done. > > Loaded symbols for /usr/lib/libgdk-x11-2.0.so.0 > > Reading symbols from /usr/lib/libatk-1.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libatk-1.0.so.0.1310.1...done. > > done. > > Loaded symbols for /usr/lib/libatk-1.0.so.0 > > Reading symbols from /usr/lib/libgdk_pixbuf-2.0.so.0...done. > > Loaded symbols for /usr/lib/libgdk_pixbuf-2.0.so.0 > > Reading symbols from /usr/lib/libXrender.so.1...done. > > Loaded symbols for /usr/lib/libXrender.so.1 > > Reading symbols from /usr/lib/libX11.so.6...done. > > Loaded symbols for /usr/lib/libX11.so.6 > > Reading symbols from /usr/lib/libgnomevfs-2.so.0...done. > > Loaded symbols for /usr/lib/libgnomevfs-2.so.0 > > Reading symbols from /usr/lib/libgconf-2.so.4...done. > > Loaded symbols for /usr/lib/libgconf-2.so.4 > > Reading symbols from /lib/libpopt.so.0...done. > > Loaded symbols for /lib/libpopt.so.0 > > Reading symbols from /usr/lib/libORBit-2.so.0...done. > > Loaded symbols for /usr/lib/libORBit-2.so.0 > > Reading symbols from /lib/tls/i686/cmov/libpthread.so.0...done. > > [Thread debugging using libthread_db enabled] > > [New Thread -1226762560 (LWP 4841)] > > [New Thread -1251951728 (LWP 4849)] > > Loaded symbols for /lib/tls/i686/cmov/libpthread.so.0 > > Reading symbols from /lib/tls/i686/cmov/libm.so.6...done. > > Loaded symbols for /lib/tls/i686/cmov/libm.so.6 > > Reading symbols from /usr/lib/libpango-1.0.so.0...done. > > Loaded symbols for /usr/lib/libpango-1.0.so.0 > > Reading symbols from /usr/lib/libgobject-2.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libgobject-2.0.so.0.1200.7...done. > > done. > > Loaded symbols for /usr/lib/libgobject-2.0.so.0 > > Reading symbols from /usr/lib/libglib-2.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libglib-2.0.so.0.1200.7...done. > > done. > > Loaded symbols for /usr/lib/libglib-2.0.so.0 > > Reading symbols from /lib/tls/i686/cmov/libc.so.6...done. > > Loaded symbols for /lib/tls/i686/cmov/libc.so.6 > > Reading symbols from /usr/lib/libpangocairo-1.0.so.0...done. > > Loaded symbols for /usr/lib/libpangocairo-1.0.so.0 > > Reading symbols from /usr/lib/libfontconfig.so.1...done. > > Loaded symbols for /usr/lib/libfontconfig.so.1 > > Reading symbols from /usr/lib/libXext.so.6...done. > > Loaded symbols for /usr/lib/libXext.so.6 > > Reading symbols from /usr/lib/libXinerama.so.1...done. > > Loaded symbols for /usr/lib/libXinerama.so.1 > > Reading symbols from /usr/lib/libXi.so.6...done. > > Loaded symbols for /usr/lib/libXi.so.6 > > Reading symbols from /usr/lib/libXrandr.so.2...done. > > Loaded symbols for /usr/lib/libXrandr.so.2 > > Reading symbols from /usr/lib/libXcursor.so.1...done. > > Loaded symbols for /usr/lib/libXcursor.so.1 > > Reading symbols from /usr/lib/libXfixes.so.3...done. > > Loaded symbols for /usr/lib/libXfixes.so.3 > > Reading symbols from /usr/lib/libcairo.so.2...done. > > Loaded symbols for /usr/lib/libcairo.so.2 > > Reading symbols from /usr/lib/libgmodule-2.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libgmodule-2.0.so.0.1200.7...done. > > done. > > Loaded symbols for /usr/lib/libgmodule-2.0.so.0 > > Reading symbols from /lib/tls/i686/cmov/libdl.so.2...done. > > Loaded symbols for /lib/tls/i686/cmov/libdl.so.2 > > Reading symbols from /usr/lib/libxml2.so.2...done. > > Loaded symbols for /usr/lib/libxml2.so.2 > > Reading symbols from /usr/lib/libbonoboui-2.so.0...done. > > Loaded symbols for /usr/lib/libbonoboui-2.so.0 > > Reading symbols from /usr/lib/libgnomecanvas-2.so.0...done. > > Loaded symbols for /usr/lib/libgnomecanvas-2.so.0 > > Reading symbols from /usr/lib/libart_lgpl_2.so.2...done. > > Loaded symbols for /usr/lib/libart_lgpl_2.so.2 > > Reading symbols from /usr/lib/libpangoft2-1.0.so.0...done. > > Loaded symbols for /usr/lib/libpangoft2-1.0.so.0 > > Reading symbols from /usr/lib/libgthread-2.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libgthread-2.0.so.0.1200.7...done. > > done. > > Loaded symbols for /usr/lib/libgthread-2.0.so.0 > > Reading symbols from /usr/lib/libgnome-keyring.so.0...done. > > Loaded symbols for /usr/lib/libgnome-keyring.so.0 > > Reading symbols from /usr/lib/libjpeg.so.62...done. > > Loaded symbols for /usr/lib/libjpeg.so.62 > > Reading symbols from /usr/lib/libSM.so.6...done. > > Loaded symbols for /usr/lib/libSM.so.6 > > Reading symbols from /usr/lib/libICE.so.6...done. > > Loaded symbols for /usr/lib/libICE.so.6 > > Reading symbols from /usr/lib/libesd.so.0...done. > > Loaded symbols for /usr/lib/libesd.so.0 > > Reading symbols from /usr/lib/libaudiofile.so.0...done. > > Loaded symbols for /usr/lib/libaudiofile.so.0 > > Reading symbols from /usr/lib/libORBitCosNaming-2.so.0...done. > > Loaded symbols for /usr/lib/libORBitCosNaming-2.so.0 > > Reading symbols from /usr/lib/libXft.so.2...done. > > Loaded symbols for /usr/lib/libXft.so.2 > > Reading symbols from /usr/lib/libpangoxft-1.0.so.0...done. > > Loaded symbols for /usr/lib/libpangoxft-1.0.so.0 > > Reading symbols from /usr/lib/libpangox-1.0.so.0...done. > > Loaded symbols for /usr/lib/libpangox-1.0.so.0 > > Reading symbols from /lib/libncurses.so.5...done. > > Loaded symbols for /lib/libncurses.so.5 > > Reading symbols from /usr/lib/libXau.so.6...done. > > Loaded symbols for /usr/lib/libXau.so.6 > > Reading symbols from /usr/lib/libXdmcp.so.6...done. > > Loaded symbols for /usr/lib/libXdmcp.so.6 > > Reading symbols from /usr/lib/libdbus-glib-1.so.2...done. > > Loaded symbols for /usr/lib/libdbus-glib-1.so.2 > > Reading symbols from /usr/lib/libdbus-1.so.3...done. > > Loaded symbols for /usr/lib/libdbus-1.so.3 > > Reading symbols from /usr/lib/libgnutls.so.13...done. > > Loaded symbols for /usr/lib/libgnutls.so.13 > > Reading symbols from /usr/lib/libavahi-glib.so.1...done. > > Loaded symbols for /usr/lib/libavahi-glib.so.1 > > Reading symbols from /usr/lib/libavahi-common.so.3...done. > > Loaded symbols for /usr/lib/libavahi-common.so.3 > > Reading symbols from /usr/lib/libavahi-client.so.3...done. > > Loaded symbols for /usr/lib/libavahi-client.so.3 > > Reading symbols from /lib/tls/i686/cmov/libresolv.so.2...done. > > Loaded symbols for /lib/tls/i686/cmov/libresolv.so.2 > > Reading symbols from /lib/libselinux.so.1...done. > > Loaded symbols for /lib/libselinux.so.1 > > Reading symbols from /lib/tls/i686/cmov/libutil.so.1...done. > > Loaded symbols for /lib/tls/i686/cmov/libutil.so.1 > > Reading symbols from /lib/tls/i686/cmov/librt.so.1...done. > > Loaded symbols for /lib/tls/i686/cmov/librt.so.1 > > Reading symbols from /lib/ld-linux.so.2...done. > > Loaded symbols for /lib/ld-linux.so.2 > > Reading symbols from /usr/lib/libfreetype.so.6...done. > > Loaded symbols for /usr/lib/libfreetype.so.6 > > Reading symbols from /usr/lib/libz.so.1...done. > > Loaded symbols for /usr/lib/libz.so.1 > > Reading symbols from /usr/lib/libexpat.so.1...done. > > Loaded symbols for /usr/lib/libexpat.so.1 > > Reading symbols from /usr/lib/libpng12.so.0...done. > > Loaded symbols for /usr/lib/libpng12.so.0 > > Reading symbols from /usr/lib/libasound.so.2...done. > > Loaded symbols for /usr/lib/libasound.so.2 > > Reading symbols from /lib/tls/i686/cmov/libnsl.so.1...done. > > Loaded symbols for /lib/tls/i686/cmov/libnsl.so.1 > > Reading symbols from /usr/lib/libtasn1.so.3...done. > > Loaded symbols for /usr/lib/libtasn1.so.3 > > Reading symbols from /usr/lib/libgcrypt.so.11...done. > > Loaded symbols for /usr/lib/libgcrypt.so.11 > > Reading symbols from /usr/lib/libgpg-error.so.0...done. > > Loaded symbols for /usr/lib/libgpg-error.so.0 > > Reading symbols from /lib/libsepol.so.1...done. > > Loaded symbols for /lib/libsepol.so.1 > > Reading symbols from /usr/lib/X11/locale/common/xlcUTF8Load.so.2...done. > > Loaded symbols for /usr/lib/X11/locale/common/xlcUTF8Load.so.2 > > Reading symbols from /lib/tls/i686/cmov/libnss_compat.so.2...done. > > Loaded symbols for /lib/tls/i686/cmov/libnss_compat.so.2 > > Reading symbols from /lib/tls/i686/cmov/libnss_nis.so.2...done. > > Loaded symbols for /lib/tls/i686/cmov/libnss_nis.so.2 > > Reading symbols from /lib/tls/i686/cmov/libnss_files.so.2...done. > > Loaded symbols for /lib/tls/i686/cmov/libnss_files.so.2 > > Reading symbols from /usr/lib/gtk-2.0/modules/libgail.so...done. > > Loaded symbols for /usr/lib/gtk-2.0/modules/libgail.so > > Reading symbols from /usr/lib/libgailutil.so.18...done. > > Loaded symbols for /usr/lib/libgailutil.so.18 > > Reading symbols from /usr/lib/gtk-2.0/modules/libatk-bridge.so...done. > > Loaded symbols for /usr/lib/gtk-2.0/modules/libatk-bridge.so > > Reading symbols from /usr/lib/libspi.so.0...Reading symbols from /usr/lib/debug/usr/lib/libspi.so.0.10.11...done. > > done. > > Loaded symbols for /usr/lib/libspi.so.0 > > Reading symbols from /usr/lib/libXtst.so.6...done. > > Loaded symbols for /usr/lib/libXtst.so.6 > > Reading symbols from /usr/lib/gtk-2.0/modules/libgail-gnome.so...done. > > Loaded symbols for /usr/lib/gtk-2.0/modules/libgail-gnome.so > > Reading symbols from /usr/lib/libpanel-applet-2.so.0...done. > > Loaded symbols for /usr/lib/libpanel-applet-2.so.0 > > Reading symbols from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so...done. > > Loaded symbols for /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so > > Reading symbols from /usr/lib/gtk-2.0/2.10.0/engines/libubuntulooks.so...done. > > Loaded symbols for /usr/lib/gtk-2.0/2.10.0/engines/libubuntulooks.so > > Reading symbols from /usr/lib/gconv/ISO8859-1.so...done. > > Loaded symbols for /usr/lib/gconv/ISO8859-1.so > > Reading symbols from /usr/lib/pango/1.6.0/modules/pango-basic-fc.so...done. > > Loaded symbols for /usr/lib/pango/1.6.0/modules/pango-basic-fc.so > > 0xb7f55410 in ?? () > > (gdb) continue > > Continuing. > > > > Program received signal SIGABRT, Aborted. > > [Switching to Thread -1226762560 (LWP 4841)] > > 0xb7f55410 in ?? () > > (gdb) bt > > #0 0xb7f55410 in ?? () > > #1 0xbf9fff8c in ?? () > > #2 0x00000006 in ?? () > > #3 0x000012e9 in ?? () > > #4 0xb7529df0 in raise () from /lib/tls/i686/cmov/libc.so.6 > > #5 0xb752b641 in abort () from /lib/tls/i686/cmov/libc.so.6 > > #6 0xb767864a in IA__g_logv (log_domain=, > > log_level=G_LOG_LEVEL_ERROR, > > format=0xb76a2b6c "%s: failed to allocate %lu bytes", > > args1=0xbfa0056c "\030.j������\005") at gmessages.c:497 > > #7 0xb7678689 in IA__g_log (log_domain=0xb769bfe6 "GLib", > > log_level=G_LOG_LEVEL_ERROR, > > format=0xb76a2b6c "%s: failed to allocate %lu bytes") at gmessages.c:517 > > #8 0xb7677249 in IA__g_malloc (n_bytes=4294967257) at gmem.c:135 > > #9 0xb7d841aa in vte_terminal_accessible_get_text (text=0x83d56a0, > > start_offset=560, end_offset=561) > > at /home/kenny/src/vte/vte-0.15.0/./src/vteaccess.c:982 > > #10 0xb7d8464d in vte_terminal_accessible_get_text_somewhere (text=0x83d56a0, > > offset=560, boundary_type=ATK_TEXT_BOUNDARY_LINE_START, > > direction=direction_current, start_offset=0xbfa006e4, > > end_offset=0xbfa006e0) > > at /home/kenny/src/vte/vte-0.15.0/./src/vteaccess.c:1164 > > #11 0xb7d847ad in vte_terminal_accessible_get_text_at_offset (text=0x83d56a0, > > offset=560, boundary_type=ATK_TEXT_BOUNDARY_LINE_START, > > start_offset=0xbfa006e4, end_offset=0xbfa006e0) > > at /home/kenny/src/vte/vte-0.15.0/./src/vteaccess.c:1212 > > #12 0xb796d6ed in atk_text_get_text_at_offset (text=0x83d56a0, offset=560, > > boundary_type=ATK_TEXT_BOUNDARY_LINE_START, start_offset=0xbfa006e4, > > end_offset=0xbfa006e0) at atktext.c:386 > > #13 0xb6c57d41 in impl_getTextAtOffset (servant=0x84b4904, offset=560, > > type=Accessibility_TEXT_BOUNDARY_LINE_START, startOffset=0xbfa007b0, > > endOffset=0xbfa00790, ev=0xbfa009dc) at text.c:128 > > #14 0xb6c4dacf in _ORBIT_skel_small_Accessibility_Text_getTextAtOffset ( > > _o_servant=0x84b4904, _o_retval=0xbfa00850, _o_args=0xbfa00830, > > _o_ctx=0xbfa008c8, _o_ev=0xbfa009dc, > > _impl_getTextAtOffset=0xb6c57cc1 ) > > at Accessibility-common.c:700 > > #15 0xb77b9797 in ?? () from /usr/lib/libORBit-2.so.0 > > #16 0x084b4904 in ?? () > > #17 0xbfa00850 in ?? () > > #18 0xbfa00830 in ?? () > > #19 0xbfa008c8 in ?? () > > #20 0xbfa009dc in ?? () > > #21 0xb6c57cc1 in impl_getTextAfterOffset (servant=0x84a6508, > > offset=-1080031152, type=3214936112, startOffset=0xbfa008c8, > > endOffset=0xbfa00948, ev=0xbfa009dc) at text.c:110 > > #22 0xb77bf905 in ORBit_OAObject_invoke () from /usr/lib/libORBit-2.so.0 > > #23 0xb77aca1c in ORBit_small_invoke_adaptor () from /usr/lib/libORBit-2.so.0 > > #24 0xb77bd5a6 in ?? () from /usr/lib/libORBit-2.so.0 > > #25 0x084a6508 in ?? () > > #26 0x084d9600 in ?? () > > #27 0xb6c66ae0 in Accessibility_Text__imethods () from /usr/lib/libspi.so.0 > > #28 0xbfa00948 in ?? () > > #29 0xbfa009dc in ?? () > > #30 0xb77dad90 in ?? () from /usr/lib/libORBit-2.so.0 > > #31 0xbfa00948 in ?? () > > #32 0xb76d51ec in ?? () from /usr/lib/libglib-2.0.so.0 > > #33 0x084d9600 in ?? () > > #34 0xbfa00950 in ?? () > > #35 0x080d35cc in ?? () > > #36 0xb777a451 in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0 > > #37 0xb77bdc52 in ?? () from /usr/lib/libORBit-2.so.0 > > #38 0x084a6508 in ?? () > > #39 0x084fe734 in ?? () > > #40 0x00000000 in ?? () > > (gdb) quit > > The program is running. Quit anyway (and detach it)? (y or n) (gdb) continue > > Continuing. > > > > Program terminated with signal SIGABRT, Aborted. > > The program no longer exists. > > (gdb) quit > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > gnome-accessibility-list mailing list > > gnome-accessibility-list at gnome.org > > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list > > > > _______________________________________________ > gnome-accessibility-list mailing list > gnome-accessibility-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list From Padraig.Obriain at Sun.COM Wed Jan 10 11:05:58 2007 From: Padraig.Obriain at Sun.COM (Padraig O'Briain) Date: Wed, 10 Jan 2007 11:05:58 +0000 Subject: gnome-terminal crash in Feisty In-Reply-To: <1168426808.6227.6.camel@match> References: <20070108152646.GA25560@mail.hittsjunk.net> <45A267D5.1040401@sun.com> <20070108220901.GA26328@mail.hittsjunk.net> <45A348B7.2000001@sun.com> <20070109150203.GA29274@mail.hittsjunk.net> <45A3B52B.2040800@sun.com> <20070109162038.GB29402@mail.hittsjunk.net> <20070109173456.GA29714@mail.hittsjunk.net> <45A49F90.40801@sun.com> <1168426808.6227.6.camel@match> Message-ID: <45A4C896.6010809@sun.com> I had a quick look at the code and it is calculating character offsets. One possibility is that 560 or 561 is in the middle of a character. Li Yuan wrote: > Yes, I think it is vte's problem. > > I saw (start_offset=560, end_offset=561). It is strange, end-start > should be a reasonable positive value, not that big (4294967257). > > Li > > On Wed, 2007-01-10 at 08:10 +0000, Padraig O'Briain wrote: > >> #8 0xb7677249 in IA__g_malloc (n_bytes=4294967257) at gmem.c:135 >> >> This shows that the number of bytes is wrong. >> >> I suggest logging a bug againt vte. >> >> I would be helpful if we knew what the text was. >> >> >> Kenny Hitt wrote: >> >>> Replying to myself since I deleted the other messages in the thread. >>> >>> I used tee to capture the output of the gdb session since the output was >>> causing problems for vim when I used speakup's cut and paste. >>> >>> I installed the dbg versions of glib, atk, and at-spi. Hopefully this >>> log will provide enough info. >>> >>> If more is needed, let me know. >>> >>> Kenny >>> >>> >>> ------------------------------------------------------------------------ >>> >>> GNU gdb 6.6-debian >>> Copyright (C) 2006 Free Software Foundation, Inc. >>> GDB is free software, covered by the GNU General Public License, and you are >>> welcome to change it and/or distribute copies of it under certain conditions. >>> Type "show copying" to see the conditions. >>> There is absolutely no warranty for GDB. Type "show warranty" for details. >>> This GDB was configured as "i486-linux-gnu"... >>> (no debugging symbols found) >>> Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". >>> Attaching to program: /usr/bin/gnome-terminal, process 4841 >>> Reading symbols from /usr/lib/liblaunchpad-integration.so.0...(no debugging symbols found)...done. >>> Loaded symbols for /usr/lib/liblaunchpad-integration.so.0 >>> Reading symbols from /usr/lib/libglade-2.0.so.0...(no debugging symbols found)...done. >>> Loaded symbols for /usr/lib/libglade-2.0.so.0 >>> Reading symbols from /usr/lib/libgnomeui-2.so.0... >>> (no debugging symbols found)...done. >>> Loaded symbols for /usr/lib/libgnomeui-2.so.0 >>> Reading symbols from /usr/lib/libgnome-2.so.0...(no debugging symbols found)...done. >>> Loaded symbols for /usr/lib/libgnome-2.so.0 >>> Reading symbols from /usr/lib/libbonobo-2.so.0... >>> (no debugging symbols found)...done. >>> Loaded symbols for /usr/lib/libbonobo-2.so.0 >>> Reading symbols from /usr/lib/libbonobo-activation.so.4...(no debugging symbols found)...done. >>> Loaded symbols for /usr/lib/libbonobo-activation.so.4 >>> Reading symbols from /usr/lib/libstartup-notification-1.so.0... >>> (no debugging symbols found)...done. >>> Loaded symbols for /usr/lib/libstartup-notification-1.so.0 >>> Reading symbols from /usr/lib/libvte.so.9...done. >>> Loaded symbols for /usr/lib/libvte.so.9 >>> Reading symbols from /usr/lib/libgtk-x11-2.0.so.0...done. >>> Loaded symbols for /usr/lib/libgtk-x11-2.0.so.0 >>> Reading symbols from /usr/lib/libgdk-x11-2.0.so.0...done. >>> Loaded symbols for /usr/lib/libgdk-x11-2.0.so.0 >>> Reading symbols from /usr/lib/libatk-1.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libatk-1.0.so.0.1310.1...done. >>> done. >>> Loaded symbols for /usr/lib/libatk-1.0.so.0 >>> Reading symbols from /usr/lib/libgdk_pixbuf-2.0.so.0...done. >>> Loaded symbols for /usr/lib/libgdk_pixbuf-2.0.so.0 >>> Reading symbols from /usr/lib/libXrender.so.1...done. >>> Loaded symbols for /usr/lib/libXrender.so.1 >>> Reading symbols from /usr/lib/libX11.so.6...done. >>> Loaded symbols for /usr/lib/libX11.so.6 >>> Reading symbols from /usr/lib/libgnomevfs-2.so.0...done. >>> Loaded symbols for /usr/lib/libgnomevfs-2.so.0 >>> Reading symbols from /usr/lib/libgconf-2.so.4...done. >>> Loaded symbols for /usr/lib/libgconf-2.so.4 >>> Reading symbols from /lib/libpopt.so.0...done. >>> Loaded symbols for /lib/libpopt.so.0 >>> Reading symbols from /usr/lib/libORBit-2.so.0...done. >>> Loaded symbols for /usr/lib/libORBit-2.so.0 >>> Reading symbols from /lib/tls/i686/cmov/libpthread.so.0...done. >>> [Thread debugging using libthread_db enabled] >>> [New Thread -1226762560 (LWP 4841)] >>> [New Thread -1251951728 (LWP 4849)] >>> Loaded symbols for /lib/tls/i686/cmov/libpthread.so.0 >>> Reading symbols from /lib/tls/i686/cmov/libm.so.6...done. >>> Loaded symbols for /lib/tls/i686/cmov/libm.so.6 >>> Reading symbols from /usr/lib/libpango-1.0.so.0...done. >>> Loaded symbols for /usr/lib/libpango-1.0.so.0 >>> Reading symbols from /usr/lib/libgobject-2.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libgobject-2.0.so.0.1200.7...done. >>> done. >>> Loaded symbols for /usr/lib/libgobject-2.0.so.0 >>> Reading symbols from /usr/lib/libglib-2.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libglib-2.0.so.0.1200.7...done. >>> done. >>> Loaded symbols for /usr/lib/libglib-2.0.so.0 >>> Reading symbols from /lib/tls/i686/cmov/libc.so.6...done. >>> Loaded symbols for /lib/tls/i686/cmov/libc.so.6 >>> Reading symbols from /usr/lib/libpangocairo-1.0.so.0...done. >>> Loaded symbols for /usr/lib/libpangocairo-1.0.so.0 >>> Reading symbols from /usr/lib/libfontconfig.so.1...done. >>> Loaded symbols for /usr/lib/libfontconfig.so.1 >>> Reading symbols from /usr/lib/libXext.so.6...done. >>> Loaded symbols for /usr/lib/libXext.so.6 >>> Reading symbols from /usr/lib/libXinerama.so.1...done. >>> Loaded symbols for /usr/lib/libXinerama.so.1 >>> Reading symbols from /usr/lib/libXi.so.6...done. >>> Loaded symbols for /usr/lib/libXi.so.6 >>> Reading symbols from /usr/lib/libXrandr.so.2...done. >>> Loaded symbols for /usr/lib/libXrandr.so.2 >>> Reading symbols from /usr/lib/libXcursor.so.1...done. >>> Loaded symbols for /usr/lib/libXcursor.so.1 >>> Reading symbols from /usr/lib/libXfixes.so.3...done. >>> Loaded symbols for /usr/lib/libXfixes.so.3 >>> Reading symbols from /usr/lib/libcairo.so.2...done. >>> Loaded symbols for /usr/lib/libcairo.so.2 >>> Reading symbols from /usr/lib/libgmodule-2.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libgmodule-2.0.so.0.1200.7...done. >>> done. >>> Loaded symbols for /usr/lib/libgmodule-2.0.so.0 >>> Reading symbols from /lib/tls/i686/cmov/libdl.so.2...done. >>> Loaded symbols for /lib/tls/i686/cmov/libdl.so.2 >>> Reading symbols from /usr/lib/libxml2.so.2...done. >>> Loaded symbols for /usr/lib/libxml2.so.2 >>> Reading symbols from /usr/lib/libbonoboui-2.so.0...done. >>> Loaded symbols for /usr/lib/libbonoboui-2.so.0 >>> Reading symbols from /usr/lib/libgnomecanvas-2.so.0...done. >>> Loaded symbols for /usr/lib/libgnomecanvas-2.so.0 >>> Reading symbols from /usr/lib/libart_lgpl_2.so.2...done. >>> Loaded symbols for /usr/lib/libart_lgpl_2.so.2 >>> Reading symbols from /usr/lib/libpangoft2-1.0.so.0...done. >>> Loaded symbols for /usr/lib/libpangoft2-1.0.so.0 >>> Reading symbols from /usr/lib/libgthread-2.0.so.0...Reading symbols from /usr/lib/debug/usr/lib/libgthread-2.0.so.0.1200.7...done. >>> done. >>> Loaded symbols for /usr/lib/libgthread-2.0.so.0 >>> Reading symbols from /usr/lib/libgnome-keyring.so.0...done. >>> Loaded symbols for /usr/lib/libgnome-keyring.so.0 >>> Reading symbols from /usr/lib/libjpeg.so.62...done. >>> Loaded symbols for /usr/lib/libjpeg.so.62 >>> Reading symbols from /usr/lib/libSM.so.6...done. >>> Loaded symbols for /usr/lib/libSM.so.6 >>> Reading symbols from /usr/lib/libICE.so.6...done. >>> Loaded symbols for /usr/lib/libICE.so.6 >>> Reading symbols from /usr/lib/libesd.so.0...done. >>> Loaded symbols for /usr/lib/libesd.so.0 >>> Reading symbols from /usr/lib/libaudiofile.so.0...done. >>> Loaded symbols for /usr/lib/libaudiofile.so.0 >>> Reading symbols from /usr/lib/libORBitCosNaming-2.so.0...done. >>> Loaded symbols for /usr/lib/libORBitCosNaming-2.so.0 >>> Reading symbols from /usr/lib/libXft.so.2...done. >>> Loaded symbols for /usr/lib/libXft.so.2 >>> Reading symbols from /usr/lib/libpangoxft-1.0.so.0...done. >>> Loaded symbols for /usr/lib/libpangoxft-1.0.so.0 >>> Reading symbols from /usr/lib/libpangox-1.0.so.0...done. >>> Loaded symbols for /usr/lib/libpangox-1.0.so.0 >>> Reading symbols from /lib/libncurses.so.5...done. >>> Loaded symbols for /lib/libncurses.so.5 >>> Reading symbols from /usr/lib/libXau.so.6...done. >>> Loaded symbols for /usr/lib/libXau.so.6 >>> Reading symbols from /usr/lib/libXdmcp.so.6...done. >>> Loaded symbols for /usr/lib/libXdmcp.so.6 >>> Reading symbols from /usr/lib/libdbus-glib-1.so.2...done. >>> Loaded symbols for /usr/lib/libdbus-glib-1.so.2 >>> Reading symbols from /usr/lib/libdbus-1.so.3...done. >>> Loaded symbols for /usr/lib/libdbus-1.so.3 >>> Reading symbols from /usr/lib/libgnutls.so.13...done. >>> Loaded symbols for /usr/lib/libgnutls.so.13 >>> Reading symbols from /usr/lib/libavahi-glib.so.1...done. >>> Loaded symbols for /usr/lib/libavahi-glib.so.1 >>> Reading symbols from /usr/lib/libavahi-common.so.3...done. >>> Loaded symbols for /usr/lib/libavahi-common.so.3 >>> Reading symbols from /usr/lib/libavahi-client.so.3...done. >>> Loaded symbols for /usr/lib/libavahi-client.so.3 >>> Reading symbols from /lib/tls/i686/cmov/libresolv.so.2...done. >>> Loaded symbols for /lib/tls/i686/cmov/libresolv.so.2 >>> Reading symbols from /lib/libselinux.so.1...done. >>> Loaded symbols for /lib/libselinux.so.1 >>> Reading symbols from /lib/tls/i686/cmov/libutil.so.1...done. >>> Loaded symbols for /lib/tls/i686/cmov/libutil.so.1 >>> Reading symbols from /lib/tls/i686/cmov/librt.so.1...done. >>> Loaded symbols for /lib/tls/i686/cmov/librt.so.1 >>> Reading symbols from /lib/ld-linux.so.2...done. >>> Loaded symbols for /lib/ld-linux.so.2 >>> Reading symbols from /usr/lib/libfreetype.so.6...done. >>> Loaded symbols for /usr/lib/libfreetype.so.6 >>> Reading symbols from /usr/lib/libz.so.1...done. >>> Loaded symbols for /usr/lib/libz.so.1 >>> Reading symbols from /usr/lib/libexpat.so.1...done. >>> Loaded symbols for /usr/lib/libexpat.so.1 >>> Reading symbols from /usr/lib/libpng12.so.0...done. >>> Loaded symbols for /usr/lib/libpng12.so.0 >>> Reading symbols from /usr/lib/libasound.so.2...done. >>> Loaded symbols for /usr/lib/libasound.so.2 >>> Reading symbols from /lib/tls/i686/cmov/libnsl.so.1...done. >>> Loaded symbols for /lib/tls/i686/cmov/libnsl.so.1 >>> Reading symbols from /usr/lib/libtasn1.so.3...done. >>> Loaded symbols for /usr/lib/libtasn1.so.3 >>> Reading symbols from /usr/lib/libgcrypt.so.11...done. >>> Loaded symbols for /usr/lib/libgcrypt.so.11 >>> Reading symbols from /usr/lib/libgpg-error.so.0...done. >>> Loaded symbols for /usr/lib/libgpg-error.so.0 >>> Reading symbols from /lib/libsepol.so.1...done. >>> Loaded symbols for /lib/libsepol.so.1 >>> Reading symbols from /usr/lib/X11/locale/common/xlcUTF8Load.so.2...done. >>> Loaded symbols for /usr/lib/X11/locale/common/xlcUTF8Load.so.2 >>> Reading symbols from /lib/tls/i686/cmov/libnss_compat.so.2...done. >>> Loaded symbols for /lib/tls/i686/cmov/libnss_compat.so.2 >>> Reading symbols from /lib/tls/i686/cmov/libnss_nis.so.2...done. >>> Loaded symbols for /lib/tls/i686/cmov/libnss_nis.so.2 >>> Reading symbols from /lib/tls/i686/cmov/libnss_files.so.2...done. >>> Loaded symbols for /lib/tls/i686/cmov/libnss_files.so.2 >>> Reading symbols from /usr/lib/gtk-2.0/modules/libgail.so...done. >>> Loaded symbols for /usr/lib/gtk-2.0/modules/libgail.so >>> Reading symbols from /usr/lib/libgailutil.so.18...done. >>> Loaded symbols for /usr/lib/libgailutil.so.18 >>> Reading symbols from /usr/lib/gtk-2.0/modules/libatk-bridge.so...done. >>> Loaded symbols for /usr/lib/gtk-2.0/modules/libatk-bridge.so >>> Reading symbols from /usr/lib/libspi.so.0...Reading symbols from /usr/lib/debug/usr/lib/libspi.so.0.10.11...done. >>> done. >>> Loaded symbols for /usr/lib/libspi.so.0 >>> Reading symbols from /usr/lib/libXtst.so.6...done. >>> Loaded symbols for /usr/lib/libXtst.so.6 >>> Reading symbols from /usr/lib/gtk-2.0/modules/libgail-gnome.so...done. >>> Loaded symbols for /usr/lib/gtk-2.0/modules/libgail-gnome.so >>> Reading symbols from /usr/lib/libpanel-applet-2.so.0...done. >>> Loaded symbols for /usr/lib/libpanel-applet-2.so.0 >>> Reading symbols from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so...done. >>> Loaded symbols for /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so >>> Reading symbols from /usr/lib/gtk-2.0/2.10.0/engines/libubuntulooks.so...done. >>> Loaded symbols for /usr/lib/gtk-2.0/2.10.0/engines/libubuntulooks.so >>> Reading symbols from /usr/lib/gconv/ISO8859-1.so...done. >>> Loaded symbols for /usr/lib/gconv/ISO8859-1.so >>> Reading symbols from /usr/lib/pango/1.6.0/modules/pango-basic-fc.so...done. >>> Loaded symbols for /usr/lib/pango/1.6.0/modules/pango-basic-fc.so >>> 0xb7f55410 in ?? () >>> (gdb) continue >>> Continuing. >>> >>> Program received signal SIGABRT, Aborted. >>> [Switching to Thread -1226762560 (LWP 4841)] >>> 0xb7f55410 in ?? () >>> (gdb) bt >>> #0 0xb7f55410 in ?? () >>> #1 0xbf9fff8c in ?? () >>> #2 0x00000006 in ?? () >>> #3 0x000012e9 in ?? () >>> #4 0xb7529df0 in raise () from /lib/tls/i686/cmov/libc.so.6 >>> #5 0xb752b641 in abort () from /lib/tls/i686/cmov/libc.so.6 >>> #6 0xb767864a in IA__g_logv (log_domain=, >>> log_level=G_LOG_LEVEL_ERROR, >>> format=0xb76a2b6c "%s: failed to allocate %lu bytes", >>> args1=0xbfa0056c "\030.j������\005") at gmessages.c:497 >>> #7 0xb7678689 in IA__g_log (log_domain=0xb769bfe6 "GLib", >>> log_level=G_LOG_LEVEL_ERROR, >>> format=0xb76a2b6c "%s: failed to allocate %lu bytes") at gmessages.c:517 >>> #8 0xb7677249 in IA__g_malloc (n_bytes=4294967257) at gmem.c:135 >>> #9 0xb7d841aa in vte_terminal_accessible_get_text (text=0x83d56a0, >>> start_offset=560, end_offset=561) >>> at /home/kenny/src/vte/vte-0.15.0/./src/vteaccess.c:982 >>> #10 0xb7d8464d in vte_terminal_accessible_get_text_somewhere (text=0x83d56a0, >>> offset=560, boundary_type=ATK_TEXT_BOUNDARY_LINE_START, >>> direction=direction_current, start_offset=0xbfa006e4, >>> end_offset=0xbfa006e0) >>> at /home/kenny/src/vte/vte-0.15.0/./src/vteaccess.c:1164 >>> #11 0xb7d847ad in vte_terminal_accessible_get_text_at_offset (text=0x83d56a0, >>> offset=560, boundary_type=ATK_TEXT_BOUNDARY_LINE_START, >>> start_offset=0xbfa006e4, end_offset=0xbfa006e0) >>> at /home/kenny/src/vte/vte-0.15.0/./src/vteaccess.c:1212 >>> #12 0xb796d6ed in atk_text_get_text_at_offset (text=0x83d56a0, offset=560, >>> boundary_type=ATK_TEXT_BOUNDARY_LINE_START, start_offset=0xbfa006e4, >>> end_offset=0xbfa006e0) at atktext.c:386 >>> #13 0xb6c57d41 in impl_getTextAtOffset (servant=0x84b4904, offset=560, >>> type=Accessibility_TEXT_BOUNDARY_LINE_START, startOffset=0xbfa007b0, >>> endOffset=0xbfa00790, ev=0xbfa009dc) at text.c:128 >>> #14 0xb6c4dacf in _ORBIT_skel_small_Accessibility_Text_getTextAtOffset ( >>> _o_servant=0x84b4904, _o_retval=0xbfa00850, _o_args=0xbfa00830, >>> _o_ctx=0xbfa008c8, _o_ev=0xbfa009dc, >>> _impl_getTextAtOffset=0xb6c57cc1 ) >>> at Accessibility-common.c:700 >>> #15 0xb77b9797 in ?? () from /usr/lib/libORBit-2.so.0 >>> #16 0x084b4904 in ?? () >>> #17 0xbfa00850 in ?? () >>> #18 0xbfa00830 in ?? () >>> #19 0xbfa008c8 in ?? () >>> #20 0xbfa009dc in ?? () >>> #21 0xb6c57cc1 in impl_getTextAfterOffset (servant=0x84a6508, >>> offset=-1080031152, type=3214936112, startOffset=0xbfa008c8, >>> endOffset=0xbfa00948, ev=0xbfa009dc) at text.c:110 >>> #22 0xb77bf905 in ORBit_OAObject_invoke () from /usr/lib/libORBit-2.so.0 >>> #23 0xb77aca1c in ORBit_small_invoke_adaptor () from /usr/lib/libORBit-2.so.0 >>> #24 0xb77bd5a6 in ?? () from /usr/lib/libORBit-2.so.0 >>> #25 0x084a6508 in ?? () >>> #26 0x084d9600 in ?? () >>> #27 0xb6c66ae0 in Accessibility_Text__imethods () from /usr/lib/libspi.so.0 >>> #28 0xbfa00948 in ?? () >>> #29 0xbfa009dc in ?? () >>> #30 0xb77dad90 in ?? () from /usr/lib/libORBit-2.so.0 >>> #31 0xbfa00948 in ?? () >>> #32 0xb76d51ec in ?? () from /usr/lib/libglib-2.0.so.0 >>> #33 0x084d9600 in ?? () >>> #34 0xbfa00950 in ?? () >>> #35 0x080d35cc in ?? () >>> #36 0xb777a451 in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0 >>> #37 0xb77bdc52 in ?? () from /usr/lib/libORBit-2.so.0 >>> #38 0x084a6508 in ?? () >>> #39 0x084fe734 in ?? () >>> #40 0x00000000 in ?? () >>> (gdb) quit >>> The program is running. Quit anyway (and detach it)? (y or n) (gdb) continue >>> Continuing. >>> >>> Program terminated with signal SIGABRT, Aborted. >>> The program no longer exists. >>> (gdb) quit >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> gnome-accessibility-list mailing list >>> gnome-accessibility-list at gnome.org >>> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list >>> >>> >> _______________________________________________ >> gnome-accessibility-list mailing list >> gnome-accessibility-list at gnome.org >> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list >> > > _______________________________________________ > gnome-accessibility-list mailing list > gnome-accessibility-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list > From kb8aey at verizon.net Wed Jan 10 20:19:24 2007 From: kb8aey at verizon.net (mike coulombe) Date: Wed, 10 Jan 2007 14:19:24 -0600 (CST) Subject: need a litle information Message-ID: <0JBO005S25SBOE04@vms046.mailsrvcs.net> Hi, some time ago someone on this list told me how the installer could be run from terminal. I was never able to get that to work, but I now have a different computer to try with feisty. I would like to get that info again if I can so I can see if it will work now. Mike. From alpuzz at gmail.com Sat Jan 13 04:01:24 2007 From: alpuzz at gmail.com (Al Puzzuoli) Date: Fri, 12 Jan 2007 23:01:24 -0500 Subject: Speakup on alternative install cd? Message-ID: <001d01c736c7$7e975ff0$6901a8c0@thinkpad> Hi, Just wondering whether it is currently possible to use Speakup to access the alternative install cd? I tried a Feisty disk from about a week ago; but if this functionality is there, I wasn't able to make it work. Thanks, --Al -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsd at clara.co.uk Sat Jan 13 16:50:24 2007 From: jsd at clara.co.uk (Jonathan Duddington) Date: Sat, 13 Jan 2007 16:50:24 +0000 (GMT) Subject: eSpeak v1.18 released, for use with Orca/GnomeSpeech Message-ID: <4ea4a2cf8bjsd@clara.co.uk> Version 1.18 of the eSpeak synthesizer is now available at: http://espeak.sourceforge.net/ This version includes changes made by Gilles Casse which allow it to be used with a GnomeSpeech driver which he has written. This should give better results when using eSpeak with Orca and other Gnome applications. I'm not sure whether Gilles has announced his GnomeSpeech driver for eSpeak yet. He may be waiting for me announce this 1.18 version first. Please report any problems, in case there is time to fix them before the cut-off date for Ubuntu Feisty. From alpuzz at gmail.com Sat Jan 13 22:09:46 2007 From: alpuzz at gmail.com (Al Puzzuoli) Date: Sat, 13 Jan 2007 17:09:46 -0500 Subject: getting the gnome-speech eSpeak driver to build? (was, eSpeak v1.18 released, for use with Orca/GnomeSpeech) References: <4ea4a2cf8bjsd@clara.co.uk> Message-ID: <000a01c7375f$8a5efc10$6901a8c0@thinkpad> Hi all, First of all, many, many thanks to both Gilles Casse and Jonathan Duddington for making this happen! Is there a parameter that needs to be passed to the autogen script to cause the Espeak driver to be built, or should the presence of Espeak be autodetected by gnome-speech? I think I have Espeak 1.8 installed correctly, as I'm able to get it to speak system wide when I issue the espeak command; However, the gnome-speech driver is not being built. Thanks in advance for any tips, --Al ----- Original Message ----- From: "Jonathan Duddington" To: Sent: Saturday, January 13, 2007 11:50 AM Subject: eSpeak v1.18 released, for use with Orca/GnomeSpeech > Version 1.18 of the eSpeak synthesizer is now available at: > http://espeak.sourceforge.net/ > > This version includes changes made by Gilles Casse which allow it to be > used with a GnomeSpeech driver which he has written. This should give > better results when using eSpeak with Orca and other Gnome applications. > > I'm not sure whether Gilles has announced his GnomeSpeech driver for > eSpeak yet. He may be waiting for me announce this 1.18 version first. > > Please report any problems, in case there is time to fix them before > the cut-off date for Ubuntu Feisty. > > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility From gcasse at oralux.org Sat Jan 13 23:17:38 2007 From: gcasse at oralux.org (Gilles Casse) Date: Sun, 14 Jan 2007 00:17:38 +0100 Subject: getting the gnome-speech eSpeak driver to build? (was, eSpeak v1.18 released, for use with Orca/GnomeSpeech) In-Reply-To: <000a01c7375f$8a5efc10$6901a8c0@thinkpad> References: <4ea4a2cf8bjsd@clara.co.uk> <000a01c7375f$8a5efc10$6901a8c0@thinkpad> Message-ID: <17833.26770.164404.403946@gargle.gargle.HOWL> Hello, Al Puzzuoli writes: > Is there a parameter that needs to be passed to the autogen script to cause > the Espeak driver to be built, or should the presence of Espeak be > autodetected by gnome-speech? > In principle, espeak might be auto-detected. If the libespeak is not yet known by the system, running ldconfig as root might help. Best regards, Gilles -- Oralux http://oralux.org From William.Walker at Sun.COM Sun Jan 14 00:19:58 2007 From: William.Walker at Sun.COM (Willie Walker) Date: Sat, 13 Jan 2007 19:19:58 -0500 Subject: getting the gnome-speech eSpeak driver to build? (was, eSpeak v1.18 released, for use with Orca/GnomeSpeech) In-Reply-To: <000a01c7375f$8a5efc10$6901a8c0@thinkpad> References: <4ea4a2cf8bjsd@clara.co.uk> <000a01c7375f$8a5efc10$6901a8c0@thinkpad> Message-ID: <1168733998.21939.43.camel@ubuntu> Hi Al: I put Gilles's gnome-speech driver in the gnome-speech SVN trunk, and I'll do a gnome-speech 0.4.8 release with it for GNOME 2.17.90 (GNOME 2.18.0 Beta 1) a week from tomorrow. If people can give this a try before Friday and let me know of successes or issues, it would be great. Here's what I did to get it to work - it took about 15 minutes: DOWNLOAD/INSTALL ESPEAK: Download espeak-1.18-linux.zip from http://espeak.sourceforge.net/ and unzip it. Type these commands to get the espeak stuff in well-known locations: cd espeak-1.18-linux sudo cp -rp espeak-data /usr/share/ sudo cp shared_library/libespeak.so.1.1.18 /usr/lib/ sudo cp shared_library/speak_lib.h /usr/include/ sudo ldconfig BUILD/INSTALL THE GNOME-SPEECH DRIVER FOR ESPEAK: In the top-level gnome-speech source directory, type these commands to build/install gnome-speech with espeak (assuming you've pulled the gnome-speech from svn at revision 267 or greater, though 267 currently is the highest revision right now): ./autogen --prefix=/usr make sudo make install I also ran test-speech to make sure it worked - it did. Gilles made this really easy for me to integrate into gnome-speech. Thanks very much Gilles, and thanks very much Jonathan for creating eSpeak and for being receptive of Gilles's mods. Note that the gnome-speech driver depends upon the libespeech library, which has a dependency on libportaudio0. I already had libportaudio0 installed on my Ubuntu box, so I didn't run into any issues. Hope this helps, and thanks again everyone. Will On Sat, 2007-01-13 at 17:09 -0500, Al Puzzuoli wrote: > Hi all, > > First of all, many, many thanks to both Gilles Casse and Jonathan > Duddington for making this happen! > > Is there a parameter that needs to be passed to the autogen script to cause > the Espeak driver to be built, or should the presence of Espeak be > autodetected by gnome-speech? > > I think I have Espeak 1.8 installed correctly, as I'm able to get it to > speak system wide when I issue the espeak command; However, the gnome-speech > driver is not being built. > > Thanks in advance for any tips, > > --Al > > > > > > ----- Original Message ----- > From: "Jonathan Duddington" > To: > Sent: Saturday, January 13, 2007 11:50 AM > Subject: eSpeak v1.18 released, for use with Orca/GnomeSpeech > > > > Version 1.18 of the eSpeak synthesizer is now available at: > > http://espeak.sourceforge.net/ > > > > This version includes changes made by Gilles Casse which allow it to be > > used with a GnomeSpeech driver which he has written. This should give > > better results when using eSpeak with Orca and other Gnome applications. > > > > I'm not sure whether Gilles has announced his GnomeSpeech driver for > > eSpeak yet. He may be waiting for me announce this 1.18 version first. > > > > Please report any problems, in case there is time to fix them before > > the cut-off date for Ubuntu Feisty. > > > > > > -- > > Ubuntu-accessibility mailing list > > Ubuntu-accessibility at lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > > From alpuzz at gmail.com Sun Jan 14 01:08:38 2007 From: alpuzz at gmail.com (Al Puzzuoli) Date: Sat, 13 Jan 2007 20:08:38 -0500 Subject: getting the gnome-speech eSpeak driver to build? (was, eSpeak v1.18 released, for use with Orca/GnomeSpeech) References: <4ea4a2cf8bjsd@clara.co.uk> <000a01c7375f$8a5efc10$6901a8c0@thinkpad> <1168733998.21939.43.camel@ubuntu> Message-ID: <001201c73778$86c996f0$6901a8c0@thinkpad> Hi Will, Thanks a lot for this. i've managed to get it up and running, and I must say, the performance of the synthesizer is great! An interesting note. In order to get my setup working, I had to deviate slightly from the process you described. I found that before the driver would build, I needed to create two symbolic links from /usr/lib/libespeak.so.1.1.18: /usr/lib/libespeak.so, and /usr/lib/libespeak.so.1. I'm not sure how to account for that discrepancy; but for now, I'm just happy that it's working. --Al ----- Original Message ----- From: "Willie Walker" To: "Al Puzzuoli" Cc: "Jonathan Duddington" ; ; "Orca List" Sent: Saturday, January 13, 2007 7:19 PM Subject: Re: getting the gnome-speech eSpeak driver to build? (was, eSpeak v1.18 released, for use with Orca/GnomeSpeech) > Hi Al: > > I put Gilles's gnome-speech driver in the gnome-speech SVN trunk, and > I'll do a gnome-speech 0.4.8 release with it for GNOME 2.17.90 (GNOME > 2.18.0 Beta 1) a week from tomorrow. If people can give this a try > before Friday and let me know of successes or issues, it would be great. > > Here's what I did to get it to work - it took about 15 minutes: > > DOWNLOAD/INSTALL ESPEAK: > > Download espeak-1.18-linux.zip from http://espeak.sourceforge.net/ and > unzip it. > > Type these commands to get the espeak stuff in well-known locations: > > cd espeak-1.18-linux > sudo cp -rp espeak-data /usr/share/ > sudo cp shared_library/libespeak.so.1.1.18 /usr/lib/ > sudo cp shared_library/speak_lib.h /usr/include/ > sudo ldconfig > > BUILD/INSTALL THE GNOME-SPEECH DRIVER FOR ESPEAK: > > In the top-level gnome-speech source directory, type these commands to > build/install gnome-speech with espeak (assuming you've pulled the > gnome-speech from svn at revision 267 or greater, though 267 currently > is the highest revision right now): > > ./autogen --prefix=/usr > make > sudo make install > > I also ran test-speech to make sure it worked - it did. Gilles made > this really easy for me to integrate into gnome-speech. Thanks very > much Gilles, and thanks very much Jonathan for creating eSpeak and for > being receptive of Gilles's mods. > > Note that the gnome-speech driver depends upon the libespeech library, > which has a dependency on libportaudio0. I already had libportaudio0 > installed on my Ubuntu box, so I didn't run into any issues. > > Hope this helps, and thanks again everyone. > > Will > > On Sat, 2007-01-13 at 17:09 -0500, Al Puzzuoli wrote: >> Hi all, >> >> First of all, many, many thanks to both Gilles Casse and Jonathan >> Duddington for making this happen! >> >> Is there a parameter that needs to be passed to the autogen script to >> cause >> the Espeak driver to be built, or should the presence of Espeak be >> autodetected by gnome-speech? >> >> I think I have Espeak 1.8 installed correctly, as I'm able to get it to >> speak system wide when I issue the espeak command; However, the >> gnome-speech >> driver is not being built. >> >> Thanks in advance for any tips, >> >> --Al >> >> >> >> >> >> ----- Original Message ----- >> From: "Jonathan Duddington" >> To: >> Sent: Saturday, January 13, 2007 11:50 AM >> Subject: eSpeak v1.18 released, for use with Orca/GnomeSpeech >> >> >> > Version 1.18 of the eSpeak synthesizer is now available at: >> > http://espeak.sourceforge.net/ >> > >> > This version includes changes made by Gilles Casse which allow it to be >> > used with a GnomeSpeech driver which he has written. This should give >> > better results when using eSpeak with Orca and other Gnome >> > applications. >> > >> > I'm not sure whether Gilles has announced his GnomeSpeech driver for >> > eSpeak yet. He may be waiting for me announce this 1.18 version first. >> > >> > Please report any problems, in case there is time to fix them before >> > the cut-off date for Ubuntu Feisty. >> > >> > >> > -- >> > Ubuntu-accessibility mailing list >> > Ubuntu-accessibility at lists.ubuntu.com >> > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility >> >> > From j-diggs at comcast.net Sun Jan 14 18:21:07 2007 From: j-diggs at comcast.net (Joanmarie Diggs) Date: Sun, 14 Jan 2007 13:21:07 -0500 Subject: getting the gnome-speech eSpeak driver to build? (was, eSpeak v1.18 released, for use with Orca/GnomeSpeech) In-Reply-To: <001201c73778$86c996f0$6901a8c0@thinkpad> References: <4ea4a2cf8bjsd@clara.co.uk> <000a01c7375f$8a5efc10$6901a8c0@thinkpad> <1168733998.21939.43.camel@ubuntu> <001201c73778$86c996f0$6901a8c0@thinkpad> Message-ID: <1168798867.5472.0.camel@pokey> Hi Al. I had to do something similar: my /usr/lib/libespeak.so.1 pointed to /usr/lib/libespeak.so.1.1.18, but /usr/lib/libespeak.so pointed to /usr/lib/libespeak.so.1.1.15. Once I changed that, I was able to build gnome-speech (prior to that, make exits with an error). While there are lots of voices listed both in test-speech and in Orca, I seem to be limited to just one. I see them all in /usr/share/espeak-data/voices. How do I use them? Take care. Joanie On Sat, 2007-01-13 at 20:08 -0500, Al Puzzuoli wrote: > Hi Will, > > Thanks a lot for this. i've managed to get it up and running, and I must > say, the performance of the synthesizer is great! > > An interesting note. In order to get my setup working, I had to deviate > slightly from the process you described. I found that before the driver > would build, I needed to create two symbolic links from > /usr/lib/libespeak.so.1.1.18: /usr/lib/libespeak.so, and > /usr/lib/libespeak.so.1. I'm not sure how to account for that discrepancy; > but for now, I'm just happy that it's working. > > --Al > > > > > ----- Original Message ----- > From: "Willie Walker" > To: "Al Puzzuoli" > Cc: "Jonathan Duddington" ; > ; "Orca List" > Sent: Saturday, January 13, 2007 7:19 PM > Subject: Re: getting the gnome-speech eSpeak driver to build? (was, eSpeak > v1.18 released, for use with Orca/GnomeSpeech) > > > > Hi Al: > > > > I put Gilles's gnome-speech driver in the gnome-speech SVN trunk, and > > I'll do a gnome-speech 0.4.8 release with it for GNOME 2.17.90 (GNOME > > 2.18.0 Beta 1) a week from tomorrow. If people can give this a try > > before Friday and let me know of successes or issues, it would be great. > > > > Here's what I did to get it to work - it took about 15 minutes: > > > > DOWNLOAD/INSTALL ESPEAK: > > > > Download espeak-1.18-linux.zip from http://espeak.sourceforge.net/ and > > unzip it. > > > > Type these commands to get the espeak stuff in well-known locations: > > > > cd espeak-1.18-linux > > sudo cp -rp espeak-data /usr/share/ > > sudo cp shared_library/libespeak.so.1.1.18 /usr/lib/ > > sudo cp shared_library/speak_lib.h /usr/include/ > > sudo ldconfig > > > > BUILD/INSTALL THE GNOME-SPEECH DRIVER FOR ESPEAK: > > > > In the top-level gnome-speech source directory, type these commands to > > build/install gnome-speech with espeak (assuming you've pulled the > > gnome-speech from svn at revision 267 or greater, though 267 currently > > is the highest revision right now): > > > > ./autogen --prefix=/usr > > make > > sudo make install > > > > I also ran test-speech to make sure it worked - it did. Gilles made > > this really easy for me to integrate into gnome-speech. Thanks very > > much Gilles, and thanks very much Jonathan for creating eSpeak and for > > being receptive of Gilles's mods. > > > > Note that the gnome-speech driver depends upon the libespeech library, > > which has a dependency on libportaudio0. I already had libportaudio0 > > installed on my Ubuntu box, so I didn't run into any issues. > > > > Hope this helps, and thanks again everyone. > > > > Will > > > > On Sat, 2007-01-13 at 17:09 -0500, Al Puzzuoli wrote: > >> Hi all, > >> > >> First of all, many, many thanks to both Gilles Casse and Jonathan > >> Duddington for making this happen! > >> > >> Is there a parameter that needs to be passed to the autogen script to > >> cause > >> the Espeak driver to be built, or should the presence of Espeak be > >> autodetected by gnome-speech? > >> > >> I think I have Espeak 1.8 installed correctly, as I'm able to get it to > >> speak system wide when I issue the espeak command; However, the > >> gnome-speech > >> driver is not being built. > >> > >> Thanks in advance for any tips, > >> > >> --Al > >> > >> > >> > >> > >> > >> ----- Original Message ----- > >> From: "Jonathan Duddington" > >> To: > >> Sent: Saturday, January 13, 2007 11:50 AM > >> Subject: eSpeak v1.18 released, for use with Orca/GnomeSpeech > >> > >> > >> > Version 1.18 of the eSpeak synthesizer is now available at: > >> > http://espeak.sourceforge.net/ > >> > > >> > This version includes changes made by Gilles Casse which allow it to be > >> > used with a GnomeSpeech driver which he has written. This should give > >> > better results when using eSpeak with Orca and other Gnome > >> > applications. > >> > > >> > I'm not sure whether Gilles has announced his GnomeSpeech driver for > >> > eSpeak yet. He may be waiting for me announce this 1.18 version first. > >> > > >> > Please report any problems, in case there is time to fix them before > >> > the cut-off date for Ubuntu Feisty. > >> > > >> > > >> > -- > >> > Ubuntu-accessibility mailing list > >> > Ubuntu-accessibility at lists.ubuntu.com > >> > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > >> > >> > > > > From kb8aey at verizon.net Sun Jan 14 19:07:22 2007 From: kb8aey at verizon.net (mike coulombe) Date: Sun, 14 Jan 2007 13:07:22 -0600 (CST) Subject: is the installer broken Message-ID: <0JBV007KLH49WY4I@vms044.mailsrvcs.net> Hi, I downloaded the latest live CD of feisty. The installer doesn't work at all from the desktop. I had a sighted person look and they said it appears to not start. I downloaded one of these discs a few days ago and had another problem. The installer worked up to the point of picking a keyboard. After that everything on the screen got very large and it crashed. Has anyone else experienced problems with the installer over the past few days. Now for some good news, I notice I can now see all partitions on my computer using the live CD. It also looks like all settings have been put in to a control center. Mike. From alpuzz at gmail.com Sun Jan 14 20:46:41 2007 From: alpuzz at gmail.com (Al Puzzuoli) Date: Sun, 14 Jan 2007 15:46:41 -0500 Subject: getting the gnome-speech eSpeak driver to build? (was, eSpeak v1.18 released, for use with Orca/GnomeSpeech) References: <4ea4a2cf8bjsd@clara.co.uk> <000a01c7375f$8a5efc10$6901a8c0@thinkpad> <1168733998.21939.43.camel@ubuntu> <001201c73778$86c996f0$6901a8c0@thinkpad> <1168798867.5472.0.camel@pokey> Message-ID: <000701c7381d$19210570$6901a8c0@thinkpad> Hey Joanie, I'm seeing the same thing. I have a number of voices listed in test-speech as well as in the Orca person dropdown; However,selecting any of these seems to have no affect. On a somewhat related note, have you tried compiling Espeak under Ubuntu for PPC? When attempting to do so, I'm getting an error during the make, having to do with the inability to find lespeak. It's as if the compile depends on the presence of libespeak, but I don't see how to compile libespeak first. --Al ----- Original Message ----- From: "Joanmarie Diggs" To: "Al Puzzuoli" Cc: "Ubuntu Accessibility Mailing List" Sent: Sunday, January 14, 2007 1:21 PM Subject: Re: getting the gnome-speech eSpeak driver to build? (was,eSpeak v1.18 released, for use with Orca/GnomeSpeech) > Hi Al. > > I had to do something similar: my /usr/lib/libespeak.so.1 pointed > to /usr/lib/libespeak.so.1.1.18, but /usr/lib/libespeak.so pointed > to /usr/lib/libespeak.so.1.1.15. Once I changed that, I was able to > build gnome-speech (prior to that, make exits with an error). > > While there are lots of voices listed both in test-speech and in Orca, I > seem to be limited to just one. I see them all > in /usr/share/espeak-data/voices. How do I use them? > > Take care. > Joanie > > On Sat, 2007-01-13 at 20:08 -0500, Al Puzzuoli wrote: >> Hi Will, >> >> Thanks a lot for this. i've managed to get it up and running, and I must >> say, the performance of the synthesizer is great! >> >> An interesting note. In order to get my setup working, I had to deviate >> slightly from the process you described. I found that before the driver >> would build, I needed to create two symbolic links from >> /usr/lib/libespeak.so.1.1.18: /usr/lib/libespeak.so, and >> /usr/lib/libespeak.so.1. I'm not sure how to account for that >> discrepancy; >> but for now, I'm just happy that it's working. >> >> --Al >> >> >> >> >> ----- Original Message ----- >> From: "Willie Walker" >> To: "Al Puzzuoli" >> Cc: "Jonathan Duddington" ; >> ; "Orca List" >> >> Sent: Saturday, January 13, 2007 7:19 PM >> Subject: Re: getting the gnome-speech eSpeak driver to build? (was, >> eSpeak >> v1.18 released, for use with Orca/GnomeSpeech) >> >> >> > Hi Al: >> > >> > I put Gilles's gnome-speech driver in the gnome-speech SVN trunk, and >> > I'll do a gnome-speech 0.4.8 release with it for GNOME 2.17.90 (GNOME >> > 2.18.0 Beta 1) a week from tomorrow. If people can give this a try >> > before Friday and let me know of successes or issues, it would be >> > great. >> > >> > Here's what I did to get it to work - it took about 15 minutes: >> > >> > DOWNLOAD/INSTALL ESPEAK: >> > >> > Download espeak-1.18-linux.zip from http://espeak.sourceforge.net/ and >> > unzip it. >> > >> > Type these commands to get the espeak stuff in well-known locations: >> > >> > cd espeak-1.18-linux >> > sudo cp -rp espeak-data /usr/share/ >> > sudo cp shared_library/libespeak.so.1.1.18 /usr/lib/ >> > sudo cp shared_library/speak_lib.h /usr/include/ >> > sudo ldconfig >> > >> > BUILD/INSTALL THE GNOME-SPEECH DRIVER FOR ESPEAK: >> > >> > In the top-level gnome-speech source directory, type these commands to >> > build/install gnome-speech with espeak (assuming you've pulled the >> > gnome-speech from svn at revision 267 or greater, though 267 currently >> > is the highest revision right now): >> > >> > ./autogen --prefix=/usr >> > make >> > sudo make install >> > >> > I also ran test-speech to make sure it worked - it did. Gilles made >> > this really easy for me to integrate into gnome-speech. Thanks very >> > much Gilles, and thanks very much Jonathan for creating eSpeak and for >> > being receptive of Gilles's mods. >> > >> > Note that the gnome-speech driver depends upon the libespeech library, >> > which has a dependency on libportaudio0. I already had libportaudio0 >> > installed on my Ubuntu box, so I didn't run into any issues. >> > >> > Hope this helps, and thanks again everyone. >> > >> > Will >> > >> > On Sat, 2007-01-13 at 17:09 -0500, Al Puzzuoli wrote: >> >> Hi all, >> >> >> >> First of all, many, many thanks to both Gilles Casse and Jonathan >> >> Duddington for making this happen! >> >> >> >> Is there a parameter that needs to be passed to the autogen script to >> >> cause >> >> the Espeak driver to be built, or should the presence of Espeak be >> >> autodetected by gnome-speech? >> >> >> >> I think I have Espeak 1.8 installed correctly, as I'm able to get it >> >> to >> >> speak system wide when I issue the espeak command; However, the >> >> gnome-speech >> >> driver is not being built. >> >> >> >> Thanks in advance for any tips, >> >> >> >> --Al >> >> >> >> >> >> >> >> >> >> >> >> ----- Original Message ----- >> >> From: "Jonathan Duddington" >> >> To: >> >> Sent: Saturday, January 13, 2007 11:50 AM >> >> Subject: eSpeak v1.18 released, for use with Orca/GnomeSpeech >> >> >> >> >> >> > Version 1.18 of the eSpeak synthesizer is now available at: >> >> > http://espeak.sourceforge.net/ >> >> > >> >> > This version includes changes made by Gilles Casse which allow it to >> >> > be >> >> > used with a GnomeSpeech driver which he has written. This should >> >> > give >> >> > better results when using eSpeak with Orca and other Gnome >> >> > applications. >> >> > >> >> > I'm not sure whether Gilles has announced his GnomeSpeech driver for >> >> > eSpeak yet. He may be waiting for me announce this 1.18 version >> >> > first. >> >> > >> >> > Please report any problems, in case there is time to fix them before >> >> > the cut-off date for Ubuntu Feisty. >> >> > >> >> > >> >> > -- >> >> > Ubuntu-accessibility mailing list >> >> > Ubuntu-accessibility at lists.ubuntu.com >> >> > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility >> >> >> >> >> > >> >> > From alpuzz at gmail.com Sun Jan 14 21:03:12 2007 From: alpuzz at gmail.com (Al Puzzuoli) Date: Sun, 14 Jan 2007 16:03:12 -0500 Subject: Accessibility of gnome-controlcenter? Message-ID: <000e01c7381f$6801ab70$6901a8c0@thinkpad> Hi all, I've noticed that by default in Feisty, the administration menu seems to be gone, and all of the functions it contained can now be accessed via the gnome-control-center. My concern is that unless I'm missing something, there doesn't seem to be a way to navigate the control-center UI efficiently via the keyboard. Granted, it is possible to tab to, and then press enter on each function's corresponding button; However, I don't see any way of quickly jumping to a desired function. As an example, under administration, if I wanted to get to the sound preferences, I could do so relatively quickly by pressing S a couple of times. Are there plans to implement first letter navigation into the control-center's UI? If this isn't going to happen any time soon, is there an option somewhere to easily restore the administration menu? Thanks, --Al From j-diggs at comcast.net Sun Jan 14 21:09:38 2007 From: j-diggs at comcast.net (Joanmarie Diggs) Date: Sun, 14 Jan 2007 16:09:38 -0500 Subject: Accessibility of gnome-controlcenter? In-Reply-To: <000e01c7381f$6801ab70$6901a8c0@thinkpad> References: <000e01c7381f$6801ab70$6901a8c0@thinkpad> Message-ID: <1168808978.31156.1.camel@blockhead> There is a filter text box. It seems to gain focus automatically when the Control Center window is first opened. So type "sound" and then tab to the sounds button. On Sun, 2007-01-14 at 16:03 -0500, Al Puzzuoli wrote: > Hi all, > > I've noticed that by default in Feisty, the administration menu seems to be > gone, and all of the functions it contained can now be accessed via the > gnome-control-center. My concern is that unless I'm missing something, > there doesn't seem to be a way to navigate the control-center UI efficiently > via the keyboard. Granted, it is possible to tab to, and then press enter > on each function's corresponding button; However, I don't see any way of > quickly jumping to a desired function. As an example, under administration, > if I wanted to get to the sound preferences, I could do so relatively > quickly by pressing S a couple of times. Are there plans to implement first > letter navigation into the control-center's UI? If this isn't going to > happen any time soon, is there an option somewhere to easily restore the > administration menu? > > Thanks, > > --Al > > > _______________________________________________ > gnome-accessibility-list mailing list > gnome-accessibility-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list From henrik at ubuntu.com Sun Jan 14 21:16:20 2007 From: henrik at ubuntu.com (Henrik Nilsen Omma) Date: Sun, 14 Jan 2007 22:16:20 +0100 Subject: Accessibility of gnome-controlcenter? In-Reply-To: <000e01c7381f$6801ab70$6901a8c0@thinkpad> References: <000e01c7381f$6801ab70$6901a8c0@thinkpad> Message-ID: <45AA9DA4.6090105@ubuntu.com> Al Puzzuoli wrote: > Hi all, > > I've noticed that by default in Feisty, the administration menu seems to be > gone, and all of the functions it contained can now be accessed via the > gnome-control-center. My concern is that unless I'm missing something, > there doesn't seem to be a way to navigate the control-center UI efficiently > via the keyboard. Granted, it is possible to tab to, and then press enter > on each function's corresponding button; However, I don't see any way of > quickly jumping to a desired function. As an example, under administration, > if I wanted to get to the sound preferences, I could do so relatively > quickly by pressing S a couple of times. Are there plans to implement first > letter navigation into the control-center's UI? If this isn't going to > happen any time soon, is there an option somewhere to easily restore the > administration menu? > The new control centre resembles the control panel in Windows, which does respond to first-letter-pressing as you describe. I think we should pursue that option. Only trouble is that the items are sorted by category first, then alphabetically (is that a problem? the selection could skip through categories). Henrik From jsd at clara.co.uk Sun Jan 14 21:57:11 2007 From: jsd at clara.co.uk (Jonathan Duddington) Date: Sun, 14 Jan 2007 21:57:11 +0000 (GMT) Subject: getting the gnome-speech eSpeak driver to build? (was, eSpeak v1.18 released, for use with Orca/GnomeSpeech) In-Reply-To: <000701c7381d$19210570$6901a8c0@thinkpad> References: <4ea4a2cf8bjsd@clara.co.uk> <000a01c7375f$8a5efc10$6901a8c0@thinkpad> <1168733998.21939.43.camel@ubuntu> <001201c73778$86c996f0$6901a8c0@thinkpad> <1168798867.5472.0.camel@pokey> <000701c7381d$19210570$6901a8c0@thinkpad> Message-ID: <4ea542bba9jsd@clara.co.uk> In article <000701c7381d$19210570$6901a8c0 at thinkpad>, Al Puzzuoli wrote: > On a somewhat related note, have you tried compiling Espeak under > Ubuntu for PPC? When attempting to do so, I'm getting an error > during the make, having to do with the inability to find lespeak. > It's as if the compile depends on the presence of libespeak, but I > don't see how to compile libespeak first. Yes, compiling "espeak" needs the "libespeak" to be present in /usr/lib. But "make" should have compiled libespeak.so.1.18 OK. So install that in /usr/lib and do "sudo ldconfig" (I think that creates the link from /usr/lib/libespeak.so.1 to /usr/lib/libespeak.so.1.18.0). Then if you run "make" again, it should compile "espeak" OK. Perhaps there is a way of making the makefile do that automatically? From jsd at clara.co.uk Mon Jan 15 01:10:49 2007 From: jsd at clara.co.uk (Jonathan Duddington) Date: Mon, 15 Jan 2007 01:10:49 +0000 (GMT) Subject: getting the gnome-speech eSpeak driver to build? (was, eSpeak v1.18 released, for use with Orca/GnomeSpeech) In-Reply-To: <4ea542bba9jsd@clara.co.uk> References: <4ea4a2cf8bjsd@clara.co.uk> <000a01c7375f$8a5efc10$6901a8c0@thinkpad> <1168733998.21939.43.camel@ubuntu> <001201c73778$86c996f0$6901a8c0@thinkpad> <1168798867.5472.0.camel@pokey> <000701c7381d$19210570$6901a8c0@thinkpad> <4ea542bba9jsd@clara.co.uk> Message-ID: In article <4ea542bba9jsd at clara.co.uk>, Jonathan Duddington wrote: > Perhaps there is a way of making the makefile do that automatically? Following a suggestion from Gilles, here's a revised makefile that should compile all three: speak, libespeak.so.1.1.18, and espeak. Also, if you then do: sudo make install then it should put libespeak and its links into /usr/lib and put espeak into /usr/bin. -------------- next part -------------- A non-text attachment was scrubbed... Name: Makefile Type: application/octet-stream Size: 2313 bytes Desc: not available URL: From themuso at themuso.com Mon Jan 15 01:22:49 2007 From: themuso at themuso.com (Luke Yelavich) Date: Mon, 15 Jan 2007 12:22:49 +1100 Subject: getting the gnome-speech eSpeak driver to build? (was, eSpeak v1.18 released, for use with Orca/GnomeSpeech) In-Reply-To: References: <4ea4a2cf8bjsd@clara.co.uk> <000a01c7375f$8a5efc10$6901a8c0@thinkpad> <1168733998.21939.43.camel@ubuntu> <001201c73778$86c996f0$6901a8c0@thinkpad> <1168798867.5472.0.camel@pokey> <000701c7381d$19210570$6901a8c0@thinkpad> <4ea542bba9jsd@clara.co.uk> Message-ID: <20070115012249.GA6133@themuso.com> On Mon, Jan 15, 2007 at 12:10:49PM EST, Jonathan Duddington wrote: > In article <4ea542bba9jsd at clara.co.uk>, > Jonathan Duddington wrote: > > > Perhaps there is a way of making the makefile do that automatically? > > Following a suggestion from Gilles, here's a revised makefile that > should compile all three: speak, libespeak.so.1.1.18, and espeak. > > Also, if you then do: > sudo make install > > then it should put libespeak and its links into /usr/lib and put espeak > into /usr/bin. I will get to espeak sometime this week, probably while I am itting in a talk at LCA07. :) We also need to work out what we are going to do regarding espeak and getting a gnome-speech driver built, and included in Main. I'll probably chat to Henrik tonight about this. -- Luke Yelavich GPG key: 0xD06320CE (http://www.themuso.com/themuso-gpg-key.txt) Email & MSN: themuso at themuso.com Jabber: themuso at jabber.org.au -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From alpuzz at gmail.com Mon Jan 15 01:46:49 2007 From: alpuzz at gmail.com (Al Puzzuoli) Date: Sun, 14 Jan 2007 20:46:49 -0500 Subject: getting the gnome-speech eSpeak driver to build? (was, eSpeak v1.18 released, for use with Orca/GnomeSpeech) References: <4ea4a2cf8bjsd@clara.co.uk><000a01c7375f$8a5efc10$6901a8c0@thinkpad><1168733998.21939.43.camel@ubuntu><001201c73778$86c996f0$6901a8c0@thinkpad><1168798867.5472.0.camel@pokey><000701c7381d$19210570$6901a8c0@thinkpad> <4ea542bba9jsd@clara.co.uk> Message-ID: <003501c73847$0652ed80$6901a8c0@thinkpad> Hi Jonathan, Thanks very much for this! The good news is that the new makefile did exactly what it was supposed to do, and after a make, make install, I got everything compiled and put where it should go. However, at least on the PPC architecture, there appears to still be a problem. If I attempt to test Espeak via the command line, I get the following; Bad data: '/usr/share/espeak-data/en_dict'. This was actually happening to me before I upgraded to 1.18, and I was hoping that building the new version would resolve the issue. I completely removed the /usr/share/espeak-data directory, and let the make install recreate it; However, the error still persists. I have an I386 machine, and on that machine, I've tested both Espeak 1.5, as well as the newer 1.18, and neither exhibit this issue. --Al From jsd at clara.co.uk Mon Jan 15 02:11:07 2007 From: jsd at clara.co.uk (Jonathan Duddington) Date: Mon, 15 Jan 2007 02:11:07 +0000 (GMT) Subject: eSpeak - PPC architecture In-Reply-To: <003501c73847$0652ed80$6901a8c0@thinkpad> References: <4ea4a2cf8bjsd@clara.co.uk><000a01c7375f$8a5efc10$6901a8c0@thinkpad><1168733998.21939.43.camel@ubuntu><001201c73778$86c996f0$6901a8c0@thinkpad><1168798867.5472.0.camel@pokey><000701c7381d$19210570$6901a8c0@thinkpad> <4ea542bba9jsd@clara.co.uk> <003501c73847$0652ed80$6901a8c0@thinkpad> Message-ID: <4ea559fb55jsd@clara.co.uk> In article <003501c73847$0652ed80$6901a8c0 at thinkpad>, Al Puzzuoli wrote: > However, at least on the PPC architecture, there appears to still be > a problem. If I attempt to test Espeak via the command line, I get > the following; Bad data: '/usr/share/espeak-data/en_dict'. This was > actually happening to me before I upgraded to 1.18, and I was > hoping that building the new version would resolve the issue. Does PPC have different byte-ordering from i386? If so, it's possible that the data files are not binary compatible. Have you ever had eSpeak work on PPC, or know anyone who has? Delete the file /usr/share/espeak-data/en_dict file, and also make sure you don't have a directory espeak-data in your user's home directory. Then try re-compiling the dictionary data: espeak --compile=en Can it speak then? If the phoneme data (espeak-data/phondata,phonindex,phontab) is also incompatible, then that's a bigger problem. From jsd at clara.co.uk Mon Jan 15 02:42:28 2007 From: jsd at clara.co.uk (Jonathan Duddington) Date: Mon, 15 Jan 2007 02:42:28 +0000 (GMT) Subject: eSpeak - PPC architecture In-Reply-To: <4ea559fb55jsd@clara.co.uk> References: <4ea4a2cf8bjsd@clara.co.uk><000a01c7375f$8a5efc10$6901a8c0@thinkpad><1168733998.21939.43.camel@ubuntu><001201c73778$86c996f0$6901a8c0@thinkpad><1168798867.5472.0.camel@pokey><000701c7381d$19210570$6901a8c0@thinkpad> <4ea542bba9jsd@clara.co.uk> <003501c73847$0652ed80$6901a8c0@thinkpad> <4ea559fb55jsd@clara.co.uk> Message-ID: <4ea55cda0ejsd@clara.co.uk> In article <4ea559fb55jsd at clara.co.uk>, Jonathan Duddington wrote: > Delete the file /usr/share/espeak-data/en_dict file, and also make > sure you don't have a directory espeak-data in your user's home > directory. ... because it will use the espeak-data in the user's home directory in preference to /usr/share > Then try re-compiling the dictionary data: > espeak --compile=en I should have said, first go into the dictsource directory, which contains the en_rules and en_list files. It compiles en_rules and en_list to make espeak-data/en_dict. > Can it speak then? > If the phoneme data (espeak-data/phondata,phonindex,phontab) is also > incompatible, then that's a bigger problem. If so, you will need espeakedit running on PPC to be able to compile the phoneme data. Which means you need a port of the espeakedit program to PPC. From alpuzz at gmail.com Mon Jan 15 03:12:26 2007 From: alpuzz at gmail.com (Al Puzzuoli) Date: Sun, 14 Jan 2007 22:12:26 -0500 Subject: eSpeak - PPC architecture References: <4ea4a2cf8bjsd@clara.co.uk><000a01c7375f$8a5efc10$6901a8c0@thinkpad><1168733998.21939.43.camel@ubuntu><001201c73778$86c996f0$6901a8c0@thinkpad><1168798867.5472.0.camel@pokey><000701c7381d$19210570$6901a8c0@thinkpad><4ea542bba9jsd@clara.co.uk> <003501c73847$0652ed80$6901a8c0@thinkpad><4ea559fb55jsd@clara.co.uk> <4ea55cda0ejsd@clara.co.uk> Message-ID: <004a01c73852$fc833740$6901a8c0@thinkpad> Hi, After recompiling the dictionary data, I no longer get that error; However, still no speech. If I send a string to eSpeak, it just exits with no noticeable output. Does that suggest incompatible phoneme data? --Al ----- Original Message ----- From: "Jonathan Duddington" To: "Jonathan Duddington" ; Sent: Sunday, January 14, 2007 9:42 PM Subject: Re: eSpeak - PPC architecture > In article <4ea559fb55jsd at clara.co.uk>, > Jonathan Duddington wrote: > >> Delete the file /usr/share/espeak-data/en_dict file, and also make >> sure you don't have a directory espeak-data in your user's home >> directory. > > ... because it will use the espeak-data in the user's home directory in > preference to /usr/share > >> Then try re-compiling the dictionary data: >> espeak --compile=en > > I should have said, first go into the dictsource directory, which > contains the en_rules and en_list files. It compiles en_rules and > en_list to make espeak-data/en_dict. > >> Can it speak then? > >> If the phoneme data (espeak-data/phondata,phonindex,phontab) is also >> incompatible, then that's a bigger problem. > > If so, you will need espeakedit running on PPC to be able to compile > the phoneme data. Which means you need a port of the espeakedit > program to PPC. > > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility From jsd at clara.co.uk Mon Jan 15 09:06:40 2007 From: jsd at clara.co.uk (Jonathan Duddington) Date: Mon, 15 Jan 2007 09:06:40 +0000 (GMT) Subject: eSpeak - PPC architecture In-Reply-To: <004a01c73852$fc833740$6901a8c0@thinkpad> References: <4ea4a2cf8bjsd@clara.co.uk><000a01c7375f$8a5efc10$6901a8c0@thinkpad><1168733998.21939.43.camel@ubuntu><001201c73778$86c996f0$6901a8c0@thinkpad><1168798867.5472.0.camel@pokey><000701c7381d$19210570$6901a8c0@thinkpad><4ea542bba9jsd@clara.co.uk> <003501c73847$0652ed80$6901a8c0@thinkpad><4ea559fb55jsd@clara.co.uk> <4ea55cda0ejsd@clara.co.uk> <004a01c73852$fc833740$6901a8c0@thinkpad> Message-ID: <4ea580068ejsd@clara.co.uk> In article <004a01c73852$fc833740$6901a8c0 at thinkpad>, Al Puzzuoli wrote: > After recompiling the dictionary data, I no longer get that error; > However, still no speech. If I send a string to eSpeak, it just > exits with no noticeable output. > Does that suggest incompatible phoneme data? I'm not sure. What text output do you get if you use the -x option, eg: espeak -x "hello" should give the phoneme codes: h at l'oU What happens if you send the speech output to a WAV file? Can you then play the WAV file later?, eg: espeak -w test.wav "hello" Do you know whether anyone has ever had eSpeak working on a similar PPC ? From gcasse at oralux.org Mon Jan 15 09:53:31 2007 From: gcasse at oralux.org (Gilles Casse) Date: Mon, 15 Jan 2007 10:53:31 +0100 Subject: getting the gnome-speech eSpeak driver to build? (was, eSpeak v1.18 released, for use with Orca/GnomeSpeech) In-Reply-To: <1168798867.5472.0.camel@pokey> References: <4ea4a2cf8bjsd@clara.co.uk> <000a01c7375f$8a5efc10$6901a8c0@thinkpad> <1168733998.21939.43.camel@ubuntu> <001201c73778$86c996f0$6901a8c0@thinkpad> <1168798867.5472.0.camel@pokey> Message-ID: <17835.20251.548863.457327@gargle.gargle.HOWL> Hello, Joanmarie Diggs writes: > While there are lots of voices listed both in test-speech and in Orca, I > seem to be limited to just one. I see them all > in /usr/share/espeak-data/voices. How do I use them? > Sorry, this issue is fixed in release r268 of gnome-speech; thanks to Willie for his responsiveness. In principle, the numerous eSpeak languages are available now :-). Gilles -- Oralux http://oralux.org From Calum.Benson at Sun.COM Mon Jan 15 10:46:02 2007 From: Calum.Benson at Sun.COM (Calum Benson) Date: Mon, 15 Jan 2007 10:46:02 +0000 Subject: Accessibility of gnome-controlcenter? In-Reply-To: <000e01c7381f$6801ab70$6901a8c0@thinkpad> References: <000e01c7381f$6801ab70$6901a8c0@thinkpad> Message-ID: <1168857962.8976.7.camel@sr1-edub-04> On Sun, 2007-01-14 at 16:03 -0500, Al Puzzuoli wrote: > Hi all, > > I've noticed that by default in Feisty, the administration menu seems to be > gone, and all of the functions it contained can now be accessed via the > gnome-control-center. FWIW, this is a proposal for GNOME 2.18 that may or may not be adopted (although it looks like it will be). I've never been too keen on it, but assuming it gets in, I'm hopeful that it will still be possible to switch back to the more efficient, old-style menu access too. Cheeri, Calum. -- CALUM BENSON, Usability Engineer Sun Microsystems Ireland mailto:calum.benson at sun.com GNOME Desktop Group http://ie.sun.com +353 1 819 9771 Any opinions are personal and not necessarily those of Sun Microsystems From henrik at ubuntu.com Mon Jan 15 11:02:55 2007 From: henrik at ubuntu.com (Henrik Nilsen Omma) Date: Mon, 15 Jan 2007 12:02:55 +0100 Subject: Accessibility of gnome-controlcenter? In-Reply-To: <1168857962.8976.7.camel@sr1-edub-04> References: <000e01c7381f$6801ab70$6901a8c0@thinkpad> <1168857962.8976.7.camel@sr1-edub-04> Message-ID: <45AB5F5F.1010608@ubuntu.com> Calum Benson wrote: > On Sun, 2007-01-14 at 16:03 -0500, Al Puzzuoli wrote: > >> Hi all, >> >> I've noticed that by default in Feisty, the administration menu seems to be >> gone, and all of the functions it contained can now be accessed via the >> gnome-control-center. >> > > FWIW, this is a proposal for GNOME 2.18 that may or may not be adopted > (although it looks like it will be). I've never been too keen on it, > but assuming it gets in, I'm hopeful that it will still be possible to > switch back to the more efficient, old-style menu access too. > > Hm, I've seen this argumentation in other places too (from ubuntu forum users who prefer the old menu system). I think it's a bad idea for two reasons: * We cannot keep legacy approaches around forever. It will clutter the interface with options and clutter the code. If gnome decides on this option we should work to improve it (where needed) and not try to bring back the old IMHO. * We should never rely on the legacy solution to provide us with the accessibility features. It will always be less discoverable and may suddenly disappear. Making the new control centre accessible should not be that hard. Who can we contact about it? Henrik From Calum.Benson at Sun.COM Mon Jan 15 11:16:06 2007 From: Calum.Benson at Sun.COM (Calum Benson) Date: Mon, 15 Jan 2007 11:16:06 +0000 Subject: Accessibility of gnome-controlcenter? In-Reply-To: <45AB5F5F.1010608@ubuntu.com> References: <000e01c7381f$6801ab70$6901a8c0@thinkpad> <1168857962.8976.7.camel@sr1-edub-04> <45AB5F5F.1010608@ubuntu.com> Message-ID: <1168859766.8976.27.camel@sr1-edub-04> On Mon, 2007-01-15 at 12:02 +0100, Henrik Nilsen Omma wrote: > * We should never rely on the legacy solution to provide us with the > accessibility features. It will always be less discoverable and may > suddenly disappear. Indeed we shouldn't, but the menu system is more efficient for a lot of people without accessibility needs too, so I'm still against getting rid of it altogether. Both Windows XP (dunno about Vista) and Mac OS X allow menu access to individual control panels if desired, and it seems unlikely to me that we've done more user research than they have. Cheeri, Calum. -- CALUM BENSON, Usability Engineer Sun Microsystems Ireland mailto:calum.benson at sun.com GNOME Desktop Group http://ie.sun.com +353 1 819 9771 Any opinions are personal and not necessarily those of Sun Microsystems From kb8aey at verizon.net Mon Jan 15 18:19:26 2007 From: kb8aey at verizon.net (mike coulombe) Date: Mon, 15 Jan 2007 12:19:26 -0600 (CST) Subject: can't get the installer to work Message-ID: <0JBX00JR19KDNBG2@vms046.mailsrvcs.net> Hi, I downloaded another feisty CD to day. The installer starts to load and closes. Is there a problem with the installer at this time. If so can it be done from the terminal. Mike. From alpuzz at gmail.com Tue Jan 16 03:30:33 2007 From: alpuzz at gmail.com (Al Puzzuoli) Date: Mon, 15 Jan 2007 22:30:33 -0500 Subject: eSpeak - PPC architecture References: <4ea4a2cf8bjsd@clara.co.uk><000a01c7375f$8a5efc10$6901a8c0@thinkpad><1168733998.21939.43.camel@ubuntu><001201c73778$86c996f0$6901a8c0@thinkpad><1168798867.5472.0.camel@pokey><000701c7381d$19210570$6901a8c0@thinkpad><4ea542bba9jsd@clara.co.uk><003501c73847$0652ed80$6901a8c0@thinkpad><4ea559fb55jsd@clara.co.uk><4ea55cda0ejsd@clara.co.uk><004a01c73852$fc833740$6901a8c0@thinkpad> <4ea580068ejsd@clara.co.uk> Message-ID: <000701c7391e$aee95d80$6901a8c0@thinkpad> Hi Jonathan, I tried the experiments you suggested. 1.> What text output do you get if you use the -x option, eg: > espeak -x "hello"? Interestingly, I'm not getting any text at all. When I do this, I'm immediately dropped back to the shell with no output. 2. What happens if you send the speech output to a WAV file? Again, nothing useful. I think eSpeak is actually creating an invalid wav file. When I attempt to play the file using aplay, I get: Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 576061440 Hz, Mono aplay: set_params:965: Unable to install hw params: ACCESS: RW_INTERLEAVED FORMAT: S16_LE SUBFORMAT: STD SAMPLE_BITS: 16 FRAME_BITS: 16 CHANNELS: 1 RATE: NONE PERIOD_TIME: (21333 21334) PERIOD_SIZE: (12289118 12289119) PERIOD_BYTES: (24578236 24578238) PERIODS: (16 17) BUFFER_TIME: (341333 341334) BUFFER_SIZE: 196628971 BUFFER_BYTES: 393257942 TICK_TIME: 0 I'm not sure where to go with this nextin terms of further troubleshooting. If it would help at all, I could grant you ssh access to the box. Please let me know if that would be of use, or if there is anything else you'd like me to try. --Al From kb8aey at verizon.net Tue Jan 16 17:30:47 2007 From: kb8aey at verizon.net (mike coulombe) Date: Tue, 16 Jan 2007 11:30:47 -0600 (CST) Subject: need info on open office Message-ID: <0JBZ00JQY1ZBNA16@vms046.mailsrvcs.net> Hi, I was wondering what the current status with open office writer and orca is. It looks like the one in feisty is a newer version so has the performance with orca been improved. Thanks Mike. From francesco.fumanti at gmx.net Wed Jan 17 11:26:19 2007 From: francesco.fumanti at gmx.net (Francesco Fumanti) Date: Wed, 17 Jan 2007 12:26:19 +0100 Subject: Accessibility of gnome-controlcenter? Message-ID: Hello, At 11:16 AM +0000 1/15/07, Calum Benson wrote: >Both Windows XP (dunno about Vista) and Mac OS X >allow menu access to individual control panels if desired, and it seems >unlikely to me that we've done more user research than they have. I have not installed Feisty yet, so my reply might not make sense. Anyhow, I wanted to point out that the user has to open the System Preferences window (Gnome Control Centre) in order to get the menu from which he can choose a single control panel. Francesco From Norman.B.Robinson at usps.gov Fri Jan 19 14:59:50 2007 From: Norman.B.Robinson at usps.gov (Robinson, Norman B - Washington, DC) Date: Fri, 19 Jan 2007 09:59:50 -0500 Subject: Section 508 Refresh & Public Participation In-Reply-To: <1168859766.8976.27.camel@sr1-edub-04> Message-ID: List members, Have an opinion on how legal issues and technical standards impact your work? Does accessibility impact your development? Does it affect your customers? You might be interested in providing recommendations for updates or feedback to the refresh of the U. S. Section 508 (http://en.wikipedia.org/wiki/Section_508) Accessibility Standards. This effort is being coordinated on an international scale. This is an open process, please consider participating! More information is available via http://teitac.org. Please share this message as appropriate. I think this message is appropriate given this forum, but please excuse me for this one-time posting if unwelcome. I only thought there might be people interested but not aware of this effort. Regards, Norman B. Robinson From satyanarayanamurthy.tanikella at gmail.com Fri Jan 19 16:17:23 2007 From: satyanarayanamurthy.tanikella at gmail.com (Satyam) Date: Fri, 19 Jan 2007 21:47:23 +0530 Subject: Question about Ubuntu 6.10 Message-ID: <45b0ef1a.3f212922.6abb.fffff056@mx.google.com> Hi list, I am planning to install Ubuntu 6.10 (Desk top version) Now my questions are: 1. Can I install Databases like Mysql? 2. Is it possible to run Web servers like apache? 3. Is it possible to run like php etc? Hope to hear from you. Satyam. From henrik at ubuntu.com Fri Jan 19 17:56:43 2007 From: henrik at ubuntu.com (Henrik Omma) Date: Fri, 19 Jan 2007 18:56:43 +0100 Subject: Question about Ubuntu 6.10 In-Reply-To: <45b0ef1a.3f212922.6abb.fffff056@mx.google.com> References: <45b0ef1a.3f212922.6abb.fffff056@mx.google.com> Message-ID: <13408a8a0701190956n5fe5fd3ka5ee78e0c5793ef0@mail.gmail.com> Yes, you can do all of those. On 1/19/07, Satyam wrote: > Hi list, > I am planning to install Ubuntu 6.10 (Desk top version) > Now my questions are: > 1. Can I install Databases like Mysql? > 2. Is it possible to run Web servers like apache? > 3. Is it possible to run like php etc? > Hope to hear from you. > Satyam. > > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > From david.bolter at utoronto.ca Fri Jan 19 21:00:47 2007 From: david.bolter at utoronto.ca (David Bolter) Date: Fri, 19 Jan 2007 16:00:47 -0500 Subject: GOK + Ubuntu no longer explodes! Message-ID: <45B1317F.9000100@utoronto.ca> Just wanted to give a heads up that we just releasedGOK v1.2.1 and it appears to (finally) work around the GOK + Ubuntu + wacom crasher. Here is the tarball: ftp://ftp.gnome.org/pub/GNOME/sources/gok/1.2/gok-1.2.1.tar.gz cheers, David From henrik at ubuntu.com Fri Jan 19 21:21:51 2007 From: henrik at ubuntu.com (Henrik Omma) Date: Fri, 19 Jan 2007 22:21:51 +0100 Subject: GOK + Ubuntu no longer explodes! In-Reply-To: <45B1317F.9000100@utoronto.ca> References: <45B1317F.9000100@utoronto.ca> Message-ID: <13408a8a0701191321p47fdc68erdbf76b533817a560@mail.gmail.com> Great! Took me a while to find that bug as we have it down as an xorg bug in Launchpad: https://launchpad.net/ubuntu/+source/xorg/+bug/58600 Anyway, I've filed this sync request: https://bugs.launchpad.net/ubuntu/+source/gok/+bug/80655 which should fix it. Thanks! Henrik On 1/19/07, David Bolter wrote: > Just wanted to give a heads up that we just releasedGOK v1.2.1 and it > appears to (finally) work around the GOK + Ubuntu + wacom crasher. Here > is the tarball: > ftp://ftp.gnome.org/pub/GNOME/sources/gok/1.2/gok-1.2.1.tar.gz > > cheers, > David > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > From themuso at themuso.com Sun Jan 21 04:31:56 2007 From: themuso at themuso.com (Luke Yelavich) Date: Sun, 21 Jan 2007 15:31:56 +1100 Subject: eSpeak - PPC architecture In-Reply-To: <000701c7391e$aee95d80$6901a8c0@thinkpad> References: <4ea580068ejsd@clara.co.uk> <000701c7391e$aee95d80$6901a8c0@thinkpad> Message-ID: <20070121043156.GA14734@themuso.com> On Tue, Jan 16, 2007 at 02:30:33PM EST, Al Puzzuoli wrote: > Hi Jonathan, > > I tried the experiments you suggested. > > 1.> What text output do you get if you use the -x option, eg: > > espeak -x "hello"? > > Interestingly, I'm not getting any text at all. When I do this, I'm > immediately dropped back to the shell with no output. > > > 2. What happens if you send the speech output to a WAV file? > > Again, nothing useful. I think eSpeak is actually creating an invalid wav > file. I get the same behavior. Jonathan, I have come to the conclusion that the phoneme data as well as dictionaries need to be rebuilt, to suit the architecture the package is being built on. I notice that the espeakedit package has the routines to compile the phoneme data, but unfortunately one has to have a GUI running to use the --compile flag of the binary. Is it possible to separate out the phoneme compile routines to a separate binary, independant of any GUI libraries? If so, would you mind sending them to me, so I can use them to ensure all architectures ship with the correct voice and phoneme data? I don't want to make espeak 1.18 packages available, until we have this sorted out properly. Thanks. -- Luke Yelavich GPG key: 0xD06320CE (http://www.themuso.com/themuso-gpg-key.txt) Email & MSN: themuso at themuso.com Jabber: themuso at jabber.org.au -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From labrad0r at edpnet.be Sun Jan 21 09:15:05 2007 From: labrad0r at edpnet.be (Labrador) Date: Sun, 21 Jan 2007 10:15:05 +0100 Subject: installing Ubuntu with X and no assistance Message-ID: <20070121091505.GD2524@starfish> Hi, I'm new to this forum. A few months ago a sighted friend helped me with installing on his demo-pc some Ubuntu distribution with Gnopernicus. But should there be a way to do the same without any assistance ? Does the latest Ubuntu Edgy Eft come with Orca ? Or only Gnopernicus ? Any suggestions welcome. Thanks. Greetings, Labrador From jsd at clara.co.uk Sun Jan 21 10:14:27 2007 From: jsd at clara.co.uk (Jonathan Duddington) Date: Sun, 21 Jan 2007 10:14:27 +0000 (GMT) Subject: eSpeak - PPC architecture In-Reply-To: <20070121043156.GA14734@themuso.com> References: <4ea580068ejsd@clara.co.uk> <000701c7391e$aee95d80$6901a8c0@thinkpad> <20070121043156.GA14734@themuso.com> Message-ID: <4ea89d3f4ajsd@clara.co.uk> In article <20070121043156.GA14734 at themuso.com>, Luke Yelavich wrote: > > > > > 2. What happens if you send the speech output to a WAV file? > > > > Again, nothing useful. I think eSpeak is actually creating an > > invalid wav file. > I get the same behavior. What architecture and OS is this on? Is the byte order different from i386? Have you ever had eSpeak working on it, or do you know anyone who has? > Jonathan, I have come to the conclusion that the phoneme data as well > as dictionaries need to be rebuilt, to suit the architecture the > package is being built on. I notice that the espeakedit package has > the routines to compile the phoneme data, but unfortunately one has > to have a GUI running to use the --compile flag of the binary. Are you sure? What happens if you run espeakedit --compile or espeakedit --help ? Is there an error message? I've run my system (MEPIS 6, which is a KDE/Ubuntu distro) in "failsafe" mode, which I think means no GUI, and I can do espeakedit --compile OK. > Is it possible to separate out the phoneme compile routines to a > separate binary, independant of any GUI libraries? If so, would you > mind sending them to me, so I can use them to ensure all > architectures ship with the correct voice and phoneme data? Are you able to build the espeakedit program and compile the espeak-data with it? Does eSpeak then speak OK? The espeakedit program uses wxWidgets data types. It will take a bit of work to convert the phoneme compile routines so that they don't use them. From themuso at themuso.com Sun Jan 21 11:58:57 2007 From: themuso at themuso.com (Luke Yelavich) Date: Sun, 21 Jan 2007 22:58:57 +1100 Subject: eSpeak - PPC architecture In-Reply-To: <4ea89d3f4ajsd@clara.co.uk> References: <4ea580068ejsd@clara.co.uk> <000701c7391e$aee95d80$6901a8c0@thinkpad> <20070121043156.GA14734@themuso.com> <4ea89d3f4ajsd@clara.co.uk> Message-ID: <20070121115857.GA15727@themuso.com> On Sun, Jan 21, 2007 at 09:14:27PM EST, Jonathan Duddington wrote: > In article <20070121043156.GA14734 at themuso.com>, > Luke Yelavich wrote: > > > > > > > 2. What happens if you send the speech output to a WAV file? > > > > > > Again, nothing useful. I think eSpeak is actually creating an > > > invalid wav file. > > > I get the same behavior. > > What architecture and OS is this on? I got the same behavior on Ubuntu Edgy powerpc. > Is the byte order different from i386? I think it is, but I couldn't be sure of that. > Have you ever had eSpeak working on it, or do you know anyone who has? Don't know anybody who has had espeak working on powerpc, and never tried it previously. > > Jonathan, I have come to the conclusion that the phoneme data as well > > as dictionaries need to be rebuilt, to suit the architecture the > > package is being built on. I notice that the espeakedit package has > > the routines to compile the phoneme data, but unfortunately one has > > to have a GUI running to use the --compile flag of the binary. > > Are you sure? > What happens if you run espeakedit --compile or espeakedit --help ? > Is there an error message? luke at linden:~/espeak-data$ ../espeakedit-1.18/src/espeakedit --compile Error: Unable to initialize gtk, is DISPLAY set properly? luke at linden:~/espeak-data$ ../espeakedit-1.18/src/espeakedit --help Error: Unable to initialize gtk, is DISPLAY set properly? > I've run my system (MEPIS 6, which is a KDE/Ubuntu distro) in > "failsafe" mode, which I think means no GUI, and I can do > espeakedit --compile > OK. The above two commands were run on an i386 Ubuntu Edgy box, with no GUI running, and only minimum libraries installed to build the espeakedit binary. > > Is it possible to separate out the phoneme compile routines to a > > separate binary, independant of any GUI libraries? If so, would you > > mind sending them to me, so I can use them to ensure all > > architectures ship with the correct voice and phoneme data? > > Are you able to build the espeakedit program and compile the > espeak-data with it? I can build the espeakedit program, but as stated above, I cannot build the espeak data with it. > Does eSpeak then speak OK? If I could build the phoneme data successfully, I'd say that it very likely would. I don't have any GUI installed and running on my powerpc machine either, as it is mainly for server use. > The espeakedit program uses wxWidgets data types. It will take a bit > of work to convert the phoneme compile routines so that they don't use > them. Ok I thought as much. -- Luke Yelavich GPG key: 0xD06320CE (http://www.themuso.com/themuso-gpg-key.txt) Email & MSN: themuso at themuso.com Jabber: themuso at jabber.org.au -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From samuel.thibault at ens-lyon.org Sun Jan 21 12:06:49 2007 From: samuel.thibault at ens-lyon.org (Samuel Thibault) Date: Sun, 21 Jan 2007 13:06:49 +0100 Subject: eSpeak - PPC architecture In-Reply-To: <20070121115857.GA15727@themuso.com> References: <4ea580068ejsd@clara.co.uk> <000701c7391e$aee95d80$6901a8c0@thinkpad> <20070121043156.GA14734@themuso.com> <4ea89d3f4ajsd@clara.co.uk> <20070121115857.GA15727@themuso.com> Message-ID: <20070121120649.GA5784@implementation> Luke Yelavich, le Sun 21 Jan 2007 22:58:57 +1100, a écrit : > > Is the byte order different from i386? > > I think it is, but I couldn't be sure of that. It is different indeed: ppc is big endian. Samuel From jsd at clara.co.uk Sun Jan 21 12:37:38 2007 From: jsd at clara.co.uk (Jonathan Duddington) Date: Sun, 21 Jan 2007 12:37:38 +0000 (GMT) Subject: eSpeak - PPC architecture In-Reply-To: <20070121115857.GA15727@themuso.com> References: <4ea580068ejsd@clara.co.uk> <000701c7391e$aee95d80$6901a8c0@thinkpad> <20070121043156.GA14734@themuso.com> <4ea89d3f4ajsd@clara.co.uk> <20070121115857.GA15727@themuso.com> Message-ID: <4ea8aa5b5djsd@clara.co.uk> In article <20070121115857.GA15727 at themuso.com>, Luke Yelavich wrote: > I got the same behavior on Ubuntu Edgy powerpc. > > What happens if you run espeakedit --compile or espeakedit > > --help ? Is there an error message? > luke at linden:~/espeak-data$ ../espeakedit-1.18/src/espeakedit --help > Error: Unable to initialize gtk, is DISPLAY set properly? OK. I need to make a command line program with the compile phoneme routines, but which does not use wxWidgets. Do I have a deadline? From Kwatson at smed.yi.org Sun Jan 21 15:31:37 2007 From: Kwatson at smed.yi.org (Keith Watson) Date: Sun, 21 Jan 2007 10:31:37 -0500 Subject: Gaim Buddy List Message-ID: <20070121153137.GA18400@smed.yi.org> All, I understand that tables are in a state of flux right now. But is anyone besides me having an issue with the buddy list in gaim not being visible? Keith -- Among the major impediments to discovery are not the ignorant but those with illusions of knowledge. - B. Alan Wallace From alpuzz at gmail.com Sun Jan 21 16:00:01 2007 From: alpuzz at gmail.com (Al Puzzuoli) Date: Sun, 21 Jan 2007 11:00:01 -0500 Subject: eSpeak - PPC architecture References: <4ea580068ejsd@clara.co.uk><000701c7391e$aee95d80$6901a8c0@thinkpad><20070121043156.GA14734@themuso.com> <4ea89d3f4ajsd@clara.co.uk><20070121115857.GA15727@themuso.com> <4ea8aa5b5djsd@clara.co.uk> Message-ID: <002a01c73d75$4f025790$6901a8c0@thinkpad> Hi guys, My PPC box is running the GUI; so what would be involved in recompiling the data? Is it just a matter of installing the espeakedit program and issuing a command line? if the process isn't too terribly complicated, I'd be happy to recompile the data at this end and pass it along to Luke, or whomever needs it, if that would save time. --Al ----- Original Message ----- From: "Jonathan Duddington" To: Sent: Sunday, January 21, 2007 7:37 AM Subject: Re: eSpeak - PPC architecture > In article <20070121115857.GA15727 at themuso.com>, > Luke Yelavich wrote: > >> I got the same behavior on Ubuntu Edgy powerpc. > >> > What happens if you run espeakedit --compile or espeakedit >> > --help ? Is there an error message? > >> luke at linden:~/espeak-data$ ../espeakedit-1.18/src/espeakedit --help >> Error: Unable to initialize gtk, is DISPLAY set properly? > > OK. I need to make a command line program with the compile phoneme > routines, but which does not use wxWidgets. > > Do I have a deadline? > > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility From jsd at clara.co.uk Sun Jan 21 16:17:44 2007 From: jsd at clara.co.uk (Jonathan Duddington) Date: Sun, 21 Jan 2007 16:17:44 +0000 (GMT) Subject: eSpeak - PPC architecture In-Reply-To: <002a01c73d75$4f025790$6901a8c0@thinkpad> References: <4ea580068ejsd@clara.co.uk><000701c7391e$aee95d80$6901a8c0@thinkpad><20070121043156.GA14734@themuso.com> <4ea89d3f4ajsd@clara.co.uk><20070121115857.GA15727@themuso.com> <4ea8aa5b5djsd@clara.co.uk> <002a01c73d75$4f025790$6901a8c0@thinkpad> Message-ID: <4ea8be81e0jsd@clara.co.uk> In article <002a01c73d75$4f025790$6901a8c0 at thinkpad>, Al Puzzuoli wrote: > My PPC box is running the GUI; so what would be involved in > recompiling the data? Is it just a matter of installing the > espeakedit program and issuing a command line? First I must check for other byte-order dependencies, and make some changes to the espeakedit program. I will let you know when it's ready to try. You will need to compile the espeakedit program, which shouldn't be a problem. You'll need the wxWidgets libraries, but these may already be installed if you are running Ubuntu. You need the packages: libwxgtk2.6 and libwxgtk2.6-dev. Once it's compiled, hopefully you will be able to just do: epseakedit --compile and eSpeak will then be able speak OK. From j-diggs at comcast.net Sun Jan 21 16:35:40 2007 From: j-diggs at comcast.net (Joanmarie Diggs) Date: Sun, 21 Jan 2007 11:35:40 -0500 Subject: Gaim Buddy List In-Reply-To: <20070121153137.GA18400@smed.yi.org> References: <20070121153137.GA18400@smed.yi.org> Message-ID: <1169397340.7570.1.camel@pokey> Hi Keith. Rich fixed this recently. If you grab the latest Orca from SVN trunk, you should be able to access the buddy list. Hope this helps. Joanie On Sun, 2007-01-21 at 10:31 -0500, Keith Watson wrote: > All, > > I understand that tables are in a state of flux right now. But is > anyone besides me having an issue with the buddy list in gaim not > being visible? > > Keith > > -- > Among the major impediments to discovery are not the ignorant > but those with illusions of knowledge. - B. Alan Wallace > From kb8aey at verizon.net Sun Jan 21 17:34:03 2007 From: kb8aey at verizon.net (mike coulombe) Date: Sun, 21 Jan 2007 11:34:03 -0600 (CST) Subject: need some info about the alternative cd Message-ID: <0JC800JSGBGQ0Z50@vms046.mailsrvcs.net> Hi, has any accessibility been added to the alternative CD. If so how do you start the screen reader. Also has anyone installed the feisty live CD lately. I am still having a problem after picking the keyboard everything blows up very large on the screen and it seems to crash. Thanks Mike. X-Antivirus: avast! (VPS 0704-0, 01/18/2007), Outbound message X-Antivirus-Status: Clean From themuso at themuso.com Sun Jan 21 20:34:30 2007 From: themuso at themuso.com (Luke Yelavich) Date: Mon, 22 Jan 2007 07:34:30 +1100 Subject: eSpeak - PPC architecture In-Reply-To: <4ea8aa5b5djsd@clara.co.uk> References: <4ea580068ejsd@clara.co.uk> <000701c7391e$aee95d80$6901a8c0@thinkpad> <20070121043156.GA14734@themuso.com> <4ea89d3f4ajsd@clara.co.uk> <20070121115857.GA15727@themuso.com> <4ea8aa5b5djsd@clara.co.uk> Message-ID: <20070121203430.GA5588@themuso.com> On Sun, Jan 21, 2007 at 11:37:38PM EST, Jonathan Duddington wrote: > In article <20070121115857.GA15727 at themuso.com>, > Luke Yelavich wrote: > > > I got the same behavior on Ubuntu Edgy powerpc. > > > > What happens if you run espeakedit --compile or espeakedit > > > --help ? Is there an error message? > > > luke at linden:~/espeak-data$ ../espeakedit-1.18/src/espeakedit --help > > Error: Unable to initialize gtk, is DISPLAY set properly? > > OK. I need to make a command line program with the compile phoneme > routines, but which does not use wxWidgets. > > Do I have a deadline? If Al can get the data compiled and sent to me, that should be good enough for now, as I don't see the chances of espeak being used on ia64 and sparc being very high, but for the future, we need a more perminant solution that will allow all architectures to have the correct byte ordering. -- Luke Yelavich GPG key: 0xD06320CE (http://www.themuso.com/themuso-gpg-key.txt) Email & MSN: themuso at themuso.com Jabber: themuso at jabber.org.au -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From jsd at clara.co.uk Mon Jan 22 00:23:39 2007 From: jsd at clara.co.uk (Jonathan Duddington) Date: Mon, 22 Jan 2007 00:23:39 +0000 (GMT) Subject: eSpeak - PPC architecture In-Reply-To: <4ea8be81e0jsd@clara.co.uk> References: <4ea580068ejsd@clara.co.uk><000701c7391e$aee95d80$6901a8c0@thinkpad><20070121043156.GA14734@themuso.com> <4ea89d3f4ajsd@clara.co.uk><20070121115857.GA15727@themuso.com> <4ea8aa5b5djsd@clara.co.uk> <002a01c73d75$4f025790$6901a8c0@thinkpad> <4ea8be81e0jsd@clara.co.uk> Message-ID: <4ea8eafe5fjsd@clara.co.uk> In article <4ea8be81e0jsd at clara.co.uk>, Jonathan Duddington wrote: > First I must check for other byte-order dependencies, and make some > changes to the espeakedit program. I will let you know when it's ready > to try. > Once it's compiled, hopefully you will be able to just do: > epseakedit --compile > and eSpeak will then be able speak OK. I think the espeakedit program may be able to run on PPC and compile the phoneme data. espeakedit --compile will compile both the phoneme data and the dictionary data, if it finds the source data in the expected places, for which the defaults are: espeak-data/phsource espeak-data/dictsource Let me know whether it works. From jsd at clara.co.uk Mon Jan 22 00:34:07 2007 From: jsd at clara.co.uk (Jonathan Duddington) Date: Mon, 22 Jan 2007 00:34:07 +0000 (GMT) Subject: eSpeak - PPC architecture In-Reply-To: <20070121203430.GA5588@themuso.com> References: <4ea580068ejsd@clara.co.uk> <000701c7391e$aee95d80$6901a8c0@thinkpad> <20070121043156.GA14734@themuso.com> <4ea89d3f4ajsd@clara.co.uk> <20070121115857.GA15727@themuso.com> <4ea8aa5b5djsd@clara.co.uk> <20070121203430.GA5588@themuso.com> Message-ID: <4ea8ebf3a2jsd@clara.co.uk> In article <20070121203430.GA5588 at themuso.com>, Luke Yelavich wrote: > If Al can get the data compiled and sent to me, that should be good > enough for now, as I don't see the chances of espeak being used on > ia64 and sparc being very high, but for the future, we need a more > perminant solution that will allow all architectures to have the > correct byte ordering. I've seen reports of eSpeak working OK on ia64. The data should be binary compatible with i386. For example, here is a reported bug which I fixed for version 1.17 http://sourceforge.net/forum/message.php?msg_id=3991770 From alpuzz at gmail.com Mon Jan 22 01:59:45 2007 From: alpuzz at gmail.com (Al Puzzuoli) Date: Sun, 21 Jan 2007 20:59:45 -0500 Subject: eSpeak - PPC architecture References: <4ea580068ejsd@clara.co.uk><000701c7391e$aee95d80$6901a8c0@thinkpad><20070121043156.GA14734@themuso.com> <4ea89d3f4ajsd@clara.co.uk><20070121115857.GA15727@themuso.com> <4ea8aa5b5djsd@clara.co.uk><20070121203430.GA5588@themuso.com> <4ea8ebf3a2jsd@clara.co.uk> Message-ID: <001101c73dc8$fde0a520$6901a8c0@thinkpad> Upon attempting to compile the phoneme data, I'm getting the following, if there is anything I can do at my end, please let me know: Script started on Sun 21 Jan 2007 08:25:37 PM EST ]0;root at mac: ~root at mac:~# espeakedit --compile GTK Accessibility Module initialized Compiling phoneme data: /home/alpuzz/espeak-data/phsource/ Unknown phoneme table: 'en' Unknown phoneme table: 'ru' Unknown phoneme table: 'es' Unknown phoneme table: 'cy' Unknown phoneme table: 'nl' Unknown phoneme table: 'pl' Unknown phoneme table: 'de' Unknown phoneme table: 'vi' Unknown phoneme table: 'hi' Unknown phoneme table: 'af' Unknown phoneme table: 'sv' Unknown phoneme table: 'no' Unknown phoneme table: 'en' Unknown phoneme table: 'ro' Unknown phoneme table: 'eo' Unknown phoneme table: 'fi' Unknown phoneme table: 'pt' Unknown phoneme table: 'it' Unknown phoneme table: 'fr' Unknown phoneme table: 'el' Unknown phoneme table: 'en' Compiled phonemes: 477 errors. See 'error.log'. Dictionary errors: ru 642, es 367, cy 508, nl 393, pl 195, de 2478, vi 476, hi 403, af 2670, sv 680, no 163, en 19361, ro 1074, eo 324, fi 769, pt 1376, it 994, fr 3044, el 541, *** stack smashing detected ***: espeakedit terminated Aborted (core dumped) ]0;root at mac: ~root at mac:~# exit Script done on Sun 21 Jan 2007 08:26:40 PM EST ----- Original Message ----- From: "Jonathan Duddington" To: Sent: Sunday, January 21, 2007 7:34 PM Subject: Re: eSpeak - PPC architecture > In article <20070121203430.GA5588 at themuso.com>, > Luke Yelavich wrote: > >> If Al can get the data compiled and sent to me, that should be good >> enough for now, as I don't see the chances of espeak being used on >> ia64 and sparc being very high, but for the future, we need a more >> perminant solution that will allow all architectures to have the >> correct byte ordering. > > I've seen reports of eSpeak working OK on ia64. The data should be > binary compatible with i386. > > For example, here is a reported bug which I fixed for version 1.17 > http://sourceforge.net/forum/message.php?msg_id=3991770 > > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility From themuso at themuso.com Mon Jan 22 04:19:54 2007 From: themuso at themuso.com (Luke Yelavich) Date: Mon, 22 Jan 2007 15:19:54 +1100 Subject: eSpeak - PPC architecture In-Reply-To: <4ea8eafe5fjsd@clara.co.uk> References: <4ea8aa5b5djsd@clara.co.uk> <002a01c73d75$4f025790$6901a8c0@thinkpad> <4ea8be81e0jsd@clara.co.uk> <4ea8eafe5fjsd@clara.co.uk> Message-ID: <20070122041954.GA5667@themuso.com> On Mon, Jan 22, 2007 at 11:23:39AM EST, Jonathan Duddington wrote: > I think the espeakedit program may be able to run on PPC and compile > the phoneme data. > > espeakedit --compile > > will compile both the phoneme data and the dictionary data, if it finds > the source data in the expected places, for which the defaults are: > espeak-data/phsource > espeak-data/dictsource > > Let me know whether it works. Ok. The following steps were carried out on two different boxes, one powerpc, and one i386. I managed to get X forwarding set up on my powerpc, so that espeakedit can run. Here is what I did. * Unpacked fresh directories of both zip files, espeak-1.18-source.zip, and espeakedit-1.18.zip. * Created an empty espeak-data directory in my home directory, and copied the voices directory into it, from the espeak-1.18-source/espeak-data directory. * Copied dictsource from espeak-1.18 into espeak-data. * Copied the phsource directory from espeakedit-1.18 into the espeak-data directory I previously created. * Built a fresh binary of espeakedit, and moved it to my home directory. * Entered the espeak-data directory, which as previously stated, only has the voices, phsource, and dictsource directories. * Ran the command: ~/espeakedit --compile Attached are two log files, from both attempted compile runs. Notice the vast difference in output. The other difference is that the *_dict files are built on powerpc, and only the phoneme datafiles are present on i386. However, i386 has correctly built phoneme data, and powerpc doesn't, as evident from the Unknown phoneme table message when compiling, and also when I attempt to make espeak say something. Please let me know if you need any clarrification on what I have outlined above, and I hope these log files are useful. -- Luke Yelavich GPG key: 0xD06320CE (http://www.themuso.com/themuso-gpg-key.txt) Email & MSN: themuso at themuso.com Jabber: themuso at jabber.org.au -------------- next part -------------- Compiling phoneme data: /home/luke/espeak-data/phsource/ Can't read dictionary file: '/home/luke/espeak-data/en_dict' Can't read dictionary file: '/home/luke/espeak-data/en_dict' Compiled phonemes: 0 errors. Compiled 0 dictionaries -------------- next part -------------- Compiling phoneme data: /home/luke/espeak-data/phsource/ Unknown phoneme table: 'en' Can't read dictionary file: '/home/luke/espeak-data/en_dict' Unknown phoneme table: 'af' Can't read dictionary file: '/home/luke/espeak-data/af_dict' Unknown phoneme table: 'cy' Can't read dictionary file: '/home/luke/espeak-data/cy_dict' Unknown phoneme table: 'de' Can't read dictionary file: '/home/luke/espeak-data/de_dict' Unknown phoneme table: 'el' Can't read dictionary file: '/home/luke/espeak-data/el_dict' Unknown phoneme table: 'en' Can't read dictionary file: '/home/luke/espeak-data/en_dict' Unknown phoneme table: 'eo' Can't read dictionary file: '/home/luke/espeak-data/eo_dict' Unknown phoneme table: 'es' Can't read dictionary file: '/home/luke/espeak-data/es_dict' Unknown phoneme table: 'fi' Can't read dictionary file: '/home/luke/espeak-data/fi_dict' Unknown phoneme table: 'fr' Can't read dictionary file: '/home/luke/espeak-data/fr_dict' Unknown phoneme table: 'hi' Can't read dictionary file: '/home/luke/espeak-data/hi_dict' Unknown phoneme table: 'it' Can't read dictionary file: '/home/luke/espeak-data/it_dict' Unknown phoneme table: 'nl' Can't read dictionary file: '/home/luke/espeak-data/nl_dict' Unknown phoneme table: 'no' Can't read dictionary file: '/home/luke/espeak-data/no_dict' Unknown phoneme table: 'pl' Can't read dictionary file: '/home/luke/espeak-data/pl_dict' Unknown phoneme table: 'pt' Can't read dictionary file: '/home/luke/espeak-data/pt_dict' Unknown phoneme table: 'ro' Can't read dictionary file: '/home/luke/espeak-data/ro_dict' Unknown phoneme table: 'ru' Can't read dictionary file: '/home/luke/espeak-data/ru_dict' Unknown phoneme table: 'sv' Can't read dictionary file: '/home/luke/espeak-data/sv_dict' Unknown phoneme table: 'vi' Can't read dictionary file: '/home/luke/espeak-data/vi_dict' Unknown phoneme table: 'en' Compiled phonemes: 477 errors. See 'error.log'. Dictionary errors: af 2670, cy 508, de 2478, el 541, en 19361, eo 324, es 367, fi 769, fr 3044, hi 403, it 994, nl 393, no 163, pl 195, pt 1376, ro 1074, ru 642, sv 680, vi 476, *** stack smashing detected ***: /home/luke/espeakedit terminated Aborted -------------- next part -------------- ______________________________ Phoneme Table: 'base' 167: File not SPEC or RIFF: 'vowel/@' 175: File not SPEC or RIFF: 'vowel/@-' 188: File not SPEC or RIFF: 'ustop/percus10' 198: File not SPEC or RIFF: 'j/j@' 199: File not SPEC or RIFF: 'j2/j2@' 200: File not SPEC or RIFF: 'w/w@' 201: File not SPEC or RIFF: 'l/l@' 203: File not SPEC or RIFF: 'l^/j2@' 204: File not SPEC or RIFF: 'r/r@' 205: File not SPEC or RIFF: 'r2/r2@' 206: File not SPEC or RIFF: 'm/m@' 207: File not SPEC or RIFF: 'n/n@' 208: File not SPEC or RIFF: 'nn/nn@' 209: File not SPEC or RIFF: 'n^/n^@' 210: File not SPEC or RIFF: 'l/L1_ at L' 211: File not SPEC or RIFF: 'l/L2_ at L' 212: File not SPEC or RIFF: 'l/xl' 213: File not SPEC or RIFF: 'w/xw' 214: File not SPEC or RIFF: 'j/xj' 215: File not SPEC or RIFF: 'r/xr' 217: File not SPEC or RIFF: 'r3/r_@' 221: File not SPEC or RIFF: 'j/ja' 222: File not SPEC or RIFF: 'j2/j2a' 223: File not SPEC or RIFF: 'w/wa' 224: File not SPEC or RIFF: 'l/la' 226: File not SPEC or RIFF: 'l^/j2a' 227: File not SPEC or RIFF: 'r/ra' 228: File not SPEC or RIFF: 'r2/r2a' 229: File not SPEC or RIFF: 'm/ma' 230: File not SPEC or RIFF: 'n/na' 231: File not SPEC or RIFF: 'nn/nna' 232: File not SPEC or RIFF: 'n^/n^a' 233: File not SPEC or RIFF: 'l/L1_aL' 234: File not SPEC or RIFF: 'l/L2_aL' 240: File not SPEC or RIFF: 'r3/r_a' 244: File not SPEC or RIFF: 'j/je' 245: File not SPEC or RIFF: 'j2/j2e' 246: File not SPEC or RIFF: 'w/we' 247: File not SPEC or RIFF: 'l/le' 249: File not SPEC or RIFF: 'l^/j2e' 250: File not SPEC or RIFF: 'r/re' 251: File not SPEC or RIFF: 'r2/r2e' 252: File not SPEC or RIFF: 'm/me' 253: File not SPEC or RIFF: 'n/ne' 254: File not SPEC or RIFF: 'nn/nne' 255: File not SPEC or RIFF: 'n^/n^e' 256: File not SPEC or RIFF: 'l/L1_eL' 257: File not SPEC or RIFF: 'l/L2_eL' 263: File not SPEC or RIFF: 'r3/r_e' 267: File not SPEC or RIFF: 'j/ji' 268: File not SPEC or RIFF: 'j2/j2i' 269: File not SPEC or RIFF: 'w/wi' 270: File not SPEC or RIFF: 'l/li' 272: File not SPEC or RIFF: 'l^/j2i' 273: File not SPEC or RIFF: 'r/ri' 274: File not SPEC or RIFF: 'r2/r2i' 275: File not SPEC or RIFF: 'm/mi' 276: File not SPEC or RIFF: 'n/ni' 277: File not SPEC or RIFF: 'nn/nni' 278: File not SPEC or RIFF: 'n^/n^i' 279: File not SPEC or RIFF: 'l/L1_iL' 280: File not SPEC or RIFF: 'l/L2_iL' 281: File not SPEC or RIFF: 'nn/inn' 282: File not SPEC or RIFF: 'j2/xj2' 286: File not SPEC or RIFF: 'r3/r_i' 290: File not SPEC or RIFF: 'j/jo' 291: File not SPEC or RIFF: 'j2/j2o' 292: File not SPEC or RIFF: 'w/wo' 293: File not SPEC or RIFF: 'l/lo' 295: File not SPEC or RIFF: 'l^/j2o' 296: File not SPEC or RIFF: 'r/ro' 297: File not SPEC or RIFF: 'r2/r2o' 298: File not SPEC or RIFF: 'm/mo' 299: File not SPEC or RIFF: 'n/no' 300: File not SPEC or RIFF: 'nn/nno' 301: File not SPEC or RIFF: 'n^/n^o' 302: File not SPEC or RIFF: 'l/L1_oL' 303: File not SPEC or RIFF: 'l/L2_oL' 309: File not SPEC or RIFF: 'r3/r_o' 313: File not SPEC or RIFF: 'j/ju' 314: File not SPEC or RIFF: 'j2/j2u' 315: File not SPEC or RIFF: 'w/wu' 316: File not SPEC or RIFF: 'l/lu' 318: File not SPEC or RIFF: 'l^/j2u' 319: File not SPEC or RIFF: 'r/ru' 320: File not SPEC or RIFF: 'r2/r2u' 321: File not SPEC or RIFF: 'm/mu' 322: File not SPEC or RIFF: 'n/nu' 323: File not SPEC or RIFF: 'nn/nnu' 324: File not SPEC or RIFF: 'n^/n^u' 325: File not SPEC or RIFF: 'l/L1_uL' 326: File not SPEC or RIFF: 'l/L2_uL' 332: File not SPEC or RIFF: 'r3/r_u' 350: File not SPEC or RIFF: 'r/r' 351: File not SPEC or RIFF: 'r/_r' 352: File not SPEC or RIFF: 'r/tr' 355: File not SPEC or RIFF: 'r/r_' 363: File not SPEC or RIFF: 'r3/r_' 363: File not SPEC or RIFF: 'r3/rx' 364: File not SPEC or RIFF: 'r3/r_n' 365: File not SPEC or RIFF: 'r/rr' 366: File not SPEC or RIFF: 'r/trr' 377: File not SPEC or RIFF: 'r2/_r2' 386: File not SPEC or RIFF: 'l/l' 387: File not SPEC or RIFF: 'l/_l' 388: File not SPEC or RIFF: 'l/tl' 389: File not SPEC or RIFF: 'l/l_long' 397: File not SPEC or RIFF: 'l/l_' 414: File not SPEC or RIFF: 'l^/l^' 415: File not SPEC or RIFF: 'l^/_l^' 425: File not SPEC or RIFF: 'w/w' 426: File not SPEC or RIFF: 'w/_w' 434: File not SPEC or RIFF: 'w/w_' 446: File not SPEC or RIFF: 'j/_j' 456: File not SPEC or RIFF: 'j/j_' 473: File not SPEC or RIFF: 'j2/_j2' 483: File not SPEC or RIFF: 'm/_m' 484: File not SPEC or RIFF: 'm/m_' 485: File not SPEC or RIFF: 'm/mj' 495: File not SPEC or RIFF: 'n/_n' 497: File not SPEC or RIFF: 'n/n_' 498: File not SPEC or RIFF: 'n/nj' 508: File not SPEC or RIFF: 'n^/_n^' 509: File not SPEC or RIFF: 'n^/n^_' 521: File not SPEC or RIFF: 'nn/_nn' 522: File not SPEC or RIFF: 'nn/nn_' 523: File not SPEC or RIFF: 'nn/nnj' 531: File not SPEC or RIFF: 'r3/@tap' 533: File not SPEC or RIFF: 'r3/@tap_i' 550: File not SPEC or RIFF: 'b/b' 550: File not SPEC or RIFF: 'x/b' 551: File not SPEC or RIFF: 'b/b_' 551: File not SPEC or RIFF: 'x/b_' 552: File not SPEC or RIFF: 'b/ba' 553: File not SPEC or RIFF: 'b/b@' 554: File not SPEC or RIFF: 'b/be' 555: File not SPEC or RIFF: 'b/bi' 556: File not SPEC or RIFF: 'b/bo' 557: File not SPEC or RIFF: 'b/bu' 558: File not SPEC or RIFF: 'b/b at 2' 560: File not SPEC or RIFF: 'b/xb' 571: File not SPEC or RIFF: 'd/d' 571: File not SPEC or RIFF: 'x/d' 572: File not SPEC or RIFF: 'd/d_' 572: File not SPEC or RIFF: 'x/d_' 573: File not SPEC or RIFF: 'd/dr' 575: File not SPEC or RIFF: 'd/xd' 585: File not SPEC or RIFF: 'x/d_dnt' 599: File not SPEC or RIFF: 'd/tap' 601: File not SPEC or RIFF: 'd/tap_i' 615: File not SPEC or RIFF: 'dzh/dzh' 615: File not SPEC or RIFF: 'x/dzh' 616: File not SPEC or RIFF: 'dzh/dzh_' 616: File not SPEC or RIFF: 'x/dzh_' 618: File not SPEC or RIFF: 'dzh/xdzh' 626: File not SPEC or RIFF: 'x/dz_pzd' 640: File not SPEC or RIFF: 'g/g' 640: File not SPEC or RIFF: 'x/g' 641: File not SPEC or RIFF: 'g/g_' 641: File not SPEC or RIFF: 'x/g_' 643: File not SPEC or RIFF: 'g/xg' 653: File not SPEC or RIFF: 'g2/g' 653: File not SPEC or RIFF: 'x/g2_' 654: File not SPEC or RIFF: 'g2/g_' 656: File not SPEC or RIFF: 'g2/xg' 672: File not SPEC or RIFF: 'voc/bh' 672: File not SPEC or RIFF: 'vocw/v' 673: File not SPEC or RIFF: 'voc/v_' 683: File not SPEC or RIFF: 'voc/v' 692: File not SPEC or RIFF: 'voc/dh' 692: File not SPEC or RIFF: 'vocw/dh' 693: File not SPEC or RIFF: 'voc/dh_' 702: File not SPEC or RIFF: 'voc/z' 702: File not SPEC or RIFF: 'ufric/s_' 703: File not SPEC or RIFF: 'voc/z_' 713: File not SPEC or RIFF: 'voc/zh' 713: File not SPEC or RIFF: 'vocw/zh' 714: File not SPEC or RIFF: 'voc/zh_' 724: File not SPEC or RIFF: 'voc/z_pzd' 724: File not SPEC or RIFF: 'ufric/s_pzd_' 725: File not SPEC or RIFF: 'voc/z_pzd_' 737: File not SPEC or RIFF: 'voc/Q' 737: File not SPEC or RIFF: 'vocw/Q' 738: File not SPEC or RIFF: 'voc/Q_' 738: File not SPEC or RIFF: 'vocw/Q_' 767: File not SPEC or RIFF: 'ustop/p' 768: File not SPEC or RIFF: 'ustop/p_' 769: File not SPEC or RIFF: 'ustop/pr' 770: File not SPEC or RIFF: 'ustop/pl' 780: File not SPEC or RIFF: 'ustop/t' 781: File not SPEC or RIFF: 'ustop/t_' 782: File not SPEC or RIFF: 'ustop/tr' 792: File not SPEC or RIFF: 'ustop/t_dnt' 804: File not SPEC or RIFF: 'ustop/tsh' 805: File not SPEC or RIFF: 'ustop/tsh_' 814: File not SPEC or RIFF: 'ustop/ts_pzd' 826: File not SPEC or RIFF: 'ustop/c' 836: File not SPEC or RIFF: 'ustop/k' 837: File not SPEC or RIFF: 'ustop/k_' 838: File not SPEC or RIFF: 'ustop/kr' 839: File not SPEC or RIFF: 'ustop/kl' 840: File not SPEC or RIFF: 'ustop/ki' 849: File not SPEC or RIFF: 'ustop/k_unasp' 865: File not SPEC or RIFF: 'ufric/f' 866: File not SPEC or RIFF: 'ufric/f_' 876: File not SPEC or RIFF: 'ufric/th' 877: File not SPEC or RIFF: 'ufric/th_' 887: File not SPEC or RIFF: 'ufric/s' 889: File not SPEC or RIFF: 'ufric/s!' 902: File not SPEC or RIFF: 'ufric/sh' 903: File not SPEC or RIFF: 'ufric/sh_' 914: File not SPEC or RIFF: 'ufric/s_pzd' 924: File not SPEC or RIFF: 'ufric/ll' 935: File not SPEC or RIFF: 'ufric/ch' 945: File not SPEC or RIFF: 'ufric/x' 954: File not SPEC or RIFF: 'ufric/h_' 955: File not SPEC or RIFF: 'ufric/h@' 956: File not SPEC or RIFF: 'ufric/ha' 957: File not SPEC or RIFF: 'ufric/he' 958: File not SPEC or RIFF: 'ufric/hi' 959: File not SPEC or RIFF: 'ufric/ho' 960: File not SPEC or RIFF: 'ufric/hu' ______________________________ Phoneme Table: 'en' include ph_english 37: File not SPEC or RIFF: 'l/l_2' 76: File not SPEC or RIFF: 'vwl_en/@L' 85: File not SPEC or RIFF: 'vowel/a_en' 93: File not SPEC or RIFF: 'vowel/ee_2' 101: File not SPEC or RIFF: 'vowel/ii_en' 116: File not SPEC or RIFF: 'vowel/0' 124: File not SPEC or RIFF: 'vowel/V' 132: File not SPEC or RIFF: 'vowel/uu' 149: File not SPEC or RIFF: 'vowel/a#_3' 157: File not SPEC or RIFF: 'vowel/aa_2' 173: File not SPEC or RIFF: 'vowel/3_en' 182: File not SPEC or RIFF: 'vowel/i_en' 183: File not SPEC or RIFF: 'w/wi2' 191: File not SPEC or RIFF: 'vowel/oo_en' 216: File not SPEC or RIFF: 'vwl_en/u' 217: File not SPEC or RIFF: 'vwl_en/u_L' 224: File not SPEC or RIFF: 'vdiph/au' 231: File not SPEC or RIFF: 'vdiph/@u_en' 238: File not SPEC or RIFF: 'vdiph/ai_en' 245: File not SPEC or RIFF: 'vdiph/eei' 252: File not SPEC or RIFF: 'vdiph/ooi' 259: File not SPEC or RIFF: 'vowel/ee_1' 267: File not SPEC or RIFF: 'vdiph2/ii@' 275: File not SPEC or RIFF: 'vdiph2/ii at _2' 283: File not SPEC or RIFF: 'vdiph2/uu@' 291: File not SPEC or RIFF: 'vwl_en/aI@' 299: File not SPEC or RIFF: 'vwl_en/aU@' 314: File not SPEC or RIFF: 'vowel/e' 321: File not SPEC or RIFF: 'vowel/o' 328: File not SPEC or RIFF: 'vdiph/eu' 335: File not SPEC or RIFF: 'vdiph/ui' 342: File not SPEC or RIFF: 'vnasal/aa_n' 349: File not SPEC or RIFF: 'vnasal/ee_n' 356: File not SPEC or RIFF: 'vnasal/oo_n' 363: File not SPEC or RIFF: 'vnasal/W_n' 370: File not SPEC or RIFF: 'vowel/y' 384: File not SPEC or RIFF: 'vowel/y#' 391: File not SPEC or RIFF: 'vowel/oe' 398: File not SPEC or RIFF: 'vowel/u#' 404: File not SPEC or RIFF: 'vowel/o-' 412: File not SPEC or RIFF: 'vowel/i#' ______________________________ Phoneme Table: 'en_n' include ph_english_n 46: File not SPEC or RIFF: 'vowel/a' 54: File not SPEC or RIFF: 'vowel/ee_6' 78: File not SPEC or RIFF: 'vowel/0_2' 86: File not SPEC or RIFF: 'vowel/o-_2' 94: File not SPEC or RIFF: 'vowel/u' 119: File not SPEC or RIFF: 'vowel/aa_5' 135: File not SPEC or RIFF: 'vowel/3_2' 144: File not SPEC or RIFF: 'vowel/i' 153: File not SPEC or RIFF: 'vowel/oo_1' 162: File not SPEC or RIFF: 'vwl_en_n/O@' 178: File not SPEC or RIFF: 'vowel/u#_3' 179: File not SPEC or RIFF: 'vwl_en_n/u_' 187: File not SPEC or RIFF: 'vdiph/eeu_3' 194: File not SPEC or RIFF: 'vowel/o_4' 201: File not SPEC or RIFF: 'vdiph/ae_2' 230: File not SPEC or RIFF: 'vdiph2/i@' ______________________________ Phoneme Table: 'en_rp' include ph_english_rp 10: File not SPEC or RIFF: 'vwl_en_rp/@' 46: File not SPEC or RIFF: 'vowel/&' 54: File not SPEC or RIFF: 'vowel/e_mid' 62: File not SPEC or RIFF: 'vowel/ii_4' 69: File not SPEC or RIFF: 'vwl_en/i' 77: File not SPEC or RIFF: 'vowel/0_3' 85: File not SPEC or RIFF: 'vowel/V_3' 94: File not SPEC or RIFF: 'vowel/o-_3' 119: File not SPEC or RIFF: 'vwl_en_rp/aa' 135: File not SPEC or RIFF: 'vowel/3_3' 178: File not SPEC or RIFF: 'vowel/u_3' 186: File not SPEC or RIFF: 'vdiph/au_3' 193: File not SPEC or RIFF: 'vdiph/@u_2' 200: File not SPEC or RIFF: 'vdiph/ai_6' 207: File not SPEC or RIFF: 'vdiph/eei_3' 221: File not SPEC or RIFF: 'vwl_en_rp/e@' 229: File not SPEC or RIFF: 'vwl_en_rp/i@' 245: File not SPEC or RIFF: 'vwl_en_rp/oo' 261: File not SPEC or RIFF: 'vwl_en_rp/aU@' ______________________________ Phoneme Table: 'en_wm' include ph_english_wm 46: File not SPEC or RIFF: 'vowel/a_4' 63: File not SPEC or RIFF: 'vwl_en_wm/ii' 64: File not SPEC or RIFF: 'vowel/ii' 121: File not SPEC or RIFF: 'vwl_en_wm/aa' 146: File not SPEC or RIFF: 'vwl_en_wm/i' 180: File not SPEC or RIFF: 'vdiph/@u' 195: File not SPEC or RIFF: 'vdiph/Vu_2' 202: File not SPEC or RIFF: 'vdiph/ooi_3' 209: File not SPEC or RIFF: 'vdiph/@i_3' 216: File not SPEC or RIFF: 'vdiph/oi' ______________________________ Phoneme Table: 'af' include ph_af 11: File not SPEC or RIFF: 'vwl_af/@' 13: File not SPEC or RIFF: 'vwl_af/r@' 20: File not SPEC or RIFF: 'vowel/V_2' 27: File not SPEC or RIFF: 'vowel/e_mid2' 33: File not SPEC or RIFF: 'vwl_af/I' 41: File not SPEC or RIFF: 'vowel/oo_3' 55: File not SPEC or RIFF: 'vowel/uu_3' 62: File not SPEC or RIFF: 'vowel/ee_3' 63: File not SPEC or RIFF: 'l/L_eL_af' 80: File not SPEC or RIFF: 'vowel/aa_3' 87: File not SPEC or RIFF: 'vdiph/i at _2' 94: File not SPEC or RIFF: 'vowel/i_3' 102: File not SPEC or RIFF: 'vdiph2/o@' 109: File not SPEC or RIFF: 'vowel/y_3' 116: File not SPEC or RIFF: 'vdiph2/iu_3' 123: File not SPEC or RIFF: 'vdiph/Vu' 130: File not SPEC or RIFF: 'vdiph/ai_4' 138: File not SPEC or RIFF: 'vdiph/aai_2' 146: File not SPEC or RIFF: 'vdiph/@i_2' 154: File not SPEC or RIFF: 'vdiph/ooi_2' 162: File not SPEC or RIFF: 'vdiph/oi_2' 170: File not SPEC or RIFF: 'vdiph/ui_2' 178: File not SPEC or RIFF: 'vdiph/y#y_2' 186: File not SPEC or RIFF: 'vdiph2/y#@' 230: File not SPEC or RIFF: 'ufric/x2' ______________________________ Phoneme Table: 'cy' include ph_welsh 34: File not SPEC or RIFF: 'vowel/ii#' 41: File not SPEC or RIFF: 'vowel/oo_2' 48: File not SPEC or RIFF: 'vowel/u_bck' 97: File not SPEC or RIFF: 'vowel/o_2' 123: File not SPEC or RIFF: 'vdiph/ai_2' 165: File not SPEC or RIFF: 'vdiph2/iu_4' 193: File not SPEC or RIFF: 'vdiph/ui_3' ______________________________ Phoneme Table: 'de' include ph_german 11: File not SPEC or RIFF: 'vowel/@_3' 13: File not SPEC or RIFF: 'vwl_de/3' 30: File not SPEC or RIFF: 'vwl_de/r_a' 37: File not SPEC or RIFF: 'vowel/ee' 38: File not SPEC or RIFF: 'vwl_de/r_ee' 54: File not SPEC or RIFF: 'vowel/ii_2' 55: File not SPEC or RIFF: 'vwl_de/r_I' 70: File not SPEC or RIFF: 'vowel/oo' 78: File not SPEC or RIFF: 'vowel/uu_2' 79: File not SPEC or RIFF: 'vwl_de/r_U' 86: File not SPEC or RIFF: 'vowel/aa_6' 93: File not SPEC or RIFF: 'vowel/i_2' 109: File not SPEC or RIFF: 'vdiph/aau_2' 116: File not SPEC or RIFF: 'vdiph/ai_5' 138: File not SPEC or RIFF: 'vwl_de/r_e' 153: File not SPEC or RIFF: 'vwl_de/r_y' 160: File not SPEC or RIFF: 'vowel/yy_4' 188: File not SPEC or RIFF: 'ustop/ts' ______________________________ Phoneme Table: 'eo' include ph_esperanto 10: File not SPEC or RIFF: 'vowel/a_2' 18: File not SPEC or RIFF: 'vowel/a#' 69: File not SPEC or RIFF: 'vdiph/ai' ______________________________ Phoneme Table: 'fi' include ph_finnish 16: File not SPEC or RIFF: 'vowel/i_4' 24: File not SPEC or RIFF: 'vowel/ii_3' 47: File not SPEC or RIFF: 'vowel/aa' 54: File not SPEC or RIFF: 'vowel/aa#' 80: File not SPEC or RIFF: 'vowel/u_2' 86: File not SPEC or RIFF: 'vowel/uu_4' 114: File not SPEC or RIFF: 'vdiph/&i' 128: File not SPEC or RIFF: 'vdiph/eei_2' 135: File not SPEC or RIFF: 'vdiph/y#i' 149: File not SPEC or RIFF: 'vdiph/yi' 157: File not SPEC or RIFF: 'vdiph/aau' 164: File not SPEC or RIFF: 'vdiph/ou' 171: File not SPEC or RIFF: 'vdiph/eu_2' 178: File not SPEC or RIFF: 'vdiph2/iu_2' 186: File not SPEC or RIFF: 'vdiph/&y' 193: File not SPEC or RIFF: 'vdiph/eey' 200: File not SPEC or RIFF: 'vdiph/y#y' 207: File not SPEC or RIFF: 'vdiph2/iy' 215: File not SPEC or RIFF: 'vdiph2/uo' 222: File not SPEC or RIFF: 'vdiph2/ie' 229: File not SPEC or RIFF: 'vdiph2/y-y#' 300: File not SPEC or RIFF: 'ustop/p_unasp' 301: File not SPEC or RIFF: 'ustop/p_unasp_' 328: File not SPEC or RIFF: 'ufric/s_continue' 346: File not SPEC or RIFF: 'ufric/hu_fi' ______________________________ Phoneme Table: 'fr' include ph_french 16: File not SPEC or RIFF: 'vowel/@_2' 75: File not SPEC or RIFF: 'vowel/y_2' 96: File not SPEC or RIFF: 'vdiph/yi_fr' 192: File not SPEC or RIFF: 'vwl_fr/@R' 204: File not SPEC or RIFF: 'vwl_fr/@R2' ______________________________ Phoneme Table: 'fr_ca' include ph_french_ca 49: File not SPEC or RIFF: 'vowel/uu_bck' 56: File not SPEC or RIFF: 'vowel/yy' 62: File not SPEC or RIFF: 'vdiph/ae' ______________________________ Phoneme Table: 'nl' include ph_dutch 94: File not SPEC or RIFF: 'vdiph/ei' 137: File not SPEC or RIFF: 'vdiph2/yu' ______________________________ Phoneme Table: 'pl' include ph_polish 33: File not SPEC or RIFF: 'vowel/oo_4' 54: File not SPEC or RIFF: 'vnasal/ee_n2' 61: File not SPEC or RIFF: 'vnasal/oo_n2' 84: File not SPEC or RIFF: 'ustop/t_pzd' 107: File not SPEC or RIFF: 'x/d_pzd' 111: File not SPEC or RIFF: 'd/xd_pzd' 158: File not SPEC or RIFF: 'w/w2' ______________________________ Phoneme Table: 'ru' include ph_russian 180: File not SPEC or RIFF: 'vowel/o_5' 228: File not SPEC or RIFF: 'vowel/8' ______________________________ Phoneme Table: 'it' include ph_italian 98: File not SPEC or RIFF: 'vdiph2/iu' ______________________________ Phoneme Table: 'es' include ph_spanish ______________________________ Phoneme Table: 'pt' include ph_portuguese 9: File not SPEC or RIFF: 'vnasal/e_n' 15: File not SPEC or RIFF: 'vnasal/i_n' 22: File not SPEC or RIFF: 'vnasal/o_n' 28: File not SPEC or RIFF: 'vnasal/u_n' 34: File not SPEC or RIFF: 'vnasal/&_n' 40: File not SPEC or RIFF: 'vnasal/&u_n' 46: File not SPEC or RIFF: 'vnasal/oi_n' 121: File not SPEC or RIFF: 'vdiph/0i' 135: File not SPEC or RIFF: 'vdiph/eeu' 159: File not SPEC or RIFF: 'voc/Q_less' ______________________________ Phoneme Table: 'ro' include ph_romanian 13: File not SPEC or RIFF: 'vwl_ro/ii-' 15: File not SPEC or RIFF: 'vwl_ro/li' 16: File not SPEC or RIFF: 'vwl_ro/mi' 17: File not SPEC or RIFF: 'vwl_ro/ni' 37: File not SPEC or RIFF: 'vowel/i#_4' 50: File not SPEC or RIFF: 'vowel/@_low' 91: File not SPEC or RIFF: 'vdiph/ou_2' 99: File not SPEC or RIFF: 'vdiph/ii' 105: File not SPEC or RIFF: 'vdiph/i#i' 117: File not SPEC or RIFF: 'vdiph2/ea' 123: File not SPEC or RIFF: 'vdiph2/eo' 129: File not SPEC or RIFF: 'vdiph2/e[u' 135: File not SPEC or RIFF: 'vdiph2/oa' ______________________________ Phoneme Table: 'el' include ph_greek ______________________________ Phoneme Table: 'sv' include ph_swedish 29: File not SPEC or RIFF: 'vowel/e_2' 56: File not SPEC or RIFF: 'vowel/ee#_2' 64: File not SPEC or RIFF: 'vowel/y_5' 70: File not SPEC or RIFF: 'vowel/yy_3' 76: File not SPEC or RIFF: 'vowel/u#_2' 82: File not SPEC or RIFF: 'vowel/y#_2' 88: File not SPEC or RIFF: 'vowel/oe_4' 94: File not SPEC or RIFF: 'vowel/8_2' 102: File not SPEC or RIFF: 'vowel/a_5' 114: File not SPEC or RIFF: 'vowel/aa_4' 174: File not SPEC or RIFF: 'ufric/sx_sv' ______________________________ Phoneme Table: 'no' include ph_norwegian 15: File not SPEC or RIFF: 'vowel/@_hgh' 43: File not SPEC or RIFF: 'vowel/yy_2' 49: File not SPEC or RIFF: 'vowel/y_4' 55: File not SPEC or RIFF: 'vowel/oe_2' 61: File not SPEC or RIFF: 'vwl_no/y#' 88: File not SPEC or RIFF: 'vwl_no/&' 137: File not SPEC or RIFF: 'vwl_no/u#' 143: File not SPEC or RIFF: 'vwl_no/u#2' 152: File not SPEC or RIFF: 'vdiph/0i_2' 159: File not SPEC or RIFF: 'vdiph/ai_3' 181: File not SPEC or RIFF: 'vwl_no/y#y' 188: File not SPEC or RIFF: 'vwl_no/au-' ______________________________ Phoneme Table: 'vi' include ph_vi 10: File not SPEC or RIFF: 'envelope/p_level' 17: File not SPEC or RIFF: 'envelope/p_fall' 24: File not SPEC or RIFF: 'envelope/p_rise' 31: File not SPEC or RIFF: 'envelope/p_fallrise' 38: File not SPEC or RIFF: 'envelope/vi_5' 38: File not SPEC or RIFF: 'envelope/vi_5amp' 45: File not SPEC or RIFF: 'envelope/vi_6' 45: File not SPEC or RIFF: 'envelope/vi_6amp' 117: File not SPEC or RIFF: 'vowel/u_unr' 157: File not SPEC or RIFF: 'vdiph/@i' 205: File not SPEC or RIFF: 'vdiph/u-i' 267: File not SPEC or RIFF: 'vdiph2/u-@' ______________________________ Phoneme Table: 'hi' include ph_hindi 15: File not SPEC or RIFF: 'vowel/@_bck' 23: File not SPEC or RIFF: 'vowel/i_fnt' 30: File not SPEC or RIFF: 'vwl_hi/I' 37: File not SPEC or RIFF: 'vowel/e_3' 49: File not SPEC or RIFF: 'vdiph/ee-e' 69: File not SPEC or RIFF: 'vwl_hi/A' 88: File not SPEC or RIFF: 'vdiph/aaoo' 124: File not SPEC or RIFF: 'vwl_hi/r-voc' 131: File not SPEC or RIFF: 'vwl_hi/l-voc' 151: File not SPEC or RIFF: 'vdiph/aau_3' 329: File not SPEC or RIFF: 'ustop/t_short' ______________________________ Phoneme Table: 'qaa' include ph_test_qaa 21: File not SPEC or RIFF: 'envelope/p_214' 33: File not SPEC or RIFF: 'envelope/p_211' Refs 1454, Reused 874 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From s.bienlein at gmx.de Mon Jan 22 10:31:53 2007 From: s.bienlein at gmx.de (Simon Bienlein) Date: Mon, 22 Jan 2007 11:31:53 +0100 Subject: need some info about the alternative cd References: <0JC800JSGBGQ0Z50@vms046.mailsrvcs.net> Message-ID: <001301c73e10$896672e0$c864a8c0@simonlaptop> Hi, a couple of days ago, I installed Edgy Eft on my computer. I used the alternate install CD. When the start screen appeared, I pressed F6 and entered the following for my Braille display that is connected via a serial connection: install brltty=cb,ttyS0,de During the installation, I switched to a virtual console by pressing Alt+F2 and renamed the script /usr/lib/finish-install.de/50brltty to /usr/lib/finish-install.d/05brltty At the end of the installation, the brltty script also ran. At the restart, brltty was not started and after the login, Orca did not speak either. Simon From henrik at ubuntu.com Tue Jan 23 21:05:10 2007 From: henrik at ubuntu.com (Henrik Omma) Date: Tue, 23 Jan 2007 22:05:10 +0100 Subject: installing Ubuntu with X and no assistance In-Reply-To: <20070121091505.GD2524@starfish> References: <20070121091505.GD2524@starfish> Message-ID: <13408a8a0701231305l71fb9aa7l4026dd967f22e41d@mail.gmail.com> Hello, It works reasonably well ... if you have the patience to work around some of the warts. You can see a guide here: http://www.ubuntu.com/access/livecd Henrik On 1/21/07, Labrador wrote: > Hi, > > I'm new to this forum. > > A few months ago a sighted friend helped me with installing on his > demo-pc some Ubuntu distribution with Gnopernicus. > But should there be a way to do the same without any assistance ? > > Does the latest Ubuntu Edgy Eft come with Orca ? Or only Gnopernicus ? > > Any suggestions welcome. > Thanks. > > Greetings, > > Labrador > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > From gcasse at oralux.org Tue Jan 23 21:43:36 2007 From: gcasse at oralux.org (Gilles Casse) Date: Tue, 23 Jan 2007 22:43:36 +0100 Subject: Orca Urgent: Restoring Ubuntu? In-Reply-To: <20070123104857.GB29242@ubuntu> References: <20070123104857.GB29242@ubuntu> Message-ID: <17846.33160.533221.681688@gargle.gargle.HOWL> Hermann writes: > yesterday I upgraded Espeak. After completion Orca didn't speak correctly > anymore: Words or parts of words were not spoken. This post is also copied to the Ubuntu list. In eSpeak 1.18, the installed command line is named espeak instead of speak. So if you are using Speech Dispatcher, the related configuration file might be updated accordingly. Besides it, feedback on the gnome-speech driver for eSpeak is welcomed :-). Best regards, Gilles -- Oralux http://oralux.org From alpuzz at gmail.com Thu Jan 25 16:06:23 2007 From: alpuzz at gmail.com (Al Puzzuoli) Date: Thu, 25 Jan 2007 11:06:23 -0500 Subject: eSpeak is working on PPC! Message-ID: <003901c7409a$c39d84d0$6901a8c0@thinkpad> Thanks to Jonathan, eSpeak is now a viable option on the PPC architecture. I currently have it running on my Mac as the default synthesizer for Orca. Luke, Are you now able to compile phoneme data at your end? I thought you had devised a way to do this, but if you still need me to send the phoneme data, I'd be happy to do so. --Al -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsd at clara.co.uk Thu Jan 25 16:46:35 2007 From: jsd at clara.co.uk (Jonathan Duddington) Date: Thu, 25 Jan 2007 16:46:35 +0000 (GMT) Subject: eSpeak is working on PPC! In-Reply-To: <003901c7409a$c39d84d0$6901a8c0@thinkpad> References: <003901c7409a$c39d84d0$6901a8c0@thinkpad> Message-ID: <4eaad07ddcjsd@clara.co.uk> In article <003901c7409a$c39d84d0$6901a8c0 at thinkpad>, Al Puzzuoli wrote: > Thanks to Jonathan, eSpeak is now a viable option on the PPC > architecture. I currently have it running on my Mac as the default > synthesizer for Orca. > Luke, Are you now able to compile phoneme data at your end? I > thought you had devised a way to do this, but if you still need me to > send the phoneme data, I'd be happy to do so. Yes, Luke has also been helping me with this and he now has espeakedit running on his PPC. The makefile now includes a test for PPC and automatically defines a macro for the compilation, so the eSpeak programs know whether to swap the byte order when writing to the portaudio sound interface. Unless anyone tells me of any problems, I'll make a new release of eSpeak tomorrow, version 1.19, from which Luke can make packages. If anyone has any language data updates, please send them to me now. From Kwatson at smed.yi.org Sat Jan 27 13:21:10 2007 From: Kwatson at smed.yi.org (Keith Watson) Date: Sat, 27 Jan 2007 08:21:10 -0500 Subject: Term crashing in ubuntu feisty Message-ID: <20070127132110.GA1913@smed.yi.org> All, I am experiencing an issue with my terminals crashing in gnome. I have see a few threads with this being an issue, but have not seen any fixes or experienced any fixes with my upgrades. Can someone verify that they are indeed experiencing this same issue? I have it occurring on 3 different systems, so I don't think I should be the only one with these problems. Help! Keith -- Among the major impediments to discovery are not the ignorant but those with illusions of knowledge. - B. Alan Wallace From j-diggs at comcast.net Sat Jan 27 15:04:43 2007 From: j-diggs at comcast.net (Joanmarie Diggs) Date: Sat, 27 Jan 2007 10:04:43 -0500 Subject: Term crashing in ubuntu feisty In-Reply-To: <20070127132110.GA1913@smed.yi.org> References: <20070127132110.GA1913@smed.yi.org> Message-ID: <1169910283.26856.10.camel@pokey> Hi Keith, all. gnome-terminal in Feisty did have some crashing issues, not to mention some accessibility issues when using it with Orca. *As far as I can tell*, the crashes were fixed in the most recent release of VTE (0.15.2) http://ftp.gnome.org/pub/GNOME/sources/vte/0.15/vte-0.15.2.tar.gz If you are using it with Orca, you'll want the latest VTE from SVN trunk (svn co http://svn.gnome.org/svn/vte/trunk vte). Hope this helps! Joanie On Sat, 2007-01-27 at 08:21 -0500, Keith Watson wrote: > All, > > I am experiencing an issue with my terminals crashing in gnome. I > have see a few threads with this being an issue, but have not > seen any fixes or experienced any fixes with my upgrades. Can > someone verify that they are indeed experiencing this same issue? > I have it occurring on 3 different systems, so I don't think I > should be the only one with these problems. > > Help! > > Keith > > -- > Among the major impediments to discovery are not the ignorant > but those with illusions of knowledge. - B. Alan Wallace > From kenny at hittsjunk.net Sat Jan 27 15:51:14 2007 From: kenny at hittsjunk.net (Kenny Hitt) Date: Sat, 27 Jan 2007 09:51:14 -0600 Subject: Term crashing in ubuntu feisty In-Reply-To: <20070127132110.GA1913@smed.yi.org> References: <20070127132110.GA1913@smed.yi.org> Message-ID: <20070127155114.GA11418@mail.hittsjunk.net> Hi. I also have the problem. I sent Willy email with a way to always cause the crash, but none of his people seem to be having the same problem. I think I know what is happening, but I would like to compare notes with someone who isn't having the problem. Unfortunately, neither he or his people got back to me. Kenny On Sat, Jan 27, 2007 at 08:21:10AM -0500, Keith Watson wrote: > All, > > I am experiencing an issue with my terminals crashing in gnome. I > have see a few threads with this being an issue, but have not > seen any fixes or experienced any fixes with my upgrades. Can > someone verify that they are indeed experiencing this same issue? > I have it occurring on 3 different systems, so I don't think I > should be the only one with these problems. > > Help! > > Keith > > -- > Among the major impediments to discovery are not the ignorant > but those with illusions of knowledge. - B. Alan Wallace > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility From j-diggs at comcast.net Sat Jan 27 16:07:06 2007 From: j-diggs at comcast.net (Joanmarie Diggs) Date: Sat, 27 Jan 2007 11:07:06 -0500 Subject: Term crashing in ubuntu feisty In-Reply-To: <20070127155114.GA11418@mail.hittsjunk.net> References: <20070127132110.GA1913@smed.yi.org> <20070127155114.GA11418@mail.hittsjunk.net> Message-ID: <1169914026.26856.14.camel@pokey> Hi Kenny. If you build the latest version of VTE from svn trunk and are still having the problem, I would be happy to compare notes with you. Take care. Joanie On Sat, 2007-01-27 at 09:51 -0600, Kenny Hitt wrote: > Hi. > > I also have the problem. I sent Willy email with a way to always cause > the crash, but none of his people seem to be having the same problem. I > think I know what is happening, but I would like to compare notes with > someone who isn't having the problem. > Unfortunately, neither he or his people got back to me. > > Kenny > > > > On Sat, Jan 27, 2007 at 08:21:10AM -0500, Keith Watson wrote: > > All, > > > > I am experiencing an issue with my terminals crashing in gnome. I > > have see a few threads with this being an issue, but have not > > seen any fixes or experienced any fixes with my upgrades. Can > > someone verify that they are indeed experiencing this same issue? > > I have it occurring on 3 different systems, so I don't think I > > should be the only one with these problems. > > > > Help! > > > > Keith > > > > -- > > Among the major impediments to discovery are not the ignorant > > but those with illusions of knowledge. - B. Alan Wallace > > > > -- > > Ubuntu-accessibility mailing list > > Ubuntu-accessibility at lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > _______________________________________________ > gnome-accessibility-list mailing list > gnome-accessibility-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list From William.Walker at Sun.COM Sun Jan 28 19:34:48 2007 From: William.Walker at Sun.COM (Willie Walker) Date: Sun, 28 Jan 2007 14:34:48 -0500 Subject: Term crashing in ubuntu feisty In-Reply-To: <20070127155114.GA11418@mail.hittsjunk.net> References: <20070127132110.GA1913@smed.yi.org> <20070127155114.GA11418@mail.hittsjunk.net> Message-ID: <1170012888.7388.33.camel@ubuntu> Hi Kenny: We're not ignoring you. As a matter of fact, gnome-terminal issues such as the one you are seeing have been a primary focus for us and we've been directly engaged with the VTE team over the past few weeks. Sorry if you got the impression we didn't care. We do care. :-) Forward progress on the bug has only been made recently (a few days ago), so there really hasn't been much to report. Our hopes are to have the problems resolved by GNOME 2.18, due out in March. Please give the new VTE stuff a shot as Joanie suggests in a follow up to this message and let us know your experiences. Thanks! Will On Sat, 2007-01-27 at 09:51 -0600, Kenny Hitt wrote: > Hi. > > I also have the problem. I sent Willy email with a way to always cause > the crash, but none of his people seem to be having the same problem. I > think I know what is happening, but I would like to compare notes with > someone who isn't having the problem. > Unfortunately, neither he or his people got back to me. > > Kenny > > > > On Sat, Jan 27, 2007 at 08:21:10AM -0500, Keith Watson wrote: > > All, > > > > I am experiencing an issue with my terminals crashing in gnome. I > > have see a few threads with this being an issue, but have not > > seen any fixes or experienced any fixes with my upgrades. Can > > someone verify that they are indeed experiencing this same issue? > > I have it occurring on 3 different systems, so I don't think I > > should be the only one with these problems. > > > > Help! > > > > Keith > > > > -- > > Among the major impediments to discovery are not the ignorant > > but those with illusions of knowledge. - B. Alan Wallace > > > > -- > > Ubuntu-accessibility mailing list > > Ubuntu-accessibility at lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > _______________________________________________ > gnome-accessibility-list mailing list > gnome-accessibility-list at gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list From kb8aey at verizon.net Tue Jan 30 02:16:16 2007 From: kb8aey at verizon.net (mike coulombe) Date: Mon, 29 Jan 2007 20:16:16 -0600 (CST) Subject: having problems booting Message-ID: <0JCN003R0SZ3EPOF@vms048.mailsrvcs.net> Hi, two things. I got the latest feisty live CD and see the problem with it blowing up on the screen after choosing a keyboard type has been fixed. However I am having a problem with grub. I have two hard drives so the jumper settings may be the problem. Grub starts to load and gives a error 21. I have windows on one drive and oralux and ubuntu on the other. I got the same message after installing oralux. Also when I first installed windows it said there wasn't a compatible xp partition on the drive oralux and ubuntu are now on. However it showed the size and even was able to delete and create a partition. It just wouldn't use it. does anyone know what error 21 from grub means. Thanks Mike. X-Antivirus: avast! (VPS 000708-1, 01/29/2007), Outbound message X-Antivirus-Status: Clean From kb8aey at verizon.net Tue Jan 30 04:36:33 2007 From: kb8aey at verizon.net (mike coulombe) Date: Mon, 29 Jan 2007 22:36:33 -0600 (CST) Subject: need info on the live dvd Message-ID: <0JCN00GH2ZGVKDU0@vms042.mailsrvcs.net> Hi, what do you get on the live dvd that isn't on the live CD. Basically what I want to know is if the extra stuff on the dvd is for different types of installs, or if there are actually more programs in the menus when it is run as a live dvd. Mike. From 0905300097 at orangemail.sk Tue Jan 30 09:21:09 2007 From: 0905300097 at orangemail.sk (Lubos Pintes) Date: Tue, 30 Jan 2007 10:21:09 +0100 Subject: Ubuntu on Asus notebook Message-ID: <000301c7444f$fa898490$0b01a8c0@xy> Hello all, I tried the feisty live cd on my notebook. The sound is not functioning. The orca is not running "Cannot connect to display ...". I can only run the brltty from console. I have very good Internet connection, so downloading iso image is a matter of several minutes. I would like to help with testing but I have almost no experiences. Which information is needed? Where can I send it? How can I obtain it? Thank. From henrik at ubuntu.com Tue Jan 30 10:35:06 2007 From: henrik at ubuntu.com (Henrik Nilsen Omma) Date: Tue, 30 Jan 2007 11:35:06 +0100 Subject: Ubuntu on Asus notebook In-Reply-To: <000301c7444f$fa898490$0b01a8c0@xy> References: <000301c7444f$fa898490$0b01a8c0@xy> Message-ID: <45BF1F5A.1080500@ubuntu.com> Hi Lubos, I'm afraid Asus noteboks are not very well are not very well supported on Ubuntu at this point. If you want to debug this further, I suggest you look at the laptop testing pages: https://wiki.ubuntu.com/LaptopTesting and google for Ubuntu and your model number. Also see the ubuntu forums hardware and laptops section: http://www.ubuntuforums.org/forumdisplay.php?f=135 Others may have had the same problems. If you want to file bugs with useful log files you should look at pages like these: https://help.ubuntu.com/community/DebuggingXAutoconfiguration https://wiki.ubuntu.com/DebuggingHardwareDetection https://wiki.ubuntu.com/DebuggingACPI https://wiki.ubuntu.com/DebuggingKernelProblems Good luck sorting it out! Henrik Lubos Pintes wrote: > Hello all, > I tried the feisty live cd on my notebook. The sound is not functioning. The > orca is not running "Cannot connect to display ...". I can only run the > brltty from console. > I have very good Internet connection, so downloading iso image is a matter > of several minutes. I would like to help with testing but I have almost no > experiences. > Which information is needed? > Where can I send it? > How can I obtain it? > Thank. > > > From kb8aey at verizon.net Wed Jan 31 02:51:01 2007 From: kb8aey at verizon.net (mike coulombe) Date: Tue, 30 Jan 2007 20:51:01 -0600 (CST) Subject: live dvd Message-ID: <0JCP002P8P91CX41@vms048.mailsrvcs.net> Hi I downloaded the live dvd, but didn't see any different programs when running it as a live dvd. Are more programs installed when it is used for installing. There must be some reason for the extra size. Mike. From themuso at themuso.com Wed Jan 31 03:19:54 2007 From: themuso at themuso.com (Luke Yelavich) Date: Wed, 31 Jan 2007 14:19:54 +1100 Subject: live dvd In-Reply-To: <0JCP002P8P91CX41@vms048.mailsrvcs.net> References: <0JCP002P8P91CX41@vms048.mailsrvcs.net> Message-ID: <20070131031954.GA5575@themuso.com> On Wed, Jan 31, 2007 at 01:51:01PM EST, mike coulombe wrote: > Hi I downloaded the live dvd, > but didn't see any different programs when running it as a live dvd. > Are more programs installed when it is used for installing. > There must be some reason for the extra size. As far as I know, the live DVD also has the actual package files on the DVD as welll as the live image. This is to facilitate updates, as well as letting people try out Ubuntu before they install it. -- Luke Yelavich GPG key: 0xD06320CE (http://www.themuso.com/themuso-gpg-key.txt) Email & MSN: themuso at themuso.com Jabber: themuso at jabber.org.au -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From kb8aey at verizon.net Wed Jan 31 04:11:10 2007 From: kb8aey at verizon.net (mike coulombe) Date: Tue, 30 Jan 2007 22:11:10 -0600 (CST) Subject: lsr Message-ID: <0JCP00GT8SYMYVX9@vms044.mailsrvcs.net> Hi, I tried lsr on the computer I just put ubuntu on, and it still doesn't work. Has anyone else been able to get it to work in feisty. Is there another package I have to install to make it work. Mike. From kenny at hittsjunk.net Wed Jan 31 04:24:51 2007 From: kenny at hittsjunk.net (Kenny Hitt) Date: Tue, 30 Jan 2007 22:24:51 -0600 Subject: lsr In-Reply-To: <0JCP00GT8SYMYVX9@vms044.mailsrvcs.net> References: <0JCP00GT8SYMYVX9@vms044.mailsrvcs.net> Message-ID: <20070131042451.GA2786@mail.hittsjunk.net> Hi. On Tue, Jan 30, 2007 at 10:11:10PM -0600, mike coulombe wrote: > Hi, I tried lsr on the computer I just put ubuntu on, and it still doesn't work. > Has anyone else been able to get it to work in feisty. > Is there another package I have to install to make it work. > Mike. > I do have lsr working in Feisty, but I built it from source. Kenny From themuso at themuso.com Wed Jan 31 04:47:27 2007 From: themuso at themuso.com (Luke Yelavich) Date: Wed, 31 Jan 2007 15:47:27 +1100 Subject: lsr In-Reply-To: <20070131042451.GA2786@mail.hittsjunk.net> References: <0JCP00GT8SYMYVX9@vms044.mailsrvcs.net> <20070131042451.GA2786@mail.hittsjunk.net> Message-ID: <20070131044727.GA8131@themuso.com> On Wed, Jan 31, 2007 at 03:24:51PM EST, Kenny Hitt wrote: > I do have lsr working in Feisty, but I built it from source. Is that an official release, or from svn? -- Luke Yelavich GPG key: 0xD06320CE (http://www.themuso.com/themuso-gpg-key.txt) Email & MSN: themuso at themuso.com Jabber: themuso at jabber.org.au -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From kenny at hittsjunk.net Wed Jan 31 10:56:49 2007 From: kenny at hittsjunk.net (Kenny Hitt) Date: Wed, 31 Jan 2007 04:56:49 -0600 Subject: lsr In-Reply-To: <20070131044727.GA8131@themuso.com> References: <0JCP00GT8SYMYVX9@vms044.mailsrvcs.net> <20070131042451.GA2786@mail.hittsjunk.net> <20070131044727.GA8131@themuso.com> Message-ID: <20070131105649.GA3691@mail.hittsjunk.net> Hi. On Wed, Jan 31, 2007 at 03:47:27PM +1100, Luke Yelavich wrote: > > Is that an official release, or from svn? > -- > Luke Yelavich It is the CVS version. I haven't updated lsr to svn yet. Based on the dates in the Changelog, it was from 12/27/2006. Although I've tried it, I don't run it very often. It isn't as useful in gnome-terminal as Orca. Since I still use console apps for several things, I prefer Orca for daily screen reading use. Kenny From henrik at ubuntu.com Wed Jan 31 11:02:34 2007 From: henrik at ubuntu.com (Henrik Nilsen Omma) Date: Wed, 31 Jan 2007 12:02:34 +0100 Subject: Braille support testing Message-ID: <45C0774A.8030106@ubuntu.com> Hello folks, We are trying to improve out-of-the-box support for braille displays for Feisty with this spec: https://wiki.ubuntu.com/Accessibility/Specs/BrailleSupport From what I can tell, braille support on the Gnome desktop via Orca already works out of the box, using the braille monitor (on-screen graphical display for testing). However, since none of us in the devel team have an actual braille display we know little about the hardware side of it. After Herd 3 is out (this week) we want to switch back on general USB detection and deploy a script to assist with the configuration of serial displays. We would appreciate help with testing from anyone with a braille device, and esp. serial ones. The setup script on the wiki page above is also incomplete in that it needs the correct parameters for setting up brltty with the serial device. Any input is appreciated. Henrik From samuel.thibault at ens-lyon.org Wed Jan 31 13:39:49 2007 From: samuel.thibault at ens-lyon.org (Samuel Thibault) Date: Wed, 31 Jan 2007 14:39:49 +0100 Subject: Braille support testing In-Reply-To: <45C0774A.8030106@ubuntu.com> References: <45C0774A.8030106@ubuntu.com> Message-ID: <20070131133949.GD3478@implementation.labri.fr> Hi, Henrik Nilsen Omma, le Wed 31 Jan 2007 12:02:34 +0100, a écrit : > After Herd 3 is out (this week) we want to switch back on general USB > detection and deploy a script to assist with the configuration of serial > displays. We would appreciate help with testing from anyone with a > braille device, and esp. serial ones. For testing over serial cable, you could just use the TTY driver (tt), that lets you use another box with minicom. Samuel From 0905300097 at orangemail.sk Wed Jan 31 17:20:15 2007 From: 0905300097 at orangemail.sk (Lubos Pintes) Date: Wed, 31 Jan 2007 18:20:15 +0100 Subject: Braille support testing References: <45C0774A.8030106@ubuntu.com> Message-ID: <00cc01c7455c$12a2b7b0$0b01a8c0@xy> Hello, I reviewed the script, and didn't understand the u option. What is set there? I am using braille display compatible with Alva ABT. It is connected via pl2303 USB-to-serial converter which is supported by Linux. When I start brltty, I specify /dev/ttyUSB0 device. Is this the case? Or some other configuration option must be introduced for my situation? Thank.----- Original Message ----- From: "Henrik Nilsen Omma" To: Cc: "Colin Watson" ; "Dave Mielke" Sent: Wednesday, January 31, 2007 12:02 PM Subject: Braille support testing > Hello folks, > > We are trying to improve out-of-the-box support for braille displays for > Feisty with this spec: > https://wiki.ubuntu.com/Accessibility/Specs/BrailleSupport > > From what I can tell, braille support on the Gnome desktop via Orca > already works out of the box, using the braille monitor (on-screen > graphical display for testing). However, since none of us in the devel > team have an actual braille display we know little about the hardware > side of it. > > After Herd 3 is out (this week) we want to switch back on general USB > detection and deploy a script to assist with the configuration of serial > displays. We would appreciate help with testing from anyone with a > braille device, and esp. serial ones. > > The setup script on the wiki page above is also incomplete in that it > needs the correct parameters for setting up brltty with the serial > device. Any input is appreciated. > > Henrik > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility From Kwatson at smed.yi.org Wed Jan 31 20:13:11 2007 From: Kwatson at smed.yi.org (Keith Watson) Date: Wed, 31 Jan 2007 15:13:11 -0500 Subject: Dectalk Express in Ubuntu Fiesty Message-ID: <20070131201311.GA28043@smed.yi.org> All, I just upgraded to the 2.6.20-6 kernel in fiesty. I am still having the same issue with my dectalk express as before. The litetalk and the software synth both work fine. I am wondering against which package I should attempt to file a bug report? Any help on this would be greatly appreciated as I really miss the dectalk. Keith -- Among the major impediments to discovery are not the ignorant but those with illusions of knowledge. - B. Alan Wallace From themuso at themuso.com Wed Jan 31 21:38:28 2007 From: themuso at themuso.com (Luke Yelavich) Date: Thu, 1 Feb 2007 08:38:28 +1100 Subject: Dectalk Express in Ubuntu Fiesty In-Reply-To: <20070131201311.GA28043@smed.yi.org> References: <20070131201311.GA28043@smed.yi.org> Message-ID: <20070131213828.GA13402@themuso.com> On Thu, Feb 01, 2007 at 07:13:11AM EST, Keith Watson wrote: > All, > > I just upgraded to the 2.6.20-6 kernel in fiesty. I am still > having the same issue with my dectalk express as before. The > litetalk and the software synth both work fine. I am wondering > against which package I should attempt to file a bug report? Any > help on this would be greatly appreciated as I really miss the > dectalk. I have a dectalk express, and intend to try it later. I'll let you know how I go. -- Luke Yelavich GPG key: 0xD06320CE (http://www.themuso.com/themuso-gpg-key.txt) Email & MSN: themuso at themuso.com Jabber: themuso at jabber.org.au -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From henrik at ubuntu.com Wed Jan 31 21:47:48 2007 From: henrik at ubuntu.com (Henrik Nilsen Omma) Date: Wed, 31 Jan 2007 22:47:48 +0100 Subject: Debugging accessible GDM in Feisty -- please help Message-ID: <45C10E84.8090402@ubuntu.com> Hello all, We wrote a spec for feisty to add accessibility functionality to the login manager, GDM. https://wiki.ubuntu.com/Accessibility/Specs/AccessGDM This does not look like it will happen as no work has been done in Ubuntu or upstream on making the themed greeter (which everyone uses by default) accessible. The folks at SUN have made the old-style one work with Orca on Solaris. For me at least, even that still just breaks on Ubuntu Feisty. Has anyone tried getting this to work in Ubuntu? The Orca changelog for 2.17.4 suggests adding o 1 1000 10000 /bin/sh -c "GTK_MODULES=gail:atk-bridge ctrun -l child -i none orca -n -d main-window" to /etc/X11/gdm/modules/AccessKeyMouseEvents Has anyone tried this? If/when it breaks are there any useful log files produced? Henrik From david.bolter at utoronto.ca Fri Jan 19 19:59:03 2007 From: david.bolter at utoronto.ca (David Bolter) Date: Fri, 19 Jan 2007 19:59:03 -0000 Subject: Announcing GOK v1.2.1! Message-ID: <45B122F2.2050101@utoronto.ca> ============== * What is GOK? ============== GOK enables users to control their desktops without having to rely on a standard keyboard or mouse. It includes a suite of on-screen keyboards as well as dynamic keyboard generation. Please see http://www.gok.ca/ for details. ================================ * What's changed for GOK v1.2.1? ================================ * GOK now has optional libusb support! (see README.libusb) * GOK now runs "out of the box" on Ubuntu without crashing! * Many new translations. ===================== * Where can I get it? ===================== You can obtain GOK v1.2.1 in source code form here: http://download.gnome.org/sources/gok/1.2/gok-1.2.1.tar.gz best regards, The GOK Team Special thanks to Ben Konrath for the great libusb work!