Firefox: language packs / en_GB dictionary
by Joe Smith
Is it expected to have Firefox install support for dozens of languages?
Every time there's a FF update, I see a long delay and a dialog poops up
showing many language plugins are installed.
Also, somewhere along the line, FF has switched to the en_GB
dictionary/spelling check (based on which words it's marking). I have no
idea how that happened or how to get back to en_US.
> $ locale
> LANG=en_US.UTF-8
> LC_CTYPE="en_US.UTF-8"
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_PAPER="en_US.UTF-8"
> LC_NAME="en_US.UTF-8"
> LC_ADDRESS="en_US.UTF-8"
> LC_TELEPHONE="en_US.UTF-8"
> LC_MEASUREMENT="en_US.UTF-8"
> LC_IDENTIFICATION="en_US.UTF-8"
> LC_ALL=
Thanks for any ideas.
<Joe
16 years, 1 month
gdmflexiserver questions
by Reid Rivenburgh
Hi. I'm hoping someone out there knows the answer to this, or can
point me to some good docs. I'm trying to use gdmflexiserver to
handle a situation where there's one user always logged in (me) and
another that may log in occasionally. I found out about
gdmflexiserver, which generally works very well to "log me out",
locking the screen and managing things like audio. What it doesn't
seem to do, though, is turn the monitor off via DPMS when it starts a
new gdm login display. This may sound trivial, but I'm trying to keep
electricity use and costs down; I hate coming back to the machine
after a day and seeing the monitor still on!
It seems like the reason for it not working is because it's reusing
some existing display that has DPMS enabled, but when switching to it
from a different VT, it thinks the gdm display has already logically
turned the monitor off. If I hit a key, it restarts whatever timer
the DPMS uses, and then eventually the monitor will turn off. The
problem is that I'm not always there to hit a key, or I may forget to
hit a key.
Some questions:
1. Does the above hypothesis sound right?
2. What is the difference between "gdmflexiserver" and "gdmflexiserver
-s"? It sounds like the -s flag will make it start a new server,
which should solve the problem, but it doesn't seem to do that.
(Bonus points if you can explain "--monte-carlo-pi"!) At the moment,
it is definitely starting a new X server when I run gdmflexiserver -s;
it quickly shows the gdm greeter, than takes several seconds to
restart X. I don't know why it started doing that yesterday.
3. Is there any way to know which DISPLAY the gdmflexiserver started?
If I could query that, then maybe I could create a script that runs
gdmflexiserver, sleeps for awhile, and then does a "xset dpms force
off". I can't test it right now because of 2, but maybe that would
work regardless of the value of DISPLAY....
4. Do the /etc/gdm/Init/Default and related sibling directory scripts
get run when running gdmflexiserver? From my testing, it seems like
they don't, but this may be because it's reusing a display and
basically just switching VTs. But if there was a script I knew would
be run whenever gdmflexiserver does its thing, that would be nice.
5. I don't really understand what the "--command=" interface in
gdm/gdmflexiserver does. It seems anything I've put in there gives me
"no longer supported". That could be key to a solution, though.
6. xautolock, which checks for an idle X server and runs an arbitrary
command, stopped working correctly at some point, maybe when I
upgraded to F9 alpha from F8 (though I changed computers in there,
too). It never runs the idle program. Someone suggested (thanks)
using a dbus-based solution that does indeed work and is probably
fine, but I'm wondering why xautolock would never think the X server
is idle?
I've asked similar questions before, and in fact it seemed like this
was working until recently. Maybe an X update changed something? I'm
running the current rawhide and the open nv driver, if it matters.
Thanks for any pointers!
Reid
P.S. Apologies if this is too long, off-topic, or esoteric....
16 years, 1 month
NTFS fstab issues
by Gianluca Cecchi
On Wed, 07 May 2008 23:11:14 -0400 Christopher L Tubbs II wrote:
>/dev/sda2 /mnt/windows ntfs-3g defaults,users,noatime,sync,noauto 0 0
As I understand fstab syntax, the word "defaults" inside option column makes
sense only if it stands alone.
Otherwise it shouldn't be present at all. Try without it. I think its
effect could be to override the specific options ("users" in particular),
preventing normal user ownership.
But the point for not being able to mount I think is that ntfs-3g binary is
not suid....
Gianluca
16 years, 1 month
rawhide report: 20080508 changes
by Fedora compose checker
Updated Packages:
gpredict-0.9.0-3.fc9
--------------------
* Wed May 07 2008 Jesse Keating <jkeating(a)redhat.com> - 0.9.0-3
- Rebuild for file corruption
paraview-3.2.1-6.fc9
--------------------
* Wed May 07 2008 Jesse Keating <jkeating(a)redhat.com> - 3.2.1-6
- Rebuild for file corruption
Broken deps for ppc64
----------------------------------------------------------
livecd-tools-017-1.fc9.ppc64 requires yaboot
perl-Test-AutoBuild-darcs-1.2.2-3.fc9.noarch requires darcs >= 0:1.0.0
ppc64-utils-0.14-2.fc9.ppc64 requires yaboot
16 years, 1 month
Firefox 3 Beta 5
by Christopher L Tubbs II
Has anybody else noticed that firefox takes forever to close? It brings
up the "wait/force quit" dialog box in GNOME every time I close it. It
eventually closes, but it takes longer than I would expect.
Rainman
16 years, 1 month
rawhide (9-RC1) install report
by G.Wolfe Woodbury
Going on Jesse's statement that today's rawhide will be 9-RC1, I did a
full install of rawhide-20080507
Result: successful
Notes: I still can't make method= and stage2= work together correctly
during the install. If I only specify method=nfs:wolves.private:/path I
still get the loader taking the stage2 off of the boot.iso CD. (This
fails due to a flakey drive.) If I specify both method=nfs:... and
stage2=nfs:... the method is ignored in favor of some strange name
derived from the stage2= Fortunately I can switch to an http install.
I customized my software, trying among other things to eliminate the
texlive packages. To my suprize it came in as a result of selecting
xdvik! TeX is not the only thing that generates dvi. groff also
generates dvi and xdvik should not require (imo) texlive.
NetworkManager is still not very friendly to wired only networks, but it
seems to be getting better.
Kudos to everyone for getting 9 whipped into shape so well.
--
G.Wolfe Woodbury
16 years, 1 month
NTFS fstab issues
by Christopher L Tubbs II
Ok, I'm having some issues with mounting an ntfs partition in fstab.
Perhaps I am just doing something wrong, and maybe somebody here can
tell me what it is, before I file a bug report...
The following line mounts perfectly as root, but will not work as a
normal user:
/dev/sda2 /mnt/windows ntfs-3g defaults,users,noatime,sync,noauto 0 0
The command I'm using from the command line both as root and as normal
user is: mount /dev/sda2
Permissions on /mnt/windows is rwx for everybody. It also doesn't matter
if I specify the type to be ntfs, ntfs-3g, or auto. Nor does it matter
if I have the defaults option prior to the others or not.
On a side note, I've noticed that the verbose flag for mount does
nothing, unless I mount as type "auto", then it only says a "I will try
ntfs" message (this message appears as both root and normal user).
Shouldn't it show some messages when it fails?
Rainman
16 years, 1 month
Menu entries in Gnome
by Dejan Čabrilo
Hey all,
I've been testing Fedora 9 for a while now, and I came to notice a bit
silly organization of GNOME menu entries. Perhaps I should report this
as a sort of a bug?
1) Authorizations (polkit-gnome-authorization), Power Management
(gnome-power-preferences) and Software Updates (gpk-prefs) reside in
System/Preferences/System.
First of all, this is a problem because of two "System" menu names.
Also, I think it would make more sense to put them in
System/Administration.
2) Qt3 Config (qtconfig) and Qt4 Config (qtconfig-qt4) are both in
System/Preferences. They are the only entries, at least on my system,
that reside in the top of Preferences. It would make more sense to put
them in System/Preferences/Look and Feel
3) There are other weird things about menu entries that I see..
Namely, why do we have both Main menu/System tools, and
System/Administration, or why is Keyboard Shortcuts in Personal and
not Look and Feel. However, these should be addressed upstream to
GNOME, right?
Dejan
16 years, 1 month
GDM Greeter
by Christopher L Tubbs II
What does everybody think of the new greeter?
Personally, I have issues with it:
1) suspend option remains, even after disabling suspend globally via
gconf-editor (bug already reported, and apparently patch has already
been committed upstream)
2) I can't seem to configure my "face" image. Putting a ".face" graphic
in my home directory doesn't work, nor does configuring image with
System->Preferences->Personal->About Me.
3) Why is there an animation between clicking my name and typing my
password?!?! Even Windows XP welcome screen is better than this! I want
to log in NOW, not when the animation is complete.
4) Where the hell are the login screen settings? This is a serious
oversight. I had thought the greeter configuration was supposed to be
EASIER than previous releases (I can't remember where I read that, but
for some reason I was expecting it).
5) It's ugly.
Anybody else have thoughts on the Fedora 9 pre-release greeter?
Rainman
16 years, 1 month
Re: [g-a-devel] [gdm-list] What's the Status of Audio in GDM?
by Janina Sajka
Hi, Brian:
Brian Cameron writes:
>
> Chuck:
>
> > I've done some testing of accessibility support on GDM, specifically
> > the screen reader and audio output, on Fedora 9.
> >
> > On Wed, May 07, 2008 at 10:13:06AM -0400, Janina Sajka wrote:
> >> What is the plan for SoundOnLogin=true ? Is it coming back? Should I
> >> just be patient?
> >
> > I don't know about that option, however I do have sound working on my
> > GDM login screen. Orca starts up automatically.
You have Orca starting during GDM? I would like to set that up. If
you're achieving it via Ctrl-S, it isn't working that way for me yet. If
some other mechanism, I'd really appreciate a pointer.
>
> The feature was to provide 3 sounds at various points in the login
> process:
>
> 1. When the login screen is ready for input
> 2. On failed login
> 3. On successful login
>
Yes, yes. Just as of this morning this is also working for me on two
machines. Seems to have come on line with the push of
gnome-audio-2.22.2.
And a very elegant logo audio /usr/share/sounds/startup3.wav is! I would
venture it's the classiest yet from Gnome!
I should note, though, that it's only sounding on my laptop because I
have a spare audio device--which happens to be the third audio device.
While I can aplay -D hw:0 (or hw:1), the playing of this sound comes
over hw:2 for some reason. I'm not sure why, and that gives me the
concern that many users might miss it if something else has taken
the only audio device available.
In my case hw:0 is taken by Speakup (the console screen reader) driving
TTSynth (http://ttsynth.com). I have to pull off a little trick to make
sure that other sounds can still play over hw:0, but I have that
covered.
A console twinkle voip phone is running over hw:1. I don't know why
startup3.wav won't play there, and would like to know, actually.
> The previous GDM allowed you to configure whether the above 3 sounds
> would be played, and allowed you to configure what soundfile would be
> played for each.
>
> This allows users who are blind to navigate the login process without
> needing to use orca or to know how to launch orca. Since, in the
> normal use-case, a user just enters their username and password, it
> isn't really necessary to provide full orca feedback to navigate this
> most common use-case. Orca is really only needed if the user wants to
> navigate the GUI to do other use-cases like change the language, change
> the session, use the XDMCP chooser, etc.
>
It's still a good idea to have Orca available. For one thing that
competing OS from the U.S. West Coast does that. For another, even
something as simple as Login, <enter> passwd, <enter> can go awry
without feedback. It has for me, and I'm pretty on top of things. Yet,
my password shows up in my logs sometimes, because, for some reason,
I've gotten out of sync. Maybe the phone rang and I inadvertently
pressed <enter> without realizing it? Now I'm entering my password in
the login field without knowing it. If Orca where there speaking, I'd be
hearing the chars echo'd, and would immediately stop typing them and
clear my entry with backspace. But, without Orca, I'm assuming, and
sometimes getting it wrong.
> However, now that GDM has the Face Browser on by default, it might
> not be possible for blind users to easily navigate the login process
> without Orca anymore. Though perhaps a hotkey could be added to
> allow the username entry field to become available so that a blind
> user could avoid having to use the face browser. For most blind
> users, the Face Browser is a distraction and makes the login process
> more cumbersome.
>
> It might be reasonable to avoid supporting these sound prompts if it is
> possible for blind users to launch orca from the login screen via a
> keybinding, and if GDM works well enough with orca that a blind user can
> navigate the login screen without needing these sound prompts.
>
> However, without the sound alerting the user when GDM is ready for
> input, a blind user would have to guess when to hit the hotkey to
> start orca, which is a bit ugly. I can imagine if the bootup
> process had a problem, a blind user might wait a long time before
> realizing that GDM is not showing up.
>
Exactly. we need to know to start typing--or navigating.
May I make an additional rfe in this regard? The Ctrl-S gesture requires
that one hold the combination for some period of time. My experience
when this was working for me--back with Fedora 7--was that the exact
amount of time could vary by several seconds actually. I guess it
depended on what other pids were keeping the hd busy?
So, my RFE -- Could we have a very brief sound when Ctrl-S actually
engages? So we know when it's OK to let go? Else one can hold them too
long and miss the functionality only to become frustrated.
I am thinking of something very simple an inocuous like
/usr/share/sounds/pop.wav ? From an audio interface point of view I
think this would be quite elegant and certainly functional.
Janina
> Brian
> _______________________________________________
> Gnome-accessibility-devel mailing list
> Gnome-accessibility-devel(a)gnome.org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
--
Janina Sajka, Phone: +1.202.595.7777; sip:janina@a11y.org
Partner, Capital Accessibility LLC http://CapitalAccessibility.Com
Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada
Learn more at http://ScreenlessPhone.Com
Chair, Open Accessibility janina(a)a11y.org
Linux Foundation http://a11y.org
16 years, 1 month
