[Fedora-i18n-bugs] [Bug 608653] New: gettext package has unnecessary dependency on CVS on x86_64
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: gettext package has unnecessary dependency on CVS on x86_64
https://bugzilla.redhat.com/show_bug.cgi?id=608653
Summary: gettext package has unnecessary dependency on CVS on
x86_64
Product: Fedora
Version: rawhide
Platform: x86_64
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: gettext
AssignedTo: petersen(a)redhat.com
ReportedBy: mathepic(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: petersen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
Description of problem: On x86_64 systems, the "gettext" package requires
"CVS". This does not occur on i686.
Version-Release number of selected component (if applicable):
0.17-16.2.fc13
How reproducible:
Easy to reproduce, assuming you have an x86_64 machine.
Steps to Reproduce:
1. Su to root
2. Update system with "yum update" (may need --skip-broken)
3. Attempt to remove CVS
Actual results:
Many packages depend on CVS indirectly or directly, like policycoreutils.
Except for gettext, all the other packages depend on CVS because they depend on
gettext.
Expected results:
CVS shouldn't be a dependency of gettext.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
14 years
[Fedora-i18n-bugs] [Bug 598289] Unicode character input not available by default
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=598289
--- Comment #14 from Simos Xenitellis <simos.bugzilla(a)gmail.com> 2010-06-30 10:17:11 EDT ---
(In reply to comment #13)
> (In reply to comment #11)
> > This will set the default for every user account on the system, right?
>
> Yes, it effects every user.
>
> >
> > Obviously, uninstalling xim means that no user on the system can use xim, but I
> > suppose the ibus input methods will still be available, correct?
>
> Yes, GTK_IM_MODULE=xim uses im-xim.so and GTK_IM_MODULE=ibus uses im-ibus.so so
> if you uninstall xim, ibus is still available.
>
> > Sorry, this method does not seem to work: I could not see that environment
> > variable from a gnome-terminal shell and gtk+ applications did not provide the
> > C-S-u input method.
>
> OK, I confirmed it works below.
>
> % cat $HOME/.xinputrc
> XIM=none
> XIM_PROGRAM=
> XIM_ARGS=
> GTK_IM_MODULE=gtk-im-context-simple
> QT_IM_MODULE=xim
> IMSETTINGS_IGNORE_ME=yes
> DISABLE_IMSETTINGS=yes
>
> > 1) What is the standard configuration going to be for Fedora users in locales
> > that use the Latin alphabet, like en_US. Will an input method be part of the
> > standard configuration or not? If no input method is installed, will
> > gtk-im-context-simple be used or not?
>
> AFAIK, many European people like to use compose keys so probably xim is more
> useful than gtk-im-context-simple.
gtk-im-context-simple supports (the vast majority) of the compose sequence that
are available with XIM.
> Yes, if you uninstall IM modules in /usr/lib*/gtk-2.0/../immodules,
> gtk-im-context-simple will be used.
> If you don't set GTK_IM_MODULE, /etc/gtk-2.0/*/gtk.immodules decide the default
> module.
> ibus-daemon runs on Asian locales by default.
If the variable GTK_IM_MODULE is not set, then GTK+ selects by default
gtk-im-context-simple.
>
> (In reply to comment #12)
> > That is, is it possible to have ISO 14755 functionality in IBus that works
> > under all IBus input methods? Does IBus allow this feature?
>
> One idea might be to add features in ibus-rawcode.
> - Disable lookup window option
> - Auto disable engine option
>
> It means you'll use Ctrl+Space instead of Ctrl+Shift+u by default while the
> trigger key can be customized with ibus-setup.
>
> If we try to implement Ctrl+Shift+U in ibus-daemon, probably we developers need
> further discussions internally.
It would be good if this could go forward. Then Fedora and other distributions
could claim ISO 14755 support.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
14 years
[Fedora-i18n-bugs] [Bug 575752] New: [abrt] crash in w3m-0.5.2-15.fc12: Process /usr/bin/w3m was killed by signal 11 (SIGSEGV)
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: [abrt] crash in w3m-0.5.2-15.fc12: Process /usr/bin/w3m was killed by signal 11 (SIGSEGV)
https://bugzilla.redhat.com/show_bug.cgi?id=575752
Summary: [abrt] crash in w3m-0.5.2-15.fc12: Process
/usr/bin/w3m was killed by signal 11 (SIGSEGV)
Product: Fedora
Version: 12
Platform: x86_64
OS/Version: Linux
Status: NEW
Status Whiteboard: abrt_hash:94f636b14840fae853fa53bf99ab456456010f28
Severity: medium
Priority: low
Component: w3m
AssignedTo: pnemade(a)redhat.com
ReportedBy: rbinkhor(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: pnemade(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
abrt 1.0.8 detected a crash.
architecture: x86_64
Attached file: backtrace
cmdline: w3m -o indent_incr=0 -o multicol=false -o no_cache=true -o
use_cookie=false -o display_charset=utf8 -o system_charset=utf8 -o
follow_locale=false -o use_language_tag=true -o ucs_conv=true -T text/html
-dump
/home/rbinkhorst/buildroot/BUILD/xulrunner-1.9.0.10/mozilla/layout/generic/crashtests/323386-1.html
comment: No idea, it popped up in ABRT
component: w3m
executable: /usr/bin/w3m
kernel: 2.6.32.9-70.fc12.x86_64
package: w3m-0.5.2-15.fc12
rating: 4
reason: Process /usr/bin/w3m was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
14 years
[Fedora-i18n-bugs] [Bug 594707] New: [abrt] crash in w3m-0.5.2-15.fc12: raise: Process /usr/bin/w3m was killed by signal 6 (SIGABRT)
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: [abrt] crash in w3m-0.5.2-15.fc12: raise: Process /usr/bin/w3m was killed by signal 6 (SIGABRT)
https://bugzilla.redhat.com/show_bug.cgi?id=594707
Summary: [abrt] crash in w3m-0.5.2-15.fc12: raise: Process
/usr/bin/w3m was killed by signal 6 (SIGABRT)
Product: Fedora
Version: 12
Platform: i686
OS/Version: Linux
Status: NEW
Status Whiteboard: abrt_hash:d106ee41a2e44b3f3c0024b24e471d3fd09e8baa
Severity: medium
Priority: low
Component: w3m
AssignedTo: pnemade(a)redhat.com
ReportedBy: theo148(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: pnemade(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
abrt 1.0.9 detected a crash.
architecture: i686
Attached file: backtrace
cmdline: w3m -o indent_incr=0 -o multicol=false -o no_cache=true -o
use_cookie=false -o display_charset=utf8 -o system_charset=utf8 -o
follow_locale=false -o use_language_tag=true -o ucs_conv=true -T text/html
-dump /home/antiaircraft/Archives/php-bigxhtml.html
comment: I'm pretty sure this crash happened when I moved a large HTML file
(the extracted single-page PHP manual) while Tracker was using w3m to index it.
I haven't been able to reproduce the crash however.
component: w3m
crash_function: raise
executable: /usr/bin/w3m
global_uuid: d106ee41a2e44b3f3c0024b24e471d3fd09e8baa
kernel: 2.6.32.12-115.fc12.i686
package: w3m-0.5.2-15.fc12
rating: 4
reason: Process /usr/bin/w3m was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
14 years
[Fedora-i18n-bugs] [Bug 599314] New: [abrt] crash in w3m-0.5.2-15.fc12: Strnew_size: Process /usr/bin/w3m was killed by signal 11 (SIGSEGV)
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: [abrt] crash in w3m-0.5.2-15.fc12: Strnew_size: Process /usr/bin/w3m was killed by signal 11 (SIGSEGV)
https://bugzilla.redhat.com/show_bug.cgi?id=599314
Summary: [abrt] crash in w3m-0.5.2-15.fc12: Strnew_size:
Process /usr/bin/w3m was killed by signal 11 (SIGSEGV)
Product: Fedora
Version: 12
Platform: i686
OS/Version: Linux
Status: NEW
Status Whiteboard: abrt_hash:f5052578a2f01c7b22c86c9657b868fb91922649
Severity: medium
Priority: low
Component: w3m
AssignedTo: pnemade(a)redhat.com
ReportedBy: theo148(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: pnemade(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
abrt 1.0.9 detected a crash.
architecture: i686
Attached file: backtrace
cmdline: w3m -o indent_incr=0 -o multicol=false -o no_cache=true -o
use_cookie=false -o display_charset=utf8 -o system_charset=utf8 -o
follow_locale=false -o use_language_tag=true -o ucs_conv=true -T text/html
-dump '/home/antiaircraft/Archives/Documentation and
Manuals/php_manual_en-bigxhtml.html'
comment: This crash occurred while Tracker was indexing. I haven't been able to
reproduce it.
component: w3m
crash_function: Strnew_size
executable: /usr/bin/w3m
global_uuid: f5052578a2f01c7b22c86c9657b868fb91922649
kernel: 2.6.32.12-115.fc12.i686
package: w3m-0.5.2-15.fc12
rating: 4
reason: Process /usr/bin/w3m was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
14 years
[Fedora-i18n-bugs] [Bug 598289] Unicode character input not available by default
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=598289
--- Comment #13 from fujiwara <tfujiwar(a)redhat.com> 2010-06-30 06:03:08 EDT ---
(In reply to comment #11)
> This will set the default for every user account on the system, right?
Yes, it effects every user.
>
> Obviously, uninstalling xim means that no user on the system can use xim, but I
> suppose the ibus input methods will still be available, correct?
Yes, GTK_IM_MODULE=xim uses im-xim.so and GTK_IM_MODULE=ibus uses im-ibus.so so
if you uninstall xim, ibus is still available.
> Sorry, this method does not seem to work: I could not see that environment
> variable from a gnome-terminal shell and gtk+ applications did not provide the
> C-S-u input method.
OK, I confirmed it works below.
% cat $HOME/.xinputrc
XIM=none
XIM_PROGRAM=
XIM_ARGS=
GTK_IM_MODULE=gtk-im-context-simple
QT_IM_MODULE=xim
IMSETTINGS_IGNORE_ME=yes
DISABLE_IMSETTINGS=yes
> 1) What is the standard configuration going to be for Fedora users in locales
> that use the Latin alphabet, like en_US. Will an input method be part of the
> standard configuration or not? If no input method is installed, will
> gtk-im-context-simple be used or not?
AFAIK, many European people like to use compose keys so probably xim is more
useful than gtk-im-context-simple.
Yes, if you uninstall IM modules in /usr/lib*/gtk-2.0/../immodules,
gtk-im-context-simple will be used.
If you don't set GTK_IM_MODULE, /etc/gtk-2.0/*/gtk.immodules decide the default
module.
ibus-daemon runs on Asian locales by default.
> 2) How will Fedora users input characters by their code? Will there be one
> standard method for doing this?
ibus-daemon enables ibus IM engine(e.g. ibus-rawcode) when you type trigger key
likes Ctrl+Space.
So the code point feature is implemented in an ibus engine, you need to type
Ctrl+Space to enable the engine.
(In reply to comment #12)
> That is, is it possible to have ISO 14755 functionality in IBus that works
> under all IBus input methods? Does IBus allow this feature?
One idea might be to add features in ibus-rawcode.
- Disable lookup window option
- Auto disable engine option
It means you'll use Ctrl+Space instead of Ctrl+Shift+u by default while the
trigger key can be customized with ibus-setup.
If we try to implement Ctrl+Shift+U in ibus-daemon, probably we developers need
further discussions internally.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
14 years