Your message dated Mon, 04 Aug 2014 15:49:32 +0200
with message-id <1407160172.16578.3.camel@shepard>
and subject line Re: Rhythmbox is reacting very slowly when accessibility 
support is enabled
has caused the Debian Bug report #675241,
regarding Rhythmbox is reacting very slowly when accessibility support is 
enabled
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
675241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675241
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rhythmbox
Version: 2.96-5
Severity: important

Hi,

I've recently started Orca by accident. Upon startup, Orca automatically
sets "org.gnome.desktop.interface.toolkit-accessibility" to "true" [0].
After a lot of trial-and-error I discovered that this setting was the
reason why Rhythmbox was suddenly reacting *very* slowly. Please take a
look a these numbers:

                          | value == false | value == true
-------------------------------------------+--------------
Rhythmbox startup         |     < 1 second |  ~ 10 seconds
Searching for an album    |     < 1 second |   ~ 3 seconds
Clearing the search field |     < 1 second |   ~ 5 seconds

These times were measured with a database containing ~ 4000 songs. With
a bigger database the effect is much more dramatic - Rhythmbox is
basically unusable there (startup alone takes several minutes).

I don't think the accidental launch of one application should make
another application unusable without even telling the user what the
problem is.

Best regards

Alexander Kurtz

[0] I guess doing this directly after startup without first asking the 
    user is not perfect, but I can understand the rationale behind this 
    decision.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message ---
Version: 3.0.3-1

Hi,

I just tested Rhytmbox 3.0.3-1 with a database containing > 30000 songs
and "org.gnome.desktop.interface.toolkit-accessibility" set to "true"
and everything worked fine. I'm therefore closing this bug now.

Best regards

Alexander Kurtz

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---

Reply via email to