Ask Your Question

mkungla's profile - activity

2017-10-29 19:02:41 -0500 answered a question I can't login after upgrading to fedora 25

I had similar issue multiple cases and always was the reason that I had compiled or installed proprietary graphics driver from src or unofficial repo which caused upon upgrade initramfs not to rebuild correctly. Especially in case of kernel update.

Solution was to simply login via pseudo terminal ctrl+alt+f2

uninstall and reinstall graphics driver based on instruction depending of driver installed and reboot which always have worked out and solved the issue for me.

Even if that is not solution for problem you had I hope that it helps someone facing similar problem I had!

2017-03-14 18:21:00 -0500 received badge  Scholar (source)
2017-03-14 18:20:42 -0500 received badge  Famous Question (source)
2016-11-26 15:43:13 -0500 commented answer How can I install a minimal GNOME desktop on F22 Server?

sudo dnf systemctl set-default graphical.target should be without dnf so just sudo systemctl set-default graphical.target...

2016-09-19 01:15:55 -0500 received badge  Notable Question (source)
2016-09-14 07:04:21 -0500 commented answer How would I make adjustment of brightness available for users?

Option "ACPI_OSI=" did not get backlight keys working on f25 with that. Instead I wrote small python lib to control my ROG keyboard backlight via the D-Bus interface. Asus ROG Linux extras

2016-09-09 18:46:08 -0500 asked a question How would I make adjustment of brightness available for users?

I was searching how to enable ASUS ROG G752 keyboard leds and I didn't find any info on that subject besides that - it is not possible to enable these. However I discovered kernel has there something to provide this and that it is so easy to enable these as root. There is 3 brightness levels so,

disable leds : echo 0 >> /sys/class/leds/asus\:\:kbd_backlight/brightness

max brightness: echo 3 >> /sys/class/leds/asus\:\:kbd_backlight/brightness

So how would I make this available for users?

2016-03-24 10:47:32 -0500 received badge  Popular Question (source)
2016-03-16 19:11:02 -0500 received badge  Nice Answer (source)
2016-03-16 17:53:06 -0500 received badge  Teacher (source)
2016-03-16 17:53:06 -0500 received badge  Necromancer (source)
2016-01-26 12:56:28 -0500 commented question How to install .tar file

Btw change your question title to something like 'How to install FlashTool' or 'problem while seting up FlashTool'

2016-01-18 13:36:58 -0500 received badge  Citizen Patrol (source)
2016-01-17 13:15:21 -0500 answered a question Failed to obtain the transaction lock (logged in as: root).

This is something occouring once a while and has been reported as bug over several Fedora releases. These bug's have been closed and then reopened and so on, for instance Red Hat Bugzilla bug #1204488.

While searching the solution you most likely come across multitude of suggestions.
which may or may not work for you.

So most cases root cause of this problem is surely that previous dnf upgrade | install got interrupted.
it could be that you your self canceled the transaction by pressing Ctrl+c or other user was running transaction or any other reason out of million interrupted the transaction.

  • As @pnadk mentioned first thing indeed you could try to remove rm /var/cache/dnf/metadata_lock.pid

    However your problem might not disappear, for instance you don't have this lock file there. Or you deleted it and still have the same problem Error: Could not run transaction ...

  • You might have tried systemd-tmpfiles --remove dnf.conf

  • Or dnf clean all
  • Or If you ran dnf under a regular user, without the noroot plugin installed then install the plugin
    dnf install dnf-plugins-core
  • You might have tried to search dnf processes running and killing them kill pid, kill -9 pid, kill {x}
  • You might have tried to search cache files and deleting them manually

And still the same story...
Just before you pull your hairs out take a note:
You might have already solved the issue at first step just restart you PC and you are most likely good to go!

2016-01-16 09:42:01 -0500 received badge  Editor (source)
2016-01-16 09:41:02 -0500 answered a question After a kernel update cannot decrypt the lux partition due to the change of keyboard layout

When you can not decrypt your LUKS partition after kernel update and you have possibility that this is because you use multiple keyboard layouts then here are following two of the solutions.

  • 1th Try to enter your passphrase by using key's matching your input sources used. You just might be lucky to use correct keymap and you can decrypt you partition. And you have to remember that for now-on that this is the input source layout you have to use while entering your LUKS pass phrase.

So if you installed Fedora and created your LUKS partition with en_US layout and
now updated your kernel while using for instance nl_NL input source then from now on you
you have to use nl_NL layout for your LUKS pass phrase.
That repeats it's self over and over again every time when you upgrade the kernel, so if next time upgrading
the Kernel and you happend to have en_US active then LUKS passphrase will map to this.

  • 2nd option is to remove last updated kernel

