[Bug 1405539] changing the default keyboard layout changes also disk decryption in plymouth , but only after kernel update, long after
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1405539
--- Comment #45 from Christian Stadelmann <rhbz2(a)genodeftest.de> ---
Older duplicate of this bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1151651
> This does not seem to be a plymouth bug, but something else.
This is NOT a bug in plymouth, as booting without plymouth is also affected.
I'd prefer to blame localectl or whichever tool is changing the system keyboard
layout. A similar issue has been reported a few times before:
https://bugzilla.redhat.com/show_bug.cgi?id=917718
https://bugzilla.redhat.com/show_bug.cgi?id=1059485
Possible solutions from here:
* automatically trigger rebuilding the initramfs every time the system-wide
keyboard layout changed. Sounds like a bad idea because it might lock out
people from their own systems on reboot, so we need to educate the user about
the fact that this also changes the initramfs layout.
* (from localectl binary): When changing the system layout, tell the user to
rebuild their initramfs manually to apply these changes.
(In reply to Iiro Laiho from comment #43)
> Sounds like a some kind of design flaw. Non-root users aren't supposed to be
> able to change system-wide settings, right?
Yes, with PolicyKit (or sudo) they are, that's what is going on behind
gnome-control-center asking for your password.(In reply to Iiro Laiho from
comment #44)
> And to add to my comment, when Gnome has changed console keyboard layouts,
> "VC Keymap: n/a" shows on the output of "localectl" command. I am using the
> Finnish (DAS) keyboard layout.
Also, please have a look at `man localectl`:
> Note that the changes performed using this tool might require the initramfs to be rebuilt to take effect during early system boot. The initramfs is not rebuilt automatically by localectl.
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 4 months
[Bug 1203721] keyboard layout de-neo (Neo2) is broken
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1203721
Christian Stadelmann <rhbz2(a)genodeftest.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(rhbz2@genodeftest |
|.de) |
--- Comment #8 from Christian Stadelmann <rhbz2(a)genodeftest.de> ---
(In reply to Peter Hutterer from comment #7)
> sorry, this fell through. still an issue? The warnings themselves don't
> matter much btw, I think almost all layouts have multiple defined keys,
> that's just how we stack them.
No, I see no issues in daily usage. I just thought reporting these warnings
might help fixing their cause, but it seems like the warnings are ok.
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 4 months
[Bug 1410885] Media (volume) keys on Sun keyboard no longer work
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1410885
Peter Hutterer <peter.hutterer(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alt-gtk-de-sig(a)lists.fedora
| |project.org,
| |rdieter(a)gmail.com
Component|xkeyboard-config |mate-desktop
Assignee|peter.hutterer(a)redhat.com |fedora(a)raveit.de
--- Comment #9 from Peter Hutterer <peter.hutterer(a)redhat.com> ---
Based on Pawel's observations in Comment 8, I'm punting this back to mate.
Comment 1 also shows that X does the right thing, SunFront shows up in the xev
output. This is an issue with mapping the key in mate
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 4 months
[Bug 1203721] keyboard layout de-neo (Neo2) is broken
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1203721
Peter Hutterer <peter.hutterer(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |needinfo?(rhbz2@genodeftest
| |.de)
--- Comment #7 from Peter Hutterer <peter.hutterer(a)redhat.com> ---
sorry, this fell through. still an issue? The warnings themselves don't matter
much btw, I think almost all layouts have multiple defined keys, that's just
how we stack them.
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 4 months
[Bug 1470300] New: If eclipse-nls-* packages are installed eclipse fails to start
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1470300
Bug ID: 1470300
Summary: If eclipse-nls-* packages are installed eclipse fails
to start
Product: Fedora
Version: 26
Component: eclipse-nls
Severity: high
Assignee: sflaniga(a)redhat.com
Reporter: cquike(a)arcor.de
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, sflaniga(a)redhat.com
Created attachment 1297127
--> https://bugzilla.redhat.com/attachment.cgi?id=1297127&action=edit
/home/user/workspace/.metadata/.log
Description of problem:
After upgrading to Fedora 26, eclipse is unable to start. After selecting the
workspace a window appears with the following message;
"An error has occurred, See the log file
/home/user/workspace/.metadata/.log". I have attached that log file here
Version-Release number of selected component (if applicable):
# rpm -qa | grep eclipse
eclipse-p2-discovery-4.6.3-3.fc26.noarch
eclipse-linuxtools-5.3.1-2.fc26.noarch
eclipse-swt-4.6.3-3.fc26.x86_64
eclipse-gcov-5.3.1-2.fc26.noarch
eclipse-cdt-arduino-9.2.1-2.fc26.x86_64
eclipse-mylyn-tasks-bugzilla-3.21.0-4.fc26.noarch
eclipse-usage-4.4.3-1.fc26.noarch
eclipse-rpm-editor-5.3.1-2.fc26.noarch
eclipse-perf-5.3.1-2.fc26.noarch
eclipse-cdt-parsers-9.2.1-2.fc26.x86_64
eclipse-mylyn-builds-3.21.0-4.fc26.noarch
eclipse-ecf-core-3.13.3-2.fc26.x86_64
eclipse-nls-de-4.6.0-2.fc26.noarch
eclipse-e4-importer-0.2.0-0.3.gitb33919c.fc26.noarch
eclipse-emf-runtime-2.12.0-4.fc26.noarch
eclipse-contributor-tools-4.6.3-3.fc26.x86_64
eclipse-emf-core-2.12.0-4.fc26.x86_64
eclipse-valgrind-5.3.1-2.fc26.noarch
eclipse-cdt-docker-9.2.1-2.fc26.x86_64
eclipse-dtp-1.12.0-9.fc26.noarch
eclipse-platform-4.6.3-3.fc26.x86_64
eclipse-ptp-9.1.2-1.fc26.x86_64
eclipse-mylyn-versions-3.21.0-4.fc26.noarch
eclipse-abrt-0.0.3-2.fc26.noarch
eclipse-epp-logging-2.0.3-3.fc26.noarch
eclipse-packagekit-0.2.0-5.fc26.noarch
eclipse-mylyn-3.21.0-4.fc26.noarch
eclipse-tm-terminal-4.2.0-1.fc26.noarch
eclipse-nls-it-4.6.0-2.fc26.noarch
eclipse-subclipse-4.2.2-2.fc26.noarch
eclipse-swtbot-2.5.0-5.fc26.noarch
eclipse-cdt-native-9.2.1-2.fc26.x86_64
eclipse-pde-4.6.3-3.fc26.x86_64
eclipse-mylyn-context-java-3.21.0-4.fc26.noarch
eclipse-pydev-5.5.0-3.fc26.x86_64
eclipse-nls-fr-4.6.0-2.fc26.noarch
eclipse-mylyn-context-cdt-3.21.0-4.fc26.noarch
eclipse-gef-3.11.0-2.fc26.noarch
eclipse-equinox-osgi-4.6.3-3.fc26.x86_64
eclipse-linuxtools-libhover-5.3.1-2.fc26.noarch
eclipse-ecf-runtime-3.13.3-2.fc26.noarch
eclipse-launchbar-2.1.0-2.fc26.noarch
eclipse-egit-4.7.0-2.fc26.noarch
eclipse-fedorapackager-0.6.0-2.fc26.noarch
eclipse-cdt-llvm-9.2.1-2.fc26.x86_64
eclipse-nls-4.6.0-2.fc26.noarch
eclipse-changelog-5.3.1-2.fc26.noarch
eclipse-filesystem-1.0-8.fc26.x86_64
eclipse-gprof-5.3.1-2.fc26.noarch
eclipse-mylyn-docs-wikitext-3.21.0-4.fc26.noarch
eclipse-pydev-mylyn-5.5.0-3.fc26.x86_64
eclipse-mylyn-tasks-web-3.21.0-4.fc26.noarch
eclipse-remote-2.1.1-2.fc26.noarch
eclipse-cdt-qt-9.2.1-2.fc26.x86_64
eclipse-mylyn-tasks-trac-3.21.0-4.fc26.noarch
eclipse-linuxtools-docker-5.3.1-2.fc26.noarch
eclipse-linuxtools-vagrant-5.3.1-2.fc26.noarch
eclipse-nls-es-4.6.0-2.fc26.noarch
eclipse-cdt-tests-9.2.1-2.fc26.x86_64
eclipse-tm-terminal-connectors-4.2.0-1.fc26.noarch
eclipse-mylyn-builds-hudson-3.21.0-4.fc26.noarch
eclipse-cdt-9.2.1-2.fc26.x86_64
eclipse-rse-3.7.2-2.fc26.noarch
eclipse-mpc-1.5.4-1.fc26.noarch
eclipse-tests-4.6.3-3.fc26.x86_64
eclipse-oprofile-5.3.1-2.fc26.noarch
eclipse-jgit-4.7.0-7.fc26.noarch
eclipse-jdt-4.6.3-3.fc26.noarch
How reproducible:
Always
Steps to Reproduce:
1. Start eclipse in the command line
2. Select a workspace. In my case the workspace has been inherited from the
Fedora 25 installation.
Actual results:
A pop-up window appears with an error
Additional info:
As a workaround, removing the nls packages allows to start eclipse:
# dnf remove eclipse-nls-fr.noarch eclipse-nls-es.noarch eclipse-nls-de.noarch
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 4 months