Is anyone still seeing this om Gutsy. Removing dapper task as this is
not an SRU issue.
** Changed in: epiphany-browser (Ubuntu)
Target: dapper-updates = None
--
Epiphany Python extension functions are broken on amd64
https://bugs.launchpad.net/bugs/36538
You received this bug
Is this still happening on Gutsy? Removing dapper milestone.
** Changed in: gnome-power-manager (Ubuntu)
Target: dapper-updates = None
--
Shutdown from g-p-m doesn't use uspash
https://bugs.launchpad.net/bugs/35182
You received this bug notification because you are a member of Ubuntu
Confirmed in the upstream bugzilla (but found to be ubuntu specific). We
are having trouble getting a backtrace. Can apport help here?
** Changed in: gdm (Ubuntu)
Importance: Undecided = Medium
Status: New = Confirmed
Target: None = tribe-6
--
Accessible GDM broken with our
The fix for 'hominid' in gnome bug 465336 also fixes this bug in latest
gutsy for that word.
Please reopen this bug if you still see it crash with a different word
(and please cite it).
** Changed in: gnome-utils (Ubuntu)
Status: Incomplete = Fix Released
--
[apport] gnome-dictionary
Raising importance and setting milestone. This represents and access
regression in Gutsy.
** Changed in: gnome-panel (Ubuntu)
Importance: Low = Medium
Target: None = tribe-6
--
Visible/showing icons in Add to panel dialog should have both VISIBLE and
SHOWING states set
Raising importance and setting milestone. This represents and access
regression in Gutsy.
** Changed in: gnome-panel (Ubuntu)
Importance: Low = Medium
Target: None = tribe-6
--
AT-SPI implementation not delivering focus: events when navigating icons in
Add to panel dialog in
Joanie, is it the case that this worked as expected in Feisty?
** Changed in: gnome-panel (Ubuntu)
Status: New = Incomplete
Target: tribe-6 = None
--
Visible/showing icons in Add to panel dialog should have both VISIBLE and
SHOWING states set
Moving milestone.
** Changed in: hildon-thumbnail (Ubuntu)
Target: tribe-5 = tribe-6
--
build failure on lpia
https://bugs.launchpad.net/bugs/131255
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for glib2.0 in ubuntu.
--
Moving milestone.
** Changed in: hildon-desktop (Ubuntu)
Target: tribe-5 = tribe-6
--
build failure on lpia
https://bugs.launchpad.net/bugs/131255
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for glib2.0 in ubuntu.
--
This seems fixed in gutsy. I just tried the following:
rename ~/.gnome2/keyrings to ~/.gnome2/keyrings-0 and reboot.
Result: I get asked for the WEP authentication info and then asked to
create a keyring.
** Changed in: network-manager (Ubuntu)
Importance: Undecided = Low
Status:
** Changed in: hildon-desktop (Ubuntu)
Assignee: (unassigned) = Ubuntu Mobile and Embedded developers
** Changed in: hildon-thumbnail (Ubuntu)
Assignee: (unassigned) = Ubuntu Mobile and Embedded developers
--
build failure on lpia
https://bugs.launchpad.net/bugs/131255
You received
Bryce, assigning to you. We agreed we could fix this by removing the
static wacom entries I believe.
** Changed in: gdm (Ubuntu)
Assignee: (unassigned) = Bryce Harrington
Status: Confirmed = Triaged
--
Accessible GDM broken with our wacom setup
https://bugs.launchpad.net/bugs/83860
** Changed in: gnome-screensaver (Ubuntu)
Target: None = ubuntu-7.10-beta
--
[gutsy] booting after hibernation doesn't prompt for a password
https://bugs.launchpad.net/bugs/123080
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact
Public bug reported:
Pressing Ctrl+Alt+Tab shifts focus to the desktop or panel. There is no
obvious way to bring the focus back to your applications using just the
keyboard. (Pressing Ctrl+Alt+Left/Right is a workaround).
This is an accessibility problem for those who do not use a mouse, which
Hi,
I believe that error is described (and solved) here:
http://www.ubuntuforums.org/showthread.php?t=186890highlight=gok
Please also try SOK, which will be the default in Ubuntu 6.10:
https://wiki.ubuntu.com/Accessibility/Projects/SOK
- Henrik
--
On-screen keyboard (gok v1.0.7-0ubuntu3)
Public bug reported:
'at-spi_at-spi-registryd' crashes when trying to start an AT application
like gnopernicus.
See attached crash log
** Affects: at-spi (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
--
Crashes frequently
https://launchpad.net/bugs/56452
--
desktop-bugs
--
Crashes frequently
https://launchpad.net/bugs/56452
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Confirmed by Luke
** Summary changed:
- Crashes frequently
+ Edgy: at-spi Crashes frequently
** Changed in: at-spi (Ubuntu)
Status: Unconfirmed = Confirmed
--
Edgy: at-spi Crashes frequently
https://launchpad.net/bugs/56452
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Luke,
Do you have the problem described in
https://launchpad.net/distros/ubuntu/+source/gnome-panel/+bug/52405 ?
removing /etc/xdg/menus/debian-menu.menu is a fix described there, which seemed
to resolve both the panel problem and the at-spi problem for me.
--
Edgy: at-spi Crashes frequently
I can confirm this behaviour on the latest Edgy using totem-xine and
libxine-extracodecs. The scroll bar moves forward and the time is
advanced bit the actual playing returns to the very beginning. It works
fine with other mp3s.
** Changed in: xine-lib (Ubuntu)
Status: Unconfirmed =
It works as fine for me in Edgy. I have not installed any extra themes.
I'm closing this bug because it seems to work well in Edgy. -- when
closing I have a choice between 'Fix Released' and 'Rejected'. In this
case I'm choosing 'Rejected' because we are not aware of an actual match
that has
** Bug 49400 has been marked a duplicate of this bug
--
Unable to play 1 track
https://launchpad.net/bugs/49714
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
*** This bug is a duplicate of bug 49714 ***
On Edgy I am able to run Rhythmbox, totem-gstream and quod libet all at
once, playing three different songs at different volumes. Playlists seem
to work perfectly for all of them as well, starting the next song as it
should (I'm assuming this what the
This bug is looking difficult to reproduce as the reporter has made
changes to fstab, without it being clear what the defaults were or to
what extent Nautilus should be able to cope with such a changed
configuration. Please re-open if you can reproduce this issue on a
default install (preferably
Closing bug. It's been fixed upstream and a backport to Dapper is
unlikely. The bug has also not been confirmed on Ubuntu.
** Changed in: rhythmbox (Ubuntu)
Status: Needs Info = Rejected
--
Audioscrobbler issue
https://launchpad.net/bugs/50526
--
desktop-bugs mailing list
Hi igualeonte,
Are you able to provide any more information? I tried doing something
similar by copying a folder containing 1 text files from a USB disk
to the desktop. I did not see any major increase in memory usage. This
is on edgy.
--
resident memory of nautilus grows
I can confirm this on Edgy with abiword 2.4.5. Exact procedure to
reproduce:
* Open Abiword
* Type 'foo foo foo'
* Go to search/replace
* Type 'foo' in the search box and 'bar' in the replace box
* Hit FIND (it finds the first foo)
* Then hit REPLACE ALL
Expected result: 'bar bar bar'
Actual
I can confirm that *.flv files fail to play in totem on the latest Edgy.
ffmpeg and gstreamet0.10-ffmpeg are installed.
Google found this random flv for me: blip.tv/file/get/Roland-
VanVideoVerite119579.flv
It plays fine in VLC on the same system.
** Changed in: totem (Ubuntu)
Status:
Hello Riccardo,
Thanks for testing this. It is known to us that Orca does not behave
properly when started from the menu. The background for that is that as
a tool for blind people it was not designed to be launched from a menu.
We are currently testing some different solutions to this.
Yep, it seems easy to recover with Alt-Tab now (on Edgy). That's all we
need really. Several people reported it as a problem though and I did
test for it myself as well on Dapper, so unless I'm very mistaken it
must have been fixed in Gnome 2.16.
Marking as Fixed :)
** Changed in: gnome-panel
Sounds like a font ligatures issue.
I've tested evince with a file from the web http://xxx.lanl.gov/pdf
/astro-ph/0609120 which has been generated with Latex, in which the
'fi's look fine. I don't we can diagnose this further without a sample
file that shows the problem.
** Changed in: evince
I've tried playing this file with totem-gstreamer on Edgy and seeking
works fine here.
Aaron, do you have a chance to test this on Edgy (could be a Live CD)?
--
Totem-Gst cannot seek in file
https://launchpad.net/bugs/48992
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I find it useful to use vino on freshly installed systems, and even on
Live CDs -- there is an accessibility use case for this because it is
easier to activate vino than set up the ssh server. ssh-server is not
installed on those (for good reason).
Perhaps we could add a warning that the
It would be interesting to know if this also happens with an Upgrade
from Dapper to Edgy with the same hardware. In that case we should look
at fixing it in Edgy, but we are unlikely to fix it in Dapper. I'm
closing it now, but feel free to reopen if you can show it still happens
in a Dapper-Edgy
Public bug reported:
Orca is primarily designed with blind users in mind who tend to use
keyboard shortcuts for computer navigation. The only implemented way of
stopping Orca normally (other than 'killall orca') was with the Insert+q
keybinding. This is fine for blind users who prefer that, but
** Attachment added: Add quit button patch
http://librarian.launchpad.net/4197494/quitbutton.dpatch
--
Add a 'Quit Orca' button
https://launchpad.net/bugs/59531
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Attachment added: Apply and Cancel buttons patch
http://librarian.launchpad.net/4197495/apply_cancel.dpatch
--
Add a 'Quit Orca' button
https://launchpad.net/bugs/59531
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Public bug reported:
When starting Orca from the Gnome menus it would be best to start it
from in the gui setup mode so that average desktop users and
magnification users can see what is happening. Please change the
settings to do that (suggested patch will be attached).
Also, Orca should be
** Attachment added: change orca .desktop entry
http://librarian.launchpad.net/4197496/desktopguisetup.dpatch
--
Start Orca in --gui-setup mode from the menus
https://launchpad.net/bugs/59532
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Bug watch added: GNOME Bug Tracker #354689
http://bugzilla.gnome.org/show_bug.cgi?id=354689
** Also affects: gnome-desktop (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=354689
Importance: Unknown
Status: Unknown
--
Add a 'Quit Orca' button
** Attachment added: what the dialog looks like
http://librarian.launchpad.net/4201082/Screenshot-gnome-at-prefs.png
--
launch AT apps from gnome-at-prefs
https://launchpad.net/bugs/59553
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Attachment added: patch to add start buttons and check box
http://librarian.launchpad.net/4201085/34_at_properties_onboard_and_new_interface.patch
--
launch AT apps from gnome-at-prefs
https://launchpad.net/bugs/59553
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Public bug reported:
In order to avoid having the pre-installed AT (assistive technology)
apps appear in the applications menu we in the access team have
concluded that it would be most tidy to launch the applications and or
their settings dialogs from gnome-at-preferences. This is already the
Public bug reported:
Running OOo Calc with AT-SPI regularly causes Calc to crash.
Steps to reproduce:
* Enable Assistive Technology support in Gnome
* Log out and back in
* Open OOo Calc with a blank spreadsheet
* Create a column with number-value 5-6 items
* Use the sum symbol to create a
1.0.8 works fine for me on my dapper desktop, but I get nearly the same
error as him on the Live CD version.
[EMAIL PROTECTED]:~$ gok
GTK Accessibility Module initialized
Bonobo accessibility support initialized
/dev/js0: No such file or directory
The program 'gok' received an X Window System
I'm guessing this results from the change we made to the gok menu item
some weeks ago. Did you have dapper installed some time already? I
expect this would not happen on a fresh install because there the menu
entry never appears.
--
gok's applications menu entry does not get removed on uninstall
This still happens on the 20060518 Live CD which has gok
1.0.10-1ubuntu1.
--
On-screen keyboard (gok v1.0.7-0ubuntu3) fails
https://launchpad.net/bugs/42308
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Public bug reported:
It does start if I run it from the terminal, but I get these messages:
(process:6641): Gdk-CRITICAL **: gdk_window_set_title: assertion `title
!= NULL' f ailed
and
(srcore:6642): gnopernicus-WARNING * *: unknown text:line bouds type
-
It seems to start in a
The screenshots have been redone now.
** Changed in: example-content (Ubuntu)
Status: Confirmed = Fix Released
--
See Ubuntu in examples
https://launchpad.net/bugs/37727
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
*** This bug is a duplicate of bug 42308 ***
I have also seen this error on the Live CD, though GOK runs fine on my
desktop system.
Forum user 'ginn' seems to also have found the solution for it:
Comment out these lines:
Section InputDevice
Driver wacom
Identifier stylus
Option Device
This bug has been fixed and marked as RESOLVED upstream. Please see the
patch in Gnome bugzilla.
** Bug watch added: GNOME Bug Tracker #355583
http://bugzilla.gnome.org/show_bug.cgi?id=355583
** Also affects: gnome-mag (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=355583
This works fine on the latest Edgy live CD.
** Changed in: gnome-orca (Ubuntu)
Status: Unconfirmed = Fix Released
--
Start Orca in --gui-setup mode from the menus
https://launchpad.net/bugs/59532
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Changed in: gnome-orca (Ubuntu)
Importance: Undecided = Wishlist
Status: Unconfirmed = In Progress
--
Add a 'Quit Orca' button
https://launchpad.net/bugs/59531
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Orca does now start from the menu (though we will move it from there to
gnome-at-prefs)
** Changed in: gnome-orca (Ubuntu)
Status: In Progress = Fix Released
--
orca doesn't start
https://launchpad.net/bugs/58914
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Sorry for the long delay. Here is the strace.
** Attachment added: OOo/at-spi crash strace
http://librarian.launchpad.net/4535974/strace-oo.log.gz
--
Calc - AT-SPI causes crash
https://launchpad.net/bugs/58701
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
For Edgy we have moved to Orca, and any fixes here would not apply to
gnopernicus nor be backported to dapper.
** Changed in: gnopernicus (Ubuntu)
Status: Unconfirmed = Rejected
--
Fails to start automatically on Live CD 20060518
https://launchpad.net/bugs/45413
--
desktop-bugs
I haven't seen this on any edgy computers lately. Marking Fixed.
** Changed in: gnome-screensaver (Ubuntu)
Status: Needs Info = Fix Released
--
The screensaver fades twice
https://launchpad.net/bugs/35051
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I'm wondering if this might be a duplicate of
https://launchpad.net/distros/ubuntu/+source/xorg/+bug/58600
Galileon, could you try commenting out the wcom config lines as
explained in that bug, restrart and try again? Thanks!
--
gok doesn't work
https://launchpad.net/bugs/61656
--
My guess would be that the titlebar text is fine because it has a dark
shadow which enhances the contrast. The progressbar text which is white
on orange might be difficult to see for some.
I'm not sure if this represents a valid test, but I played with it a bit
in gimp, first making it grayscale
No apport does not pop up and of course when I run it with gdm it
refuses to crash :-/
However I do get warnings and lots of CRITICAL massages related to
AtkListener and XAccessibleContext that look highly relevant. See
attached gdm output.
** Attachment added: gdb output of soffice with at-spi
I can confirm it in Edgy using the PDF from the past. Attaching
screenshot. FWIW it looks exactly the same in Kpdf, but if imported
directly into Gimp it looks fine.
** Attachment added: letters not properly aligned
http://librarian.launchpad.net/4541649/Evince.png
--
In Ubuntu Dapper Beta
Thanks Mattias, I'm running that now and I'm no longer able to reproduce
the crash. I still get the fairly ugly wanrnings when running soffice
via gdb though (in case that's important):
** (soffice.bin:16550): WARNING **: ERROR: Event source does not implement
XAccessibleContext
**
No crashes for several days with your test version, nor with today's
update. Marking as fixed.
** Changed in: at-spi (Ubuntu)
Status: Fix Committed = Fix Released
--
Calc - AT-SPI causes crash
https://launchpad.net/bugs/58701
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I've not had any crashes after today's update. Anyone else? I've tried
to stress it a bit by killing and restarting it as well.
--
at-spi-registryd crash (please attach backtraces, check crash reports before)
https://launchpad.net/bugs/62446
--
desktop-bugs mailing list
Meh, spoke too soon. I just got the crash again :(
However, some observations: First there are two copies of at-spi-
registryd running in gnome, one as user and one as root. When I try tol
attach gdb to the user version PID I get a general Gnome freeze as Steve
says.
If I start KDE from GDM
I have some minor UI nits with their solution, but the main thing is
that they have added a quit button. I'm happy to sync with them and
propose further changes directly to upstream later.
--
Add a 'Quit Orca' button
https://launchpad.net/bugs/59531
--
desktop-bugs mailing list
for Edgy+1.
** Changed in: control-center (Ubuntu)
Assignee: Ubuntu Desktop Bugs = Henrik Nilsen Omma
Status: Needs Info = Confirmed
--
gnome accessibility: Messes up keyboard
https://launchpad.net/bugs/65920
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https
Targeted for 6.10. Please apply the second patch to just gray out the
start osk box.
** Changed in: control-center (Ubuntu)
Importance: Undecided = Medium
Status: Unconfirmed = Confirmed
Target: None = ubuntu-6.10
--
start osk at login only works with at-spi on in
Accessible login has not been properly tested on Ubuntu, and it seems to
be a topic that has gone a bit stale upstream in gnome as well.
There are instructions on getting it working here:
http://www.gnome.org/learn/access-guide/latest/sysadmin-27.html but they
are far from user friendly and
Marking this as Confirmed and as wishlist, since are really looking for
a Just Works version of accessible login, which has never existed. The
settings give the impression that it has, but that is misleading.
** Changed in: gdm (Ubuntu)
Importance: Medium = Wishlist
Assignee: Ubuntu
Hi,
Can you check if it is a duplicate of bug 58600 and if the xorg.conf
changes there resolves it?
Thanks.
--
gok crashes on launch
https://launchpad.net/bugs/67617
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Thanks for the clarification Colin. The fact that the link can be
manipulated from the shell suggests it is indeed a nautilus problem.
Reassigning.
** Changed in: example-content (Ubuntu)
Sourcepackagename: example-content = nautilus
--
Examples link in Home directory not removable
Setting to wishlist status. I agree with Daniel that it probably needs a
spec. The solution will be part technical but we also need real-world
discussions with the vendors of these voices to allow us to package
them, even if it is in the commercial repositories.
IBM seem to be on the right track
Accessibility bugs are often not like other bugs :)
Seb, I think you're right that it should be pulled in by the AT app, but
more importantly by Orca than by at-poke. Joanie first noticed the
problem when using the Orca screen reader which needs various GTK
applications to make some textual
Public bug reported:
Binary package hint: gdm
Just a few days after GOK has finally been fixed to deal with our wacom
tablet setup, it now turns out that it also breaks the accessible login.
If you go to the login screen setup window, select accessible login log
out, GDM breaks. Removing the
Some improvements have been made here. I can get accessible login to
work now but it requires some config changes in xorg.conf. I'll close
this as Fix Released as I've opened bug 83860 on the remaining issue.
** Changed in: gdm (Ubuntu)
Status: Confirmed = Fix Released
--
The greeter
This works fine for me in Feisty now. Upstream have made several
improvements in this area. Please re-open if you still see this on
Feisty.
One remaining quirk is that running 'orca --help' kills an existing Orca
session. I've asked on the list about this and will open a bug if it is
considered
Public bug reported:
In the 2.17.x series Orca upstream introduced an optional main window of
questionable usefulness. It's on by default, but can easily be switched
off with the '--disable=main-window' argument.
The less cluttered single preferences window would suit Ubuntu better.
We also
Chris, I think you touched this last :) Could you make the 2-line patch
for this?
** Changed in: control-center (Ubuntu)
Importance: Undecided = Low
Status: Unconfirmed = Confirmed
--
Please launch Orca with --disable=main-window
https://launchpad.net/bugs/84172
--
desktop-bugs
I cannot reproduce this on Feisty. Upstream have done a lot of stability
work so it's likely fixed. Please re-open if you see it again.
** Changed in: gnome-orca (Ubuntu)
Status: Needs Info = Fix Released
--
Crash on exiting orca.
https://launchpad.net/bugs/57535
--
desktop-bugs
I've seen this in the past but not recently. In any case it would be
related to starting at-spi, not Orca. We did have some at-spi-registryd
issues that have since been fixed, so i6t could be that. (I have seen
this more lately with turning on and off Beryl though :) )
Please re-open if you see
I can confirm this on Feisty, with both German and Spanish.
Carlos, Danilo: what is the next action item here? Do you need to fix
something in Rosetta or should I speak with upstream?
** Changed in: gnome-orca (Ubuntu)
Status: Unconfirmed = Confirmed
** Also affects: rosetta (upstream)
Yes, it looks like a general Gecko problem, now fixed for Firefox 3.
Mozilla don't seem to want yo backport it so we won't either. We should
start making builds of FF available somewhere though.
** Changed in: gnome-orca (Ubuntu)
Status: Unconfirmed = Rejected
** Changed in: firefox
John, even if it's not in universe/multiverse we could perhaps put the
deb on a server somewhere to download, or e could ask someone with an
existing third party repo like Luke or Sevaas to host it.
It could be great for a11y testing so we could give useful feedback to
the Mozilla devs while they
** Bug watch added: GNOME Bug Tracker #406803
http://bugzilla.gnome.org/show_bug.cgi?id=406803
** Also affects: gdm (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=406803
Importance: Unknown
Status: Unknown
--
Accessible GDM broken with our wacom setup
Public bug reported:
Binary package hint: gnome-themes
(as we discussed in Oslo)
High Contrast Inverse is the most useful. The others should be removed
from the default install.
One solution would be to move HCI to gnome-themes and not install the
accessibility themes pckage (with the
*** This bug is a duplicate of bug 58600 ***
Unfortunately yes, but it's fixed in Feisty with GOK 1.2.1. It is
unlikely that we will backport it officially to Edgy. It can be worked
around in Edgy by removing the wacom tablet support in xorg.conf.
--
[edgy] gok crash at startup
attached patch
** Attachment added: Quit button patch by Chris Jones
http://librarian.launchpad.net/6425869/01_settings_quit.dpatch
--
Add a 'Quit Orca' button
https://launchpad.net/bugs/59531
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Opening back up this old Orca bug from Edgy because we need to apply the
same change to Feisty again. Upstream made their own floating Quit
button solution which does not fit well with our presentation of these
things. Bug 84172 successfully removes that (Fix Released), but we need
to put our own
** Changed in: gnome-speech (Ubuntu)
Assignee: Accessibility = (unassigned)
--
Easy install of proprietary voice synthesizers
https://launchpad.net/bugs/82098
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Closing as fixed. We now use Orca as our main screen reader and it does
now have braille support. There are some remaining issues for Feisty,
but there are separate bugs filed.
** Changed in: gnopernicus (Ubuntu)
Status: Needs Info = Fix Released
--
No support for BRLTTY in Gnopernicus.
Hello,
Would you be able to test this with Feisty? Both AT-SPI and Evolution
have seen a range of bug fixes since 6.10. Thanks.
--
Crash when setting mensaje as read
https://launchpad.net/bugs/69453
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I cannot reproduce this on Feisty. Gustaf, have you tried?
I suspect we should do a review of how all these key shortcuts and
dialogs work.
--
slow key dialog not controllable by keyboard
https://launchpad.net/bugs/65921
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Just grabbing the upstream patch ...
** Attachment added: improve keyboard navigation
http://librarian.launchpad.net/6510390/a11y.patch
--
Feisty gnome control center not entirely accessible to screen reader.
https://launchpad.net/bugs/83951
--
desktop-bugs mailing list
Luke, are we still seeing this bug on Feisty with Orca? If not, let's
close it.
--
Gnopernicus crashes on exit.
https://launchpad.net/bugs/56585
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Hi BUGabundo,
Did you have accessible login enabled? Could you also attatch the
/var/log/syslog file? This may be related to bug 83860.
--
[apport] gdmgreeter crashed with SIGSEGV in XInternAtom() on feisty
https://launchpad.net/bugs/87039
--
desktop-bugs mailing list
There seems to be a problem with AT-SPI 1.7.13. I'm guessing it's due to
the changes introduced to allow it to work with sudo. If you force and
install of 1.7.12 bit works fine. See: https://lists.ubuntu.com/archives
/ubuntu-accessibility-devel/2006-November/75.html
** Changed in: at-spi
*** This bug is a duplicate of bug 67130 ***
** This bug is no longer a duplicate of bug 67082
[Edgy] Ubuntu Installer dont find /
** This bug has been marked a duplicate of bug 67130
mount points preparation locked - No root file system
--
Edgy RC Installation Problem
Public bug reported:
Binary package hint: gnome-mag
gnome-mag now has compositing super powers which greatly improves
performance, but it needs to be built with composite to work. Can this
be done? Thanks!
See: http://www.ubuntuforums.org/showthread.php?t=275118page=3 for more
info.
**
Our magnifier setup has seen many changes since 2005. Is anyone still
seeing this in Edgy or Feisty. If not we should close it as fixed.
--
gnome-mag not working
https://launchpad.net/bugs/20503
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
1 - 100 of 259 matches
Mail list logo
