Same here with Evince not being able to lauch the browser when you clic
on a link inside a PDF:
apparmor="DENIED" operation="capable"
profile="/usr/bin/evince//sanitized_helper" pid=16137 comm="chromium-
browse" capability=21 capname="sys_admin"
** Also affects: evince (Ubuntu)
Importance: Un
I confirm the Python scopes are now, after having applied the pygobject
update, working on a Xenial 64-bit system and still working (= no
regression) on a 32-bit one. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in
After having installed 2 identical VM (PXE + preseed), with the only
difference being the architecture (32-bit vs 64-bit), I can now confirm
that the Python scopes are working on a 32-bit install and crashing on a
64-bit install, with exactly the same requests made on both sides
(calc:1+1, man:calc
Not sure if this helps but it appears this problem only occurs on a
64-bit system. I did a Xenial 32-bit installation recently and the
Python scopes (I tested calc: and manpages:) worked properly. On a
Xenial 64-bit installation, even with the very last updates (especially
the recent libunity-core)
I would say this check-boxes display problem has been corrected in
poppler 0.10.3, available in Jaunty.
Ref.: https://bugs.freedesktop.org/show_bug.cgi?id=19359#c3
I am using Intrepid and I have just installed poppler 0.10.3 straight
from Jaunty (without even rebuilding since it's a new version n
Mhhh... Did I do something wrong when linking to Gnome bug tracking
system? Because first I didn't see the status change from Unknown to
New, and now the bug is solved (fixed) already on Gnome's side but it's
still shown as Unknown here. :-/
--
missing utf-8 input decoding in the Python Console p
Done and linked to this bug (correctly, I hope).
Thank you for having pointed that. :-)
Anything else to do?
** Bug watch added: GNOME Bug Tracker #558149
http://bugzilla.gnome.org/show_bug.cgi?id=558149
** Also affects: gedit via
http://bugzilla.gnome.org/show_bug.cgi?id=558149
Importan
** Description changed:
Binary package hint: gedit
+
+ Note: this bug is still present in Intrepid beta version.
Some friend found a problem with the Python Console plugin in gedit
2.22.3-0ubuntu1, coming with Ubuntu 8.04(.1).
When inputing some utf-8 encoded text, it's evaluated as
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/18224893/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/18224894/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/18224895/ProcStatus.txt
** Attachm
Public bug reported:
Binary package hint: gedit
Some friend found a problem with the Python Console plugin in gedit
2.22.3-0ubuntu1, coming with Ubuntu 8.04(.1).
When inputing some utf-8 encoded text, it's evaluated as a byte string
instead, meaning it's not decoded as it should and as it effect
I have remastered the Hardy beta LiveCD after having updated the gtk+2.0
package and I do confirm that VIQR is not anymore activated by default
for Vietnamese locale!
I have also installed the scim-m17n package to test m17n-db bugs
corrections and I do confirm that Telex is now working appropriate
Forgot to answer on one point to Sebastien Bacher:
This change is about disabling Vietnamese typing by default in GTK+,
independently of the distribution, so is suitable for upstream, IMHO.
But, we ask for this to be included in Hardy to help us promote Ubuntu
deployment using a LTS with alre
Answer to Sebstien Bacher:
Sorry for current delay in my answers: I'm currently busy working longer than
planed in Hồ Chí Minh City and have no time to do the requested test... Could
somebody else test it please?
But I'm not sure every Vietnamese people subscribed to this bug and
interested
(not sure about what is the exact meaning of "Fix Committed" in term of
bug management...)
** Changed in: m17n-db (Ubuntu)
Status: Fix Committed => In Progress
--
Bad default choices for Vietnamese installation
https://bugs.launchpad.net/bugs/191451
You received this bug notification beca
not really a scim problem, and a fixed has been done for m17n-db to get
a minimal working environment
** Changed in: m17n-db (Ubuntu)
Sourcepackagename: scim => m17n-db
Status: Confirmed => Fix Committed
--
Bad default choices for Vietnamese installation
https://bugs.launchpad.net/bugs/19
We could organize intensive testing for Vietnamese, but I'm afraid we
won't be able to test every single language provided by m17n-db... :-/
About the language-support-input-vi metapackage, I do confirm that
adding scim-m17n is enough and does work from Hardy Alpha 6 (I've just
tested it). It was
Thanks Ming Hua for you summary which is absolutely exact.
Your patch seems quite appropriate too, at least for the previous known GTK+
behavior.
Can somebody generate a .deb from this? Else I'll try through my PPA, but I'm
not sure to have time for this today...
--
Bad default choices for Viet
[More Hardy Alpha6 Vietnamese support tests]
It seems it's not exactly what I supposed... I see a strange GTK behavior here!
When running a gnome-terminal, the default GTK input method is "system" and
VIQR is *not* activated.
When running ubiquity, the default GTK input method is also "system" bu
Answer to Sebastien Bacher:
Problem summary:
When choosing some Vietnamese locale like "vi_VN", GTK is activating its VIQR
input method automatically (because of im-module hint) which leads to
unexpected typing (for most Vietnamese people, not used to this input method)
and even loss of charact
I've just tested Hardy Alpha6 and here are my comments about Vietnamese support:
- default keyboard is now US at boot, in Xorg and Ubiquity, thanks to Colin
Watson
- default GTK input method is "system" which still activate VIQR by default
because of the im-viqr.so im-module hint for "vi" environ
20 matches
Mail list logo
