https://bugzilla.redhat.com/show_bug.cgi?id=2062407
Bug ID: 2062407
Summary: msgfmt cannot invoke javac
Product: Fedora
Version: rawhide
Hardware: All
OS: Linux
Status: NEW
Component: gettext
Severity: low
Assignee: suanand(a)redhat.com
Reporter: loganjerry(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
jjanco(a)redhat.com, nphilipp(a)redhat.com,
petersen(a)redhat.com, praiskup(a)redhat.com,
suanand(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
I noticed while building jmol that every invocation of msgfmt failed, e.g.:
update-application-catalog-lang:
[echo] msgfmt Updating messages_ar.class file for Jmol ...
[exec] msgfmt: Java compiler not found, try installing gcj or set $JAVAC
[exec] msgfmt: compilation of Java class failed, please try --verbose or
set $JAVAC
[exec] 65 translated messages, 3 fuzzy translations, 380 untranslated
messages.
[exec] Result: 1
Setting JAVAC does *not* help. I used strace to see how javac is invoked and
found the problem: msgfmt passes -target 1.6, and sometimes -source 1.6, to
javac. Now that OpenJDK 17 is the default in Fedora, those arguments are no
longer valid. I don't remember if the minimum allowed is 1.7 or 1.8, but it is
one of the two. Since Fedora doesn't ship a JDK lower than 1.8, then 1.8 might
as well be used.
Version-Release number of selected component (if applicable):
gettext-0.21-11.fc37.0.20220228
How reproducible:
Always
Steps to Reproduce:
1. fedpkg clone jmol
2. cd jmol
3. fedpkg srpm
4. mock -r fedora-rawhide-x86_64 --rebuild jmol-14.32.22-1.fc37.src.rpm
Actual results:
The msgfmt invocations all fail.
Expected results:
The msgfmt invocations should succeed.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2062407
https://bugzilla.redhat.com/show_bug.cgi?id=1658174
--- Comment #7 from fujiwara <tfujiwar(a)redhat.com> ---
(In reply to fujiwara from comment #1)
> > If the window is nearly an edge it may get moved because of the resizing.
>
> My suggestion was not to move the window when the cursor is moved in the
> same page even if the resize happens. But seems you found a case the window
> is moved.
> Could you give an example of a category and which emojis your cursor is over?
Probably I think this is the main issue for you.
I think now the position of the candidate popup is better fixed in Xorg and the
position is always center in GNOME Wayland so this can be closed?
(In reply to Jens Petersen from comment #4)
> Maybe by eliding some text if it is too long?
> It could be shown in a tooltip say.
The concept is to handle the popup with the keyboard shortcut only and the
popup also includes the tooltip function.
I think how to elide the number of the annotations is hard. E.g. the "crying"
annotation is located at the last order.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1658174
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2328000
Bug ID: 2328000
Summary: [abrt] ibus-typing-booster:
_atspi_dbus_call_partial_va(): python3.12 killed by
SIGSEGV
Product: Fedora
Version: 40
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:73256a6f593877c8123e20da5fd990c7e6846fca;VAR
IANT_ID=workstation;
Component: ibus-typing-booster
Assignee: mfabian(a)redhat.com
Reporter: lantw44(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Change the input method with Ctrl+Space and it crashed the entire desktop. Seem
to be the same problem as https://bugzilla.redhat.com/show_bug.cgi?id=2278115.
Version-Release number of selected component:
ibus-typing-booster-2.26.11-1.fc40
Additional info:
reporter: libreport-2.17.15
dso_list: /usr/bin/python3.12 python3-3.12.7-1.fc40.x86_64 (Fedora
Project) 1730785750
type: CCpp
uid: 1000
package: ibus-typing-booster-2.26.11-1.fc40
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
kernel: 6.11.8-200.fc40.x86_64
runlevel: N 5
backtrace_rating: 4
reason: python3.12 killed by SIGSEGV
journald_cursor:
s=0c85b522b06f42a5a7960779df986059;i=bcf24a;b=cfec291e94224b19a1490ff2a753bf1b;m=883db5dfa;t=6277ddd49c1ca;x=45761e7ccf5a14de
rootdir: /
crash_function: _atspi_dbus_call_partial_va
executable: /usr/bin/python3.12
comment: Change the input method with Ctrl+Space and it crashed the
entire desktop. Seem to be the same problem as
https://bugzilla.redhat.com/show_bug.cgi?id=2278115.
cmdline: /usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py
--ibus
Truncated backtrace:
Thread no. 1 (19 frames)
#0 _atspi_dbus_call_partial_va at ../atspi/atspi-misc.c:1321
#1 _atspi_dbus_call_partial at ../atspi/atspi-misc.c:1361
#2 atspi_accessible_get_state_set at ../atspi/atspi-accessible.c:731
#4 ffi_call_unix64 at ../src/x86/unix64.S:104
#5 ffi_call_int at ../src/x86/ffi64.c:673
#6 ffi_call at ../src/x86/ffi64.c:710
#7 pygi_invoke_c_callable at ../gi/pygi-invoke.c:684
#8 pygi_function_cache_invoke at ../gi/pygi-cache.c:862
#9 pygi_callable_info_invoke at ../gi/pygi-invoke.c:727
#10 _wrap_g_callable_info_invoke at ../gi/pygi-invoke.c:764
#11 _callable_info_call at ../gi/pygi-info.c:548
#13 _PyObject_MakeTpCall at
/usr/src/debug/python3.12-3.12.7-1.fc40.x86_64/Objects/call.c:240
#14 _PyEval_EvalFrameDefault at Python/bytecodes.c:2715
#15 _PyFunction_Vectorcall at
/usr/src/debug/python3.12-3.12.7-1.fc40.x86_64/Objects/call.c:419
#16 _PyObject_VectorcallTstate at
/usr/src/debug/python3.12-3.12.7-1.fc40.x86_64/Include/internal/pycore_call.h:92
#17 method_vectorcall at
/usr/src/debug/python3.12-3.12.7-1.fc40.x86_64/Objects/classobject.c:69
#18 thread_run at
/usr/src/debug/python3.12-3.12.7-1.fc40.x86_64/Modules/_threadmodule.c:1114
#19 pythread_wrapper at
/usr/src/debug/python3.12-3.12.7-1.fc40.x86_64/Python/thread_pthread.h:237
#21 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2328000
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2292805
Bug ID: 2292805
Summary: [abrt] ibus-table: tcache_thread_shutdown():
python3.12 killed by SIGABRT
Product: Fedora
Version: 40
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:49912628f88fad8ef32c365c9a170d6066e7e2cb;VAR
IANT_ID=workstation;
Component: ibus-table
Assignee: mfabian(a)redhat.com
Reporter: cinxiafortis(a)tutanota.de
QA Contact: extras-qa(a)fedoraproject.org
CC: dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
mfabian(a)redhat.com, pwu(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
It has a conflict with tha app from flathub named app.drey.Warp. When I start
app.drey.Warp, my ibus-table stop and I cannot use my input method (canjie5).
After I stopped app.drey.Warp, the ibus-table works again and I can use my
input method.
Version-Release number of selected component:
ibus-table-1.17.4-3.fc40
Additional info:
reporter: libreport-2.17.15
type: CCpp
reason: python3.12 killed by SIGABRT
journald_cursor:
s=b851438adea5488c9c2c2087cbad4e16;i=1a5736;b=16be98526b23462598842ccaa91bc721;m=3c46437d;t=61b1fbb08a027;x=4fab5ac69ab93a00
executable: /usr/bin/python3.12
cmdline: /usr/bin/python3 /usr/share/ibus-table/engine/main.py --ibus
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
rootdir: /
uid: 1000
kernel: 6.8.11-300.fc40.x86_64
package: ibus-table-1.17.4-3.fc40
runlevel: N 5
dso_list: /usr/bin/python3.12 python3-3.12.3-2.fc40.x86_64 (Fedora
Project) 1715406510
backtrace_rating: 4
crash_function: tcache_thread_shutdown
comment: It has a conflict with tha app from flathub named
app.drey.Warp. When I start app.drey.Warp, my ibus-table stop and I cannot use
my input method (canjie5). After I stopped app.drey.Warp, the ibus-table works
again and I can use my input method.
Truncated backtrace:
Thread no. 1 (4 frames)
#6 tcache_thread_shutdown at malloc.c:3231
#7 __malloc_arena_thread_freeres at
/usr/src/debug/glibc-2.39-15.fc40.x86_64/malloc/arena.c:897
#8 __libc_thread_freeres at thread-freeres.c:41
#10 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2292805
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2088734
Aoife Moloney <amoloney(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |EOL
Last Closed|2024-11-27 21:01:52 |2025-05-16 07:39:53
--- Comment #14 from Aoife Moloney <amoloney(a)redhat.com> ---
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13.
Fedora Linux 40 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.
If you can reproduce this bug against a currently maintained version of Fedora
Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.
If you are unable to reopen this bug, please file a new report against an
active release.
Thank you for reporting this bug and we are sorry it could not be fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2088734
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=1580458
Aoife Moloney <amoloney(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |EOL
Status|ASSIGNED |CLOSED
Last Closed| |2025-05-16 07:37:13
--- Comment #19 from Aoife Moloney <amoloney(a)redhat.com> ---
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13.
Fedora Linux 40 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.
If you can reproduce this bug against a currently maintained version of Fedora
Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.
If you are unable to reopen this bug, please file a new report against an
active release.
Thank you for reporting this bug and we are sorry it could not be fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1580458
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…