+ Added reading of estimated time to fully charged battery
(time_to_full_now)
The remaining time is calculated if the value is not provided
in the battery information.
If the battery does not provide charging current information,
the estimated time to charge the battery cannot be calculated.
Signed-off-by: Slávek Banko <slavek.banko@axis.cz>
+ The current frequency is parsed from the scaling_cur_freq file
If the current frequency is not found in /proc/cpuinfo, the attempt
to read value from cpuinfo_cur_freq failed because only root can
read this file.
+ The have_frequency flag is not set when parsing current frequency from sysfs
Setting the have_frequency flag after parsing current frequency for the
first core caused the current frequency not to be parsed for other cores.
+ Frequency characteristics are parsed for all cores
The assumption that the frequency characteristics for all cores will be
the same as the first core is no longer reliable. There are heterogeneous
architectures - for example ARM big.LITTLE.
Signed-off-by: Slávek Banko <slavek.banko@axis.cz>
+ Added initialization of all values
Some batteries do not provide all values and, without
initialization, values may contain dubious data.
+ Added reading of current battery capacity value in percent
(capacity)
Some batteries may provide the current capacity value in
percent instead of the current energy value.
+ Added check whether the battery provides current energy value
(charge_now or energy_now)
The current energy is calculated if the value is not provided
in the battery information.
+ Added reading of estimated time to empty battery
(time_to_empty_now)
The remaining time is calculated if the value is not provided
in the battery information.
If the battery does not provide charging current information,
the estimated time to charge the battery cannot be calculated.
Signed-off-by: Slávek Banko <slavek.banko@axis.cz>
It is very unclear at this point what a valid use case for this feature
would possibly be. The old documentation only mentions $(hostname) as
an example, which can be done with $HOSTNAME instead.
Note that $(...) is still supported in Exec lines of desktop files,
this does not require [$e] anyway (and actually works better without it,
otherwise the $ signs need to be doubled to obey tdeconfig $e escaping rules...).
Based on KDE Frameworks 5 kconfig patch for CVE-2019-14744.
This resolves issue #45.
Signed-off-by: Slávek Banko <slavek.banko@axis.cz>
1. added disk helper source files
2. removed WITH_UDISKS2, WITH_UDISK, WITH_UDEVIL defines. The respective code is always included
3. order of execution for mount/umount activities: udisks2, udisk, udevil, pmount.
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
Use interface name in TDENetworkConnectionManager_BackendNM instead of MAC address
This relates to bug 2748
The name of the network interface seems to be a more stable identifier than the MAC
address because the MAC address can be changed easily or even automatically - see
randomization of MAC addresses on wireless interfaces. Therefore, the use of the
MAC address as a network interface identifier was abandoned.
Beware, this change is an API / ABI change! However, most changes are internal
and the only one affected is application TDENetworkManager.
Signed-off-by: Slávek Banko <slavek.banko@axis.cz>
Matías Fonzo
François Andriot
Chris
Anton Repko
Roman Savochenko