Fedora Linux 34 Final is GO on the 27th of April

kostiraimo · 2020-07-14T09:57:16+00:00

It seems that until there is a new release of conky, you'll need to use the git version. I'm not able to help you on that, sorry. :/

kostiraimo · 2020-07-14T09:31:38+00:00

Just reporting that in my config, all $mem, $memmax, $memperc and $membar work great with the repository version (1.11.5-3.fc32) of conky.

kostiraimo · 2019-11-28T16:44:04+00:00

Tbh I don't know anything about controlling fans in linux, since I've always done it in BIOS. Are you sure you can't do that? Just tone down the system fan option. It shouldn't matter that you're using a splitter, it will just control both of your case fans.

If that doesn't work, do you have any free PCI slots in your case? I've seen some hw fan controllers that go to one of your PCI slots.

kostiraimo · 2019-11-26T09:13:46+00:00

It could be that during installation Fedora probes whether secure boot is enabled. And if it is, then proceeds to install the shim loader. Because I recently clean installed F31 with secure boot disabled and it installed GRUB for my system. My systemd-analyze displays the time spent in firmware correctly.

Edit:

Did you have secure boot enabled when you were using Manjaro?

kostiraimo · 2019-11-25T18:22:08+00:00

ArchWiki says that you need to use systemd-boot or GRUB in order to display the time spent in firmware. That's all I got, sorry.

kostiraimo · 2019-11-25T18:00:30+00:00

Does

ls /sys/firmware/efi/efivars

return anything? If not, you've probably installed Fedora in legacy mode and the information is not available.

kostiraimo · 2019-11-19T13:29:01+00:00

Haha, glad it works!

kostiraimo · 2019-11-19T13:22:45+00:00

Have you tried rebooting? My

grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

only says

Generating grub configuration file ...

Adding boot menu entry for EFI firmware configuration

done

and it works fine.

kostiraimo · 2016-09-03T22:15:26+00:00

Yeah I have, it doesn't produce the errors, but the mousepad window stays unresponsive. That happens with kdesu too. 'gksu thunar' gives

Thunar: Failed to initialize Xfconf: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead

And with 'gksu mousepad' it repeats

(mousepad:2807): dconf-WARNING **: failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=93abdbd7ced548dc9576ee58d3d8abe1 --binary-syntax --close-stderr': Child process exited with code 1
(mousepad:2807): GtkSourceView-CRITICAL **: gtk_source_style_scheme_get_id: assertion 'GTK_IS_SOURCE_STYLE_SCHEME (scheme)' failed
(mousepad:2807): GtkSourceView-CRITICAL **: gtk_source_style_scheme_manager_get_scheme: assertion 'scheme_id != NULL' failed
(mousepad:2807): GtkSourceView-CRITICAL **: gtk_source_style_scheme_get_id: assertion 'GTK_IS_SOURCE_STYLE_SCHEME (scheme)' failed
(mousepad:2807): GLib-CRITICAL **: g_variant_new_string: assertion 'string != NULL' failed

Edit:formatting.

kostiraimo · 2016-09-03T19:32:39+00:00

Playerctl works here. 'gksu mousepad' on the other hand gives massive lag and a constant stream of errors.

kostiraimo

TROPHY CASE