For those struggling with this issue, a workaround is to call "texindy
-C utf8" or, if using imakeidx, using "\makeindex[options=-C utf8]"
(obviously, as long as your document is indeed utf8). Using
XeLaTex/LuaLaTeX also works, because both also force utf8.
--
You received this bug notification
Public bug reported:
When building the xindy-rules package, the file "make-
rules/inputenc/Makefile.in" uses grep to remove comment lines from
latin?.xdy files and concatenate them into latin.xdy. This fails because
gnu grep recognizes some of the files as binary and, instead of
outputting the
Public bug reported:
It seems that the mplayer build for trusty tahr has been compiled
without support for dvdnav. Since dvdnav support was included in
previous versions and since the changelog does not mention this change,
I assume this is a bug. This is mplayer version 2:1.1+dfsg1-0ubuntu3 .
It does not happen for me anymore with an up-to-date 12.04 ubuntu, but I
was unable to identify what solved the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942991
Title:
Really long
This happens to me when using startx, not when using lightdm. It also
happens if I try to start gnome-session over ssh. Right now I am on a
Oneiric machine, but I am pretty sure the same happens on Precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I cannot reproduce this in maverick anymore and, in fact, it resolved by
itself quite some time ago. I suppose it was on the upgrade to Lucid,
but I do not remember at all, sorry. I guess the bug may be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Server (running Xtightvnc) is karmic, client (running vinagre) is
maverick. I have the same problem, and XKL_XMODMAP_DISABLE=1 solves it.
There are lots of messages and bug reports on this since feisty,
including weird suggestions to disable gnome-session or set up an
invalid keymap.
--
You
Using an up-to-date Lucid with gwibber 2.30.0.1-0ubuntu1, I have the
same problem: I authenticate on facebook but cannot add. Tried the patch
from Toby Roworth (post #64) and got exactly the same error message as
Jorge Rubio on post #67.
Since some people had success with OpenDNS (not my case),
Yes, it is in my user's config; therefore, indeed it is not the default.
The file is dated 2008-03-28, however, so the behaviour did change by
itself on the switch to karmic. And in fact, the problem is not that the
keyring is locked (I would even argue that this should be the default,
but this is
This key is set to true; the key use_screensaver_settings is also set to
true. FWIW, /apps/gnome-screensaver/lock_enabled is also enabled.
Thanks for the attention!
--
gnome-keyring does not grant permissions automatically on resume
https://bugs.launchpad.net/bugs/454404
You received this bug
Uh? Please note:
1. I did not change this; it is the default value;
2. This did not happen in Hardy, Intrepid or Jaunty (and probably not
before either); the behaviour changed by itself on the upgrade to
karmic;
3. It is IMHO a good idea to lock the keyring on suspend, since it makes
a lot of
Public bug reported:
Binary package hint: gnome-keyring
When I log in, nm-applet connects automatically to my access point,
since the default keyring is unlocked on login and the WPA key is stored
there. But if I suspend the machine (to RAM) and then bring it back, I
get a prompt asking for my
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33860515/Dependencies.txt
--
gnome-keyring does not grant permissions automatically on resume
https://bugs.launchpad.net/bugs/454404
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Testing very lightly yet, I also believe I have Jean-Rémy's described
behaviour. Pidgin 2.5.5 in jauty.
--
Pidgin memory leak on Intrepid
https://bugs.launchpad.net/bugs/302132
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hi,
Unfortunately, I am not using the same laptop anymore, so I can't answer
for sure. I believe it has been fixed, but don't really remember, as
this problem didn't really bug me much. Since there are only two old
reports about it, I suggest closing the bug, if it resurfaces someone
will post it
Fixed here too, but I don't remember *when* it became fixed (I don't
reboot often and upgraded to Feisty during beta, so I don't know if the
fix appeared before or after the upgrade).
--
Problems with Alps touchpad after upgrade to Edgy
https://bugs.launchpad.net/bugs/69152
You received this bug
Hi,
I have a toshiba satellite M50 that suffers from the same problem on
edgy (this was upgraded from dapper, which worked flawlessly). X
thinks the trackpad is at event2 when it is, in fact, at event3.
Restarting X, or going to text mode and back, solves this. This is
version 0.14.6-0ubuntu3 of
Hi,
Same here, on a toshiba satellite M50, this didn't happen in dapper. I
also have the problem described in bug 23946 that didn't exist in dapper
too, maybe the two are related.
--
Edgy doesn't detect instantly like Dapper
https://launchpad.net/bugs/62361
--
ubuntu-bugs mailing list
Ok, I have ubuntu 6.10 here with not many different packages (quite a
few from universe, multiverse, etc, and w32codecs, flash etc, but
virtually nothing hand-compiled or taken from a completely alien
source).
Took the ubuntu source packages for amarok-1.4.1, compiled it, no FLAC.
Took the ubuntu
19 matches
Mail list logo
