[Bug 2274678] New: Black screen on each first GUI login after a
reboot
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2274678
Bug ID: 2274678
Summary: Black screen on each first GUI login after a reboot
Product: Fedora
Version: 40
Hardware: x86_64
OS: Linux
Status: NEW
Component: imsettings
Keywords: Desktop
Severity: medium
Assignee: tagoh(a)redhat.com
Reporter: mmuehlfe(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
When I boot my laptop and log in to Cinnamon, the screen stays black. Only the
mouse cursor is visible and can be moved.
To work around this problem, I switch to the console, kill the
"cinnamon-session-binary" process, and then log in again. After this
workaround, I can logout/login as often as I want, and everything works as
expected. However, as soon as I reboot, the problem is back and I, again, need
the workaround.
The errors in /var/log/messages and .xsession-errors sound like the problem is
related to imsettings-daemon.
I can reproduce this problem after each reboot of my laptop (Dell Latitude
E7440). I don't have this problem on my F40 desktop computer. Both are fresh
installations (no upgrades) of F40, and all available updates are installed.
Reproducible: Always
Steps to Reproduce:
1. Boot Fedora 40.
2. Log in to Cinnamon.
Actual Results:
Black screen on the first time you log in after a reboot. Only the mouse cursor
is visible and can be moved.
Expected Results:
Desktop should be shown and be usable.
* The problem also exists if SELinux is in permissive mode.
* The problem also exists with a new user account (empty home directory).
* Only the first user who logs into the GUI after a reboot has this problem. If
you run the workaround, all users can login/logoff without getting the black
screen.
* After a reboot, the problem is back, and the first GUI login shows the black
screen.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2274678
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
2 months
[Bug 2272023] New: Super+Space not working in Typing Booster
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2272023
Bug ID: 2272023
Summary: Super+Space not working in Typing Booster
Product: Fedora
Version: 40
OS: Linux
Status: NEW
Component: ibus-typing-booster
Keywords: i18n, Regression
Severity: medium
Assignee: mfabian(a)redhat.com
Reporter: petersen(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: anish.developer(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com
Target Milestone: ---
Classification: Fedora
After ibus is switched to Typing Booster, Super+Space causes space characters
to be
inserted rather than activate the Input Source switcher.
Reproducible: Always
Steps to Reproduce:
1. Switch input to Typing Booster in F40 Workstation
2. Use Super+Space to switch input source
Actual Results:
Space character is inserted in gnome-text-editor
Expected Results:
Input source switcher to be activated
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2272023
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
2 months, 1 week
[Bug 1890085] English keyboard layout is erroneously used during
initramfs phase (e.g. decrypting encrypted storage devices) instead of native
layout, on Silverblue / ostree installs
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1890085
--- Comment #43 from Adam Williamson <awilliam(a)redhat.com> ---
that would be a different bug, but it seems strange, because we do have
automated testing for that and it is not currently failing. see e.g.
https://openqa.fedoraproject.org/tests/2552274 - that test installs in French,
and for the encryption passphrase, it presses the keys that would produce the
string 'weakpassword' on a US keyboard, which should give a different string in
French (at least A becomes Q and W becomes Z, don't remember if anything else
changes). It then presses the same keys when booting the installed system to
unlock it. If the layout were different between the installer and the unlock
prompt, the test would fail.
Theoretically the test can falsely pass if the layout is wrong at *both*
points, but that's not what you describe, and we have a guard against that in
the test (we have the system hit the keys marked 'qwerty' on a US keyboard when
typing the username, and we check that the username actually comes out as
'azerty'; if not, the test fails).
Do let us know if you hit this consistently, though. Please file a new bug in
that case.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1890085
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
2 months, 1 week
[Bug 2270227] New: [abrt] ibus-rime:
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release():
ibus-engine-rime killed by SIGSEGV
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2270227
Bug ID: 2270227
Summary: [abrt] ibus-rime:
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_
release(): ibus-engine-rime killed by SIGSEGV
Product: Fedora
Version: 39
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:65b87b45a9e995afda800e61151d1eebf130392a;VAR
IANT_ID=workstation;
Component: ibus-rime
Assignee: pwu(a)redhat.com
Reporter: ylx30130(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
ibus-rime-1.5.0-7.fc39
Additional info:
reporter: libreport-2.17.11
type: CCpp
reason: ibus-engine-rime killed by SIGSEGV
journald_cursor:
s=625d004b3b0a4a63997b281eb7d80d59;i=22a32;b=fcdfb51170a84076a5b9a8c9326954fd;m=40248a8b2;t=613fcfda50840;x=dced373c335a04fc
executable: /usr/libexec/ibus-rime/ibus-engine-rime
cmdline: /usr/libexec/ibus-rime/ibus-engine-rime --ibus
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
rootdir: /
uid: 1000
kernel: 6.7.9-200.fc39.x86_64
package: ibus-rime-1.5.0-7.fc39
runlevel: N 5
backtrace_rating: 4
crash_function: std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release
Truncated backtrace:
Thread no. 1 (22 frames)
#0 std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release at
/usr/include/c++/13/bits/shared_ptr_base.h:337
#1 std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count at
/usr/include/c++/13/bits/shared_ptr_base.h:1071
#2 std::__shared_ptr<rime::Session, (__gnu_cxx::_Lock_policy)2>::~__shared_ptr
at /usr/include/c++/13/bits/shared_ptr_base.h:1524
#3 std::shared_ptr<rime::Session>::~shared_ptr at
/usr/include/c++/13/bits/shared_ptr.h:175
#4 std::pair<unsigned long const, std::shared_ptr<rime::Session> >::~pair at
/usr/include/c++/13/bits/stl_pair.h:187
#5 std::__new_allocator<std::_Rb_tree_node<std::pair<unsigned long const,
std::shared_ptr<rime::Session> > > >::destroy<std::pair<unsigned long const,
std::shared_ptr<rime::Session> > > at
/usr/include/c++/13/bits/new_allocator.h:194
#6 std::allocator_traits<std::allocator<std::_Rb_tree_node<std::pair<unsigned
long const, std::shared_ptr<rime::Session> > > > >::destroy<std::pair<unsigned
long const, std::shared_ptr<rime::Session> > > at
/usr/include/c++/13/bits/alloc_traits.h:557
#7 std::_Rb_tree<unsigned long, std::pair<unsigned long const,
std::shared_ptr<rime::Session> >, std::_Select1st<std::pair<unsigned long
const, std::shared_ptr<rime::Session> > >, std::less<unsigned long>,
std::allocator<std::pair<unsigned long const, std::shared_ptr<rime::Session> >
> >::_M_destroy_node at /usr/include/c++/13/bits/stl_tree.h:625
#8 std::_Rb_tree<unsigned long, std::pair<unsigned long const,
std::shared_ptr<rime::Session> >, std::_Select1st<std::pair<unsigned long
const, std::shared_ptr<rime::Session> > >, std::less<unsigned long>,
std::allocator<std::pair<unsigned long const, std::shared_ptr<rime::Session> >
> >::_M_drop_node at /usr/include/c++/13/bits/stl_tree.h:633
#9 std::_Rb_tree<unsigned long, std::pair<unsigned long const,
std::shared_ptr<rime::Session> >, std::_Select1st<std::pair<unsigned long
const, std::shared_ptr<rime::Session> > >, std::less<unsigned long>,
std::allocator<std::pair<unsigned long const, std::shared_ptr<rime::Session> >
> >::_M_erase at /usr/include/c++/13/bits/stl_tree.h:1938
#10 std::_Rb_tree<unsigned long, std::pair<unsigned long const,
std::shared_ptr<rime::Session> >, std::_Select1st<std::pair<unsigned long
const, std::shared_ptr<rime::Session> > >, std::less<unsigned long>,
std::allocator<std::pair<unsigned long const, std::shared_ptr<rime::Session> >
> >::clear at /usr/include/c++/13/bits/stl_tree.h:1255
#11 std::map<unsigned long, std::shared_ptr<rime::Session>, std::less<unsigned
long>, std::allocator<std::pair<unsigned long const,
std::shared_ptr<rime::Session> > > >::clear at
/usr/include/c++/13/bits/stl_map.h:1184
#12 rime::Service::CleanupAllSessions at
/usr/src/debug/librime-1.8.5-3.fc39.x86_64/src/rime/service.cc:150
#13 RimeFinalize at
/usr/src/debug/librime-1.8.5-3.fc39.x86_64/src/rime_api.cc:85
#14 ibus_rime_stop at
/usr/src/debug/ibus-rime-1.5.0-7.fc39.x86_64/rime_main.c:84
#15 sigterm_cb at /usr/src/debug/ibus-rime-1.5.0-7.fc39.x86_64/rime_main.c:138
#17 syscall at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:37
#18 g_cond_wait at ../glib/gthread-posix.c:1552
#19 g_async_queue_pop_intern_unlocked at ../glib/gasyncqueue.c:425
#20 g_thread_pool_spawn_thread at ../glib/gthreadpool.c:311
#21 g_thread_proxy at ../glib/gthread.c:831
#23 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=2270227
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
2 months, 1 week