[Fedora-i18n-bugs] [Bug 473665] New: scim-python : Unowned directories
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: scim-python : Unowned directories
https://bugzilla.redhat.com/show_bug.cgi?id=473665
Summary: scim-python : Unowned directories
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: scim-python
AssignedTo: phuang(a)redhat.com
ReportedBy: bugs.michael(a)gmx.net
QAContact: extras-qa(a)fedoraproject.org
CC: phuang(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
One or more directories are not included within this
package and/or its sub-packages:
=> scim-python-pinyin-0.1.13rc1-1.fc10.i386 (rawhide-development-i386)
/usr/share/scim-python/data
=> scim-python-xingma-0.1.13rc1-1.fc10.i386 (rawhide-development-i386)
/usr/share/scim-python/engine/XingMa
/usr/share/scim-python/engine/XingMa/tables
=> scim-python-xingma-cangjie-0.1.13rc1-1.fc10.i386 (rawhide-development-i386)
/usr/share/scim-python/engine/XingMa
/usr/share/scim-python/engine/XingMa/tables
=> scim-python-xingma-erbi-0.1.13rc1-1.fc10.i386 (rawhide-development-i386)
/usr/share/scim-python/engine/XingMa
/usr/share/scim-python/engine/XingMa/tables
=> scim-python-xingma-wubi-0.1.13rc1-1.fc10.i386 (rawhide-development-i386)
/usr/share/scim-python/engine/XingMa
/usr/share/scim-python/engine/XingMa/tables
=> scim-python-xingma-zhengma-0.1.13rc1-1.fc10.i386 (rawhide-development-i386)
/usr/share/scim-python/engine/XingMa
/usr/share/scim-python/engine/XingMa/tables
Note: It may be necessary to include directories in multiple
packages.
[...]
Further information:
https://fedoraproject.org/wiki/Packaging/ReviewGuidelines
MUST: A package must own all directories that it creates. If it does not
create a directory that it uses, then it should require a package which
does create that directory.
https://fedoraproject.org/wiki/Packaging/Guidelines#FileAndDirectoryOwner...
https://fedoraproject.org/wiki/Packaging/UnownedDirectories
--
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, 3 months
[Fedora-i18n-bugs] [Bug 465392] New: race condition in XIM handling
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: race condition in XIM handling
https://bugzilla.redhat.com/show_bug.cgi?id=465392
Summary: race condition in XIM handling
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: scim
AssignedTo: shawn.p.huang(a)gmail.com
ReportedBy: tagoh(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: petersen(a)redhat.com, shawn.p.huang(a)gmail.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Description of problem:
if one sends the key event to SCIM too much and too faster, the application,
such as emacs and xterm freezes.
Version-Release number of selected component (if applicable):
scim-1.4.7-32.fc10
How reproducible:
always as long as it's on the above condition
Steps to Reproduce:
1.change the keyboard repeat setting to make this easier to see, like
gconftool-2 -s -t int /desktop/gnome/peripherals/keyboard/delay 100 and
gconftool-2 -s -t int /desktop/gnome/peripherals/keyboard/rate 110
2.open xterm with XMODIFIERS=@im=SCIM
3.keep pressing a key until it freezes
Actual results:
freeze
Expected results:
should handles it properly
Additional info:
What exactly happened on this race condition issue is:
https://bugzilla.redhat.com/show_bug.cgi?id=452849#c19
Quote from XIM specification:
In on-demand-synchronous method, the IM library always receives
XIM_FORWARD_EVENT or XIM_COMMIT message as a synchronous request. Also, the IM
Server needs to synchronously process the correspondent reply from the IM
library and the following XIM_FORWARD_EVENT message sent from the IM library
when any of the event causes the IM Server to send XIM_FORWARD_EVENT or
XIM_COMMIT message to the IM library, so that the input service is consistent.
If the IM library gets the control back from the application after receiving
the synchronous request, the IM library replies for the synchronous request
before processing any of the events. In this time, the IM Server blocks
XIM_FORWARD_EVENT message which is sent by the IM library, and handles it after
receiving the reply. Howerver, the IM Server handles the other protocols /at
any time/.
So in the case at the above URL, XIM server has to process XIM_SET_IC_VALUES
regardless of waiting for XIM_SYNC_REPLY.
--
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, 4 months
[Fedora-i18n-bugs] [Bug 475904] New: no sound in startdict
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: no sound in startdict
https://bugzilla.redhat.com/show_bug.cgi?id=475904
Summary: no sound in startdict
Product: Fedora
Version: 10
Platform: i386
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: stardict
AssignedTo: cchance(a)redhat.com
ReportedBy: jianliang79(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: cchance(a)redhat.com, zhu(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Description of problem:
I have installed WyabdcRealPeopleTTS sound library but stardict can't read
words for me. Another abnormal thing about sound is that now I can't even hear
the sound when the mouse pointer entering the buttons of stardict. I remember
in the previous version I can hear a little sound when the mouse pointer
entering one of the button of stardict.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
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, 4 months
[Fedora-i18n-bugs] [Bug 493172] New: Dead keys not working in some applications (xterm, emacs)
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: Dead keys not working in some applications (xterm, emacs)
https://bugzilla.redhat.com/show_bug.cgi?id=493172
Summary: Dead keys not working in some applications (xterm,
emacs)
Product: Fedora
Version: 10
Platform: i686
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: imsettings
AssignedTo: tagoh(a)redhat.com
ReportedBy: joyr(a)netikka.fi
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Created an attachment (id=337405)
--> (https://bugzilla.redhat.com/attachment.cgi?id=337405)
X session error log
Description of problem:
Not sure if this is the correct component to report on.
Dead keys stopped working for some applications, not sure when.
I'm using Gnome, layout is Finland layout, keyboard model is Evdev-managed
keyboard.
They seem to work in all GTK applications (tested: gedit, firefox, x-chat) and
also QT applications (qtconfig-qt4), but not on some (xterm, emacs).
Also tried with Sweden layout and Generic 105-key (Intl) PC model with same
problems. I'm unable to set the "Default" radio-button in keyboard preferences
but the layout changes if I drag&drop the wanted layout to first in list.
Version-Release number of selected component (if applicable):
# rpm -qa imsettings* scim* xkey* xterm* emacs* *font* *xim* | sort
abyssinica-fonts-1.0-2.fc8.noarch
baekmuk-ttf-fonts-common-2.2-9.fc10.noarch
baekmuk-ttf-fonts-gulim-2.2-9.fc10.noarch
bitmap-fonts-0.3-6.fc10.noarch
cjkunifonts-uming-0.2.20080216.1-11.fc10.noarch
dejavu-fonts-2.26-2.fc10.noarch
dejavu-fonts-experimental-2.26-2.fc10.noarch
emacs-22.3-4.fc10.i386
emacs-common-22.3-4.fc10.i386
emacs-gnuplot-4.2.3-1.fc10.i386
emacs-lua-20071122-5.fc9.noarch
emacs-nxml-mode-0.20041004-7.fc10.noarch
fontconfig-2.6.0-3.fc10.i386
fontconfig-devel-2.6.0-3.fc10.i386
fontpackages-filesystem-1.20-1.fc10.noarch
ghostscript-fonts-5.50-19.fc10.noarch
imsettings-0.105.1-4.fc10.i386
imsettings-libs-0.105.1-4.fc10.i386
jomolhari-fonts-0.003-5.fc10.noarch
kacst-fonts-2.0-1.fc10.noarch
khmeros-fonts-base-5.0-3.fc10.noarch
liberation-fonts-1.04.92-1.fc10.noarch
libfontenc-1.0.4-6.fc10.i386
libfontenc-devel-1.0.4-6.fc10.i386
libgxim-0.3.2-4.fc10.i386
libXfont-1.3.3-1.fc10.i386
libXfont-devel-1.3.3-1.fc10.i386
lklug-fonts-0.2.2-6.fc10.noarch
lohit-fonts-bengali-2.3.1-1.fc10.noarch
lohit-fonts-gujarati-2.3.1-1.fc10.noarch
lohit-fonts-hindi-2.3.1-1.fc10.noarch
lohit-fonts-kannada-2.3.1-1.fc10.noarch
lohit-fonts-maithili-2.3.1-1.fc10.noarch
lohit-fonts-malayalam-2.3.1-1.fc10.noarch
lohit-fonts-oriya-2.3.1-1.fc10.noarch
lohit-fonts-punjabi-2.3.1-1.fc10.noarch
lohit-fonts-tamil-2.3.1-1.fc10.noarch
lohit-fonts-telugu-2.3.1-1.fc10.noarch
padauk-fonts-2.4-2.fc10.noarch
paktype-fonts-2.0-2.fc8.noarch
scim-1.4.7-35.fc10.i386
scim-anthy-1.2.7-1.fc10.i386
scim-bridge-0.4.15-8.fc10.i386
scim-bridge-gtk-0.4.15-8.fc10.i386
scim-bridge-qt-0.4.15-8.fc10.i386
scim-chewing-0.3.3-0.fc10.i386
scim-hangul-0.3.2-4.fc9.i386
scim-libs-1.4.7-35.fc10.i386
scim-m17n-0.2.2-3.fc9.i386
scim-python-0.1.13rc1-1.fc10.i386
scim-python-pinyin-0.1.13rc1-1.fc10.i386
scim-qtimm-0.9.4-11.fc10.i386
scim-rawcode-1.4.7-35.fc10.i386
smc-fonts-meera-04.1-1.fc10.noarch
stix-fonts-0.9-7.fc10.noarch
texlive-texmf-errata-fonts-2007-4.fc9.noarch
texlive-texmf-fonts-2007-26.fc10.noarch
thaifonts-scalable-0.4.9-3.fc9.noarch
un-core-fonts-dotum-1.0.2-0.6.080608.fc10.noarch
urw-fonts-2.4-6.fc10.noarch
vlgothic-fonts-20090204-2.fc10.noarch
vlgothic-fonts-common-20090204-2.fc10.noarch
xkeyboard-config-1.4-7.fc10.noarch
xorg-x11-fonts-100dpi-7.2-6.fc9.noarch
xorg-x11-fonts-75dpi-7.2-6.fc9.noarch
xorg-x11-fonts-ISO8859-1-100dpi-7.2-6.fc9.noarch
xorg-x11-fonts-ISO8859-1-75dpi-7.2-6.fc9.noarch
xorg-x11-fonts-misc-7.2-6.fc9.noarch
xorg-x11-fonts-Type1-7.2-6.fc9.noarch
xorg-x11-font-utils-7.2-6.fc10.i386
xterm-242-2.fc10.i386
How reproducible:
Always.
Steps to Reproduce:
1. start xterm or emacs
2. try to input ~ using dead-key combination of "altgr" + "~" + "space"
Actual results:
xterm: A plain space character.
emacs: Error message "<dead-tilde> is undefined"
Expected results:
I should be getting the correct character "~".
Additional info:
The following error message comes from imsettings-applet everytime I press any
key on xterm (including modifiers like shift and alt):
[BUG][ 1238531428.714163] xim_proxy_client_protocol_real_xim_forward_event: The
pending key event counter is overflowed
And the following warning comes from imsettings-applet when I start xterm:
W[ 1238531541.790674]:Error while processing a value type NestedList: Error
while processing a value type XFontSet: Unable to compose a value type XFontSet
properly due to the size difference: expected size: 129, actual size: 132
--
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, 5 months
[Fedora-i18n-bugs] [Bug 488877] New: no response on xterm after switching IM
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: no response on xterm after switching IM
https://bugzilla.redhat.com/show_bug.cgi?id=488877
Summary: no response on xterm after switching IM
Product: Fedora
Version: 10
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: imsettings
AssignedTo: tagoh(a)redhat.com
ReportedBy: tagoh(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: jfrieben(a)hotmail.com, tagoh(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Depends on: 488773
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Clone Of: 488773
To keeps an issue in summary on track separately because the root cause is
different.
+++ This bug was initially created as a clone of Bug #488773 +++
Created an attachment (id=334166)
--> (https://bugzilla.redhat.com/attachment.cgi?id=334166)
X session errors caused by enabling SCIM
Description of problem:
After updating libgxim to release 0.3.2-4.fc10, xterm shows some regression:
when running a program with a noticeable amount of text output (e.g. 'ls -R
/'), then imsettings-applet starts grabbing a significant amount of CPU share
of up to 10%. Note that SCIM is disabled at this point.
After opening GNOME menu item "Input Method" and enabling SCIM which is
disabled by default, xterm does not accept any input from the keyboard anymore
unlike gnome-terminal which continues to do so.
Version-Release number of selected component (if applicable):
libgxim-0.3.2-4.fc10.x86_64
How reproducible:
Always.
Steps to Reproduce:
1. Open GNOME session.
2. Start a program in an xterm window producing text output.
3. Run 'top' in a different window.
4. Open "Input Method" from GNOME menu and enable SCIM.
Actual results:
- Noticeable CPU load caused by imsettings-applet.
- Xterm unresponsive after enabling SCIM via "Input Method" dialog window.
Expected results:
Normal behaviour of xterm just as gnome-terminal.
Additional info:
Reverting libgxim to release 0.3.1-1.fc10 allows to restore normal operation.
--
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, 5 months
[Fedora-i18n-bugs] [Bug 488773] New: libgxim-0.3.2-4.fc10: enabling SCIM blocks xterm and causes important CPU load
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: libgxim-0.3.2-4.fc10: enabling SCIM blocks xterm and causes important CPU load
https://bugzilla.redhat.com/show_bug.cgi?id=488773
Summary: libgxim-0.3.2-4.fc10: enabling SCIM blocks xterm and
causes important CPU load
Product: Fedora
Version: 10
Platform: x86_64
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: libgxim
AssignedTo: tagoh(a)redhat.com
ReportedBy: jfrieben(a)hotmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Created an attachment (id=334166)
--> (https://bugzilla.redhat.com/attachment.cgi?id=334166)
X session errors caused by enabling SCIM
Description of problem:
After updating libgxim to release 0.3.2-4.fc10, xterm shows some regression:
when running a program with a noticeable amount of text output (e.g. 'ls -R
/'), then imsettings-applet starts grabbing a significant amount of CPU share
of up to 10%. Note that SCIM is disabled at this point.
After opening GNOME menu item "Input Method" and enabling SCIM which is
disabled by default, xterm does not accept any input from the keyboard anymore
unlike gnome-terminal which continues to do so.
Version-Release number of selected component (if applicable):
libgxim-0.3.2-4.fc10.x86_64
How reproducible:
Always.
Steps to Reproduce:
1. Open GNOME session.
2. Start a program in an xterm window producing text output.
3. Run 'top' in a different window.
4. Open "Input Method" from GNOME menu and enable SCIM.
Actual results:
- Noticeable CPU load caused by imsettings-applet.
- Xterm unresponsive after enabling SCIM via "Input Method" dialog window.
Expected results:
Normal behaviour of xterm just as gnome-terminal.
Additional info:
Reverting libgxim to release 0.3.1-1.fc10 allows to restore normal operation.
--
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, 5 months
[Fedora-i18n-bugs] [Bug 490919] New: imsettings slows down frame rates significantly in Linux Gaming. (10-30 FPS)
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: imsettings slows down frame rates significantly in Linux Gaming. (10-30 FPS)
https://bugzilla.redhat.com/show_bug.cgi?id=490919
Summary: imsettings slows down frame rates significantly in
Linux Gaming. (10-30 FPS)
Product: Fedora
Version: 4
Platform: i386
OS/Version: Linux
Status: NEW
Severity: urgent
Priority: low
Component: imsettings
AssignedTo: tagoh(a)redhat.com
ReportedBy: nikitis(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Clone Of: 488976
Description of problem: The new release of imsettings-0.105.1-4.fc10 causes
games to slowdown 10-30 Frames Per Second.
Version-Release number of selected component (if applicable):
imsettings-0.105.1-4.fc10
How reproducible: 100%
Steps to Reproduce:
1.Enter into World of Warcraft (My example), Log in.
2.Start Frames Per Second Counter (Ctrl+R)
3.Move or press any key or hold any key and frames will drop.
Actual results: The Game beings to slow down as keys are pressed or held.
Expected results: The Game should not experience any frame loss as a result of
a key press. Especially not to the degree of 10-30 FPS. Maybe only a couple
of frames maximum as the screen is processing new data when turning etc.
imsettings inside of libgxim 3.1-1 functions properly in this respect, and was
the last known working version if imsettings.
Additional info:I was working with a developer and started the bug report
488976 because of this issue, and he decided it was working well enough for an
update release. Before inside the games if you turned left, and let go, you
would continue to turn left and that wasn't supposed to happen. With
sync_on_forward set to true with new version of imsettings-0.105.1-4.fc10, that
issue is fixed however there is now a regression in the fact that there is a
Frames per second loss when a key is pressed or held which results in a very
bad gaming experience. Sometimes game slows to a crawl.
I have a GeForce 8600 GT by Nvidia, dual core intel processor at 3.0 Ghz, 4GB's
of RAM running FC10 i386. I did not experience this slowdown until
libgxim-0.3.2-4.fc10 package was released.
Starting new bug report to fix this regression.
--
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, 5 months
[Fedora-i18n-bugs] [Bug 471927] New: imsettings causes window manager confusion in Xfce
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: imsettings causes window manager confusion in Xfce
https://bugzilla.redhat.com/show_bug.cgi?id=471927
Summary: imsettings causes window manager confusion in Xfce
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: imsettings
AssignedTo: tagoh(a)redhat.com
ReportedBy: kevin(a)tummy.com
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
If the imsettings and imsettings-xfce packages are installed xfwm4 settings are
confused and don't think xfwm4 is the window manager.
1. Install imsettings-xfce
2. yum groupinstall XFCE
3. login and choose Xfce as your desktop.
4. right click on the desktop
5. choose settings manager
6. choose either "Window Manager" or "Window Manager Tweaks".
7. You will get a message:
"These settings cannot work with your current window manager (imsetting-xim)"
The code in xfwm4 hasn't changed in years here. It does:
wm_name = gdk_x11_screen_get_window_manager_name (gdk_screen_get_default
());
if (g_ascii_strcasecmp (wm_name, "Xfwm4"))
{
xfce_err (_("These settings cannot work with your current window
manager (%s)"), wm_name);
return;
}
Is imsettings changing the gdk default window manager somehow?
Removing imsettings causes everything to work as normal.
--
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, 5 months
[Fedora-i18n-bugs] [Bug 481156] New: S-c-language crashes while installing new language - zero division error
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: S-c-language crashes while installing new language - zero division error
https://bugzilla.redhat.com/show_bug.cgi?id=481156
Summary: S-c-language crashes while installing new language -
zero division error
Product: Fedora
Version: 10
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: system-config-language
AssignedTo: psatpute(a)redhat.com
ReportedBy: jreznik(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: psatpute(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Description of problem: S-c-language crashes while installing new language with
traceback zero division error.
Version-Release number of selected component (if applicable):
system-config-language-1.3.2-3.fc10.noarch
How reproducible: install new language support, occurred once
Steps to Reproduce:
1. select new language, click ok
2. let new language install in the next dialog
Actual results:
Traceback (most recent call last):
File "/usr/share/system-config-language/gui_progress.py", line 101, in
callback
pct = amount/float(total)
ZeroDivisionError: float division
error: python callback <bound method GuiTransactionProgress.callback of
<gui_progress.GuiTransactionProgress instance at 0x7f0a28085200>> failed,
aborting!
Expected results:
S-c-language not crashing
--
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, 5 months
[Fedora-i18n-bugs] [Bug 483181] New: msggrep segfaults when $ anchor is used
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: msggrep segfaults when $ anchor is used
https://bugzilla.redhat.com/show_bug.cgi?id=483181
Summary: msggrep segfaults when $ anchor is used
Product: Fedora
Version: 9
Platform: i686
URL: https://savannah.gnu.org/bugs/index.php?25437
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: gettext
AssignedTo: petersen(a)redhat.com
ReportedBy: sflaniga(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: petersen(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Description of problem:
msggrep segfaults when $ anchor is used in regex
Version-Release number of selected component (if applicable):
0.17-4.fc9
How reproducible:
About 15 out of 16 runs.
Steps to Reproduce:
1.echo a=b | msggrep -P -K -e '^a$'
Actual results:
Segmentation fault (15/16 runs) or
no matches (1/16 runs)
Expected results:
One matching string
Additional info:
May be connected to https://savannah.gnu.org/bugs/index.php?25437. (My locally
compiled gettext-0.17 doesn't segfault, but never returns the expected
matches.)
--
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, 6 months