1. Boot up to previous kernel which worked before update and just verify current kernel used.

[root@local ]# uname -a

2. Find last downloaded kernel.

root@local ]# rpm -qa | grep kernel

3. From the list find kernel packages choose one which cause you a trouble and run following by replacing package names with ones you want to remove.

[root@local ]#  dnf remove kernel-4.2.5-300.fc23.x86_64 kernel-modules-4.2.5-300.fc23.x86_64 kernel-core-4.2.5-300.fc23.x86_64

4. Set your keyboard language to one which is your primary or you used when creating the LUKS passphrase for your disk,

5. and update the kernel.

[root@local ]# dnf upgrade

and you are good to go and boot with updated kernel and use your passphrase mapping to input source you want.

Conclusion:

While installing Fedora and checking option

Encrypt my data. You'll set a passphrase next

Then in DISK ENCRYPTION PASSPHRASE dialog you'll get following warning.

Warning: You won't be able to switch between keyboard layouts (from the default one) when you decrypt your disk after install.

So that is not entirely true, since you can change it when you change you input source before kernel update. So after kernel update keyboard layout set before is used instead of your (default one).

2016-01-16 09:03:28 -0500 received badge  Autobiographer
2016-01-15 11:50:10 -0500 received badge  Good Question (source)
2016-01-15 11:21:37 -0500 commented question Retrieve complete list of manually installed packages

This question should also include the dnf tag.

2016-01-15 11:05:47 -0500 commented question After a kernel update cannot decrypt the lux partition due to the change of keyboard layout

@Florian Well I use in my pass lot of special characters so these are the ones messing it up and my pass lengths are avg 15+ char :).

probably know where the keys are located

Indeed I can just enter my pass as test driven so if it does not accept it, then try key combination of other language if not then another.

Changing the keyboard layout should not affect the keyboard layout in an early stage like LUKS password dialog

It only occurs when you change you input source before kernel update. I believe key change was also warned in Fedora installation progress while setting up LUKS

2016-01-15 10:48:18 -0500 commented answer How to delete old kernel version from grub.

@FranciscoD_ well answered for not really well formatted question. I find that extremely crucial that

By default, Fedora will retain the three latest kernels

Also I find it pointless to remove these manually since the space overhead is so small that on any fairly modern hardware One should not concern about it all. By default Fedora boots up using latest installed kernel anyway and removes oldest of three when you get kernel update. My Q which explicitly gives good example why One should be interested having older kernels kept for a while my question

2016-01-15 10:24:36 -0500 received badge  Nice Question (source)
2016-01-15 10:11:06 -0500 received badge  Supporter (source)
2016-01-15 09:57:25 -0500 received badge  Student (source)
2016-01-15 09:43:11 -0500 asked a question After a kernel update cannot decrypt the lux partition due to the change of keyboard layout

I'm using Fedora 23, LUKS encrypted disk and multiple keyboard input sources for all the languages I'm daily using and switching between. When there is kernel update available and I forget to switch to enUS as primary keyboard layout then I can not decrypt LUKS partition since wrong keyboard layout is set when I update kernel.

So I solved this issue by booting up to previous kernel which worked before update and just verify current kernel used.

[root@local ]# uname -a
Linux local.localhost 4.2.3-300.fc23.x86_64 #1 SMP Mon Oct 5 15:42:54 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

then found last updated/downloaded kernel...

[root@local ]# rpm -qa | grep kernel
kernel-4.2.5-300.fc23.x86_64
kernel-core-4.2.5-300.fc23.x86_64
kernel-modules-4.2.5-300.fc23.x86_64
kernel-4.2.3-300.fc23.x86_64
kernel-core-4.2.3-300.fc23.x86_64
kernel-modules-4.2.3-300.fc23.x86_64
kernel-4.2.0-300.fc23.x86_64
kernel-core-4.2.0-300.fc23.x86_64
kernel-modules-4.2.0-300.fc23.x86_64
libreport-plugin-kerneloops-2.6.3-1.fc23.x86_64
abrt-addon-kerneloops-2.7.0-1.fc23.x86_64

so from the list took obviously highest version nr, one which was causing problem and removed the listed kernel packages.

[root@local ]#  dnf remove kernel-4.2.5-300.fc23.x86_64 kernel-modules-4.2.5-300.fc23.x86_64 kernel-core-4.2.5-300.fc23.x86_64

then made sure that my primary language enUS is selected and updated kernel again

[root@local ]# dnf upgrade

After the kernel update is done I can decrypt my LUKS partition and everything is fine but my question is. Can this issue if occurs be solved some other way (faster) or is there way to prevent that happening even when I use many keyboard layouts? And which input source, kernel update uses. One which is currently active or one which is set as primary (first in the list) PS: I'm using gnome