[Fedora-i18n-bugs] [Bug 1626422] New: libharfbuzz.so.0: undefined symbol: FT_Done_MM_Var
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1626422
Bug ID: 1626422
Summary: libharfbuzz.so.0: undefined symbol: FT_Done_MM_Var
Product: Fedora
Version: 29
Component: harfbuzz
Severity: high
Assignee: pnemade(a)redhat.com
Reporter: rvcsaba(a)freemail.hu
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, klember(a)redhat.com,
moceap(a)hotmail.com, pnemade(a)redhat.com,
psatpute(a)redhat.com
Description of problem:
I upgradede to Fedora 29, and lightdm exited error code 1. I see
seat0-greeter.log:
/usr/sbin/lightdm-gtk-greeter: symbol lookup error: /lib64/libharfbuzz.so.0:
undefined symbol: FT_Done_MM_Var
Version-Release number of selected component (if applicable):
harfbuzz-1.8.7-1.fc29.x86_64
harfbuzz-1.8.7-1.fc29.i686
lightdm-gtk-2.0.5-2.fc29.x86_64
How reproducible:
Boot my computer.
Additional info:
[+0.35s] DEBUG: XServer 0: Connecting to XServer :0
[+0.36s] DEBUG: posix_spawn avoided (fd close requested) (child_setup
specified)
[+0.36s] DEBUG: Seat seat0: Display server ready, starting session
authentication
[+0.36s] DEBUG: Session pid=1642: Started with service 'lightdm-greeter',
username 'lightdm'
[+0.39s] DEBUG: Session pid=1642: Authentication complete with return value 0:
Success
[+0.39s] DEBUG: Seat seat0: Session authenticated, running command
[+0.39s] DEBUG: Session pid=1642: Running command /usr/sbin/lightdm-gtk-greeter
[+0.39s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+0.39s] DEBUG: Session pid=1642: Logging to /var/log/lightdm/seat0-greeter.log
[+0.61s] DEBUG: Activating VT 1
[+0.61s] DEBUG: Activating login1 session c5
[+0.61s] DEBUG: Seat seat0 changes active session to c5
[+0.61s] DEBUG: Session c5 is already active
[+0.62s] DEBUG: Greeter closed communication channel
[+0.62s] DEBUG: Session pid=1642: Exited with return value 127
[+0.62s] DEBUG: Seat seat0: Session stopped
[+0.62s] DEBUG: Seat seat0: Stopping; failed to start a greeter
[+0.62s] DEBUG: Seat seat0: Stopping
[+0.62s] DEBUG: Seat seat0: Stopping display server
[+0.62s] DEBUG: Sending signal 15 to process 1624
[+0.63s] DEBUG: Seat seat0 changes active session to
[+0.75s] DEBUG: Process 1624 exited with return value 0
[+0.75s] DEBUG: XServer 0: X server stopped
[+0.75s] DEBUG: Releasing VT 1
[+0.75s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+0.75s] DEBUG: Seat seat0: Display server stopped
[+0.75s] DEBUG: Seat seat0: Stopped
[+0.75s] DEBUG: Required seat has stopped
[+0.75s] DEBUG: Stopping display manager
[+0.75s] DEBUG: Display manager stopped
[+0.75s] DEBUG: Stopping daemon
[+0.75s] DEBUG: Exiting with return value 1
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 7 months
[Fedora-i18n-bugs] [Bug 507262] New: Separate Japanese font configuration files for ghostscript
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: Separate Japanese font configuration files for ghostscript
https://bugzilla.redhat.com/show_bug.cgi?id=507262
Summary: Separate Japanese font configuration files for
ghostscript
Product: Fedora
Version: 11
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: japanese-bitmap-fonts
AssignedTo: tagoh(a)redhat.com
ReportedBy: t.matsuu(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
I'm not sure which component should be assigned for this bug. So I initially
assign this bug to japanese-bitmap-fonts because the files for discussion is
now owned by japanese-bitmap-fonts package.
Description of problem:
Now
/usr/share/ghostscript/conf.d/CIDFnmap.ja
/usr/share/ghostscript/conf.d/FAPIcidfmap.ja
/usr/share/ghostscript/conf.d/cidfmap.ja
are owned by japanese-bitmap-fonts. But they never use fonts which are bundled
in japanese-bitmap-fonts.
Moreover, fonts which are set in the config files are dispersed among some
packages.
So we need to separate ghostscript contig files from japanese-bitmap-fonts and
they should be provided by another package (or included in ghostscript or
ghostscript-fonts package).
I suggest the following idea.
1. Universal
/usr/share/ghostscript/conf.d/{CIDFnmap.ja,FAPIcidfmap.ja,cidfmap.ja} is owned
by new (eg. ghostscript-fonts-japanese), ghostscript, or ghostscript-fonts
package.
2. Each Japanese fonts have their own CIDFnmap.ja, FAPIcidfmap.ja, and
cidfmap.ja files i their common package.
Discussion required:
* fonts priority
* file owner for ghostscript config files
* package structure of IPA fonts are not ready for generate common subpackage
now (bug 507261)
--
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.
5 years, 7 months
[Fedora-i18n-bugs] [Bug 1616024] New: Hangul input no longer works after updating to 1.5.1
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1616024
Bug ID: 1616024
Summary: Hangul input no longer works after updating to 1.5.1
Product: Fedora
Version: 28
Component: ibus-hangul
Assignee: pwu(a)redhat.com
Reporter: psabata(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, pwu(a)redhat.com,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
Description of problem:
After updating to ibus-hangul-1.5.1-1.fc28, typing with the Hangul method
prints just latin letters. Downgrading to ibus-hangul-1.5.0-12.fc28 fixes the
issue.
Version-Release number of selected component (if applicable):
ibus-hangul-1.5.1-1.fc28
How reproducible:
Always, tested with GTK3 and xterm.
Steps to Reproduce:
1. Switch to the Hangul input method while running 1.5.1
2. Type anything
Actual results:
Latin letters show up.
Expected results:
Hangul shows up.
Additional info:
I put some more info in the update comment:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-add3b2828f
I run X.org but I do not run GNOME, just a simple window manager. My
installation is fairly minimal. Czech, Farsi and Russian methods work fine for
me but Japanese methods (anthy, mozc) never did.
If I had to guess, I would say some runtime dependencies are missing; probably
something that is typically installed on a GNOME workstation where, according
to the update commenters, the problem doesn't manifest itself.
If that's the case, the difference between 1.5.0 and 1.5.1 could be the same
reason why ibus-anthy and ibus-mozc don't work on my system either.
I've tried to figure this out but I'm stuck; expert advice needed :)
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 7 months
[Fedora-i18n-bugs] [Bug 1625551] [Wayland] ibus-typing-booster broken
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1625551
Milan Crha <mcrha(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anish.developer(a)gmail.com,
| |i18n-bugs(a)lists.fedoraproje
| |ct.org, mfabian(a)redhat.com
Component|evolution |ibus-typing-booster
Assignee|mcrha(a)redhat.com |mfabian(a)redhat.com
Summary|Not able to input in |[Wayland]
|Evolution using |ibus-typing-booster broken
|ibus-typing-boster/CJK in |
|wayland session |
--- Comment #5 from Milan Crha <mcrha(a)redhat.com> ---
Thanks for the steps, I can reproduce it with them too. I tried to reproduce
also in Fedora 28, but it works fine there. An interesting issue with the
rawhide (I do not have any F29 machine yet) it that it misbehaves also in the
Subject header, which is a native GtkEntry widget.
I see a runtime warning in both systems when playing with this:
> (evolution:2952): Gdk-WARNING **: 15:12:53.780: Event with type 8 not holding
> a GdkDevice. It is most likely synthesized outside Gdk/GTK+
which may or may not be related. It seems to be specific to Xorg only and I can
reproduce it with the below steps as well.
Anyway, I found out that there are other things broken here. For me, with
gtk3-3.23.2-1.fc29.x86_64 and ibus-typing-booster-2.1.0-2.fc30.noarch
I do:
a) run from a terminal: gtk3-demo
b) open: Entry->Entry Buffer
c) switch input method from English to Other (Typing Booster)
d) type: aaa<space>bbb<space>
where <space> is for a space bar key
Right now the result in the entry demo is: "aaa bbb " (quoted for clarity
only).
e) close this entry demo window, but *not* the gtk3-demo main window
f) open Entry->Entry Buffer again
g) repeat step d) (the step c) is not needed, the input method left selected)
And now, the result is: " ", aka the "aaa" and "bbb" is replaced with the
space, instead of the space being used as the word-end-indicator. I can
reproduce this also in the MiniBrowser, but the issue as low as in the GtkEntry
is more interesting.
I'd suppose from the above that there's something broken lower than in the
widgets.
I also see the runtime warnings from comment #2 whenever I close the Entry
Buffer window.
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 7 months
[Fedora-i18n-bugs] [Bug 1625596] New: emoji input does not work in f29 live
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1625596
Bug ID: 1625596
Summary: emoji input does not work in f29 live
Product: Fedora
Version: 29
Component: ibus
Keywords: i18n
Assignee: tfujiwar(a)redhat.com
Reporter: tagoh(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
Description of problem:
The emoji input in the feature of ibus 1.5.19 doesn't work on f29 Live.
Version-Release number of selected component (if applicable):
Fedora-Workstation-Live-x86_64-29-20180903.n.0.iso
How reproducible:
always
Steps to Reproduce:
1.boot up Live
2.Add the input source like "Japanese (Kana)" a.k.a. ibus-kkc
3.open gedit and type Ctrl+Shift+e and space say.
Actual results:
only the space is committed to gedit
Expected results:
should open the emoji category list as mentioned at
https://fedoraproject.org/wiki/Changes/IBus_1.5.19
Additional info:
This should be assigned to LiveCD perhaps but ibus so far to make the root
cause clear and propose the proper solution to it.
To be sure, package list attached which has the name of ibus:
$ rpm -qa ibus*
ibus-1.5.19-2.fc29.x86_64
ibus-qt-1.3.3-20.fc29.x86_64
ibus-libpinyin-1.10.0-3.fc29.x86_64
ibus-libzhuyin-1.8.92-3.fc29.x86_64
ibus-gtk3-1.5.19-2.fc29.x86_64
ibus-libs-1.5.19-2.fc29.x86_64
ibus-hangul-1.5.1-2.fc29.x86_64
ibus-kkc-1.5.22-10.fc29.x86_64
ibus-setup-1.5.19-2.fc29.noarch
ibus-rawcode-1.3.2-13.fc29.x86_64
ibus-typing-booster-2.1.0-2.fc29.noarch
ibus-m17n-1.3.4-27.fc29.x86_64
ibus-gtk2-1.5.19-2.fc29.x86_64
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 7 months