Fedocal sync with gnome calendar
by Zoltan Hoppar
Hi
Maybe it's a silly question, but - how can I feed my gnome shell calendar
with Fedocal scheduled meetings? Is it possible to check time to time
updates, or need to download every time new ical files?
Thanks,
Zoltan
--
PGP: 06853DF7
7 years, 2 months
Re: powertop
by Chris Murphy
OK so basically powertop just doesn't work on this laptop. It appears
it doesn't realize it's running on battery. gnome-shell and upower
knows it's running on battery, but powertop doesn't report the wattage
being used by the battery, or a time remaining estimate. On another
(older) laptop with identical kernel and Fedora 25 updates, powertop
does have this information from the battery, and it's successfully
writing out to saved_results.powertop file.
7 years, 2 months
Re: Issue upgrading to F25
by Porfirio Andrés Páiz Carrasco
On Jan 12, 2017 7:42 PM, "Paolo Galtieri" <pgaltieri(a)gmail.com> wrote:
>
> I decided today to upgrade one of my systems to F25. I upgraded 2 others
a few weeks ago to F25 without issues. On this system, however, after it
downloads all the packages I get this error:
>
> warning:
/var/lib/dnf/system-upgrade/adobe-source-han-sans-tw-fonts-1.004-3.fc24.noarch.rpm:
Header V3 RSA/SHA256 Signature, key ID fdb19c98: NOKEY
> Curl error (37): Couldn't read a file:// file for
file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-x86_64 [Couldn't open file
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-x86_64]
> The downloaded packages were saved in cache until the next successful
transaction.
> You can remove cached packages by executing 'dnf clean packages'.
>
> I tried the download twice with the same error.
>
> If I try to run:
>
> sudo dnf system-upgrade reboot
>
> I get:
>
> Error: system is not ready for upgrade
>
> I'm upgrading from F22. Here are the steps I followed:
>
The day after Fedora 25 was released I also tried to upgrade my laptop from
fc22 to fc25, but I had some errors messages when dnf tried to solve some
dependencies related to Python.
So then tried upgrading to fc23, the process what smooth and without
issues. So upgrading from this old EOLifed version to the close its closest
release is possible, if no, try upgrading to the closest stable release
which is fc24.
Porfirio.
> sudo dnf upgrade --refresh
>
> sudo dnf install dnf-plugin-system-upgrade
>
> sudo dnf system-upgrade download --allowerasing --refresh --releasever=25
>
> sudo dnf system-upgrade reboot
>
> It appears the package:
>
> fedora-repos-25-1.noarch
>
> is not getting installed.
>
> Anyone know what I should do next?
>
> Any help is appreciated.
>
> Paolo
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
7 years, 2 months
vi
by Patrick Dupre
Hello,
I observe 2 different behaviours of vi that I cannot explain.
2 different machines, same distribution
On one machine when I underline some text with the mouse (not in append
mode), vi turns to a VISUAL mode, and not in the other machine.
Actually, I hate the VISUAL mode!
Thank for your help.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
7 years, 2 months
gnome-software not applying updates
by Chris Murphy
Found a bug, but just got hit by it again on another computer so I
think this might be more widespread and people won't figure it out
right away.
Gist is that if you have packagekit 1.1.4-2.fc25 (maybe on f24 also I
haven't tested that), when you click Restart & Install in
gnome-software, or check the Install Pending Updates in gnome-shell,
it won't actually apply the updates at next boot. You have to do 'sudo
dnf update PackageKit' reboot, and now the GUI initiated updates will
happen.
https://bugzilla.redhat.com/show_bug.cgi?id=1409268
--
Chris Murphy
7 years, 2 months
Confusing mockbuild error
by Laverne Schrock
Hi,
I am trying to build the RPMs from the following repo:
http://copr-dist-git.fedorainfracloud.org/cgit/jsouthworth/racket/racket.git
I cloned it down, ran `spectool -g *.spec`, and then `fedpkg --release f24
mockbuild`. This last command gives the following output:
Wrote: /rpms/racket/racket-6.7-1.fc24.src.rpm
INFO: mock.py version 1.3.3 starting (python version = 3.5.2)...
Start: init plugins
INFO: selinux enabled
Finish: init plugins
Start: run
ERROR: Cannot find/open srpm: /rpms/racket/-6.7-1.fc24.src.rpm. Error:
[Errno 2] No such file or directory: '/rpms/racket/-6.7-1.fc24.src.rpm'
Could not execute mockbuild: Command '['mock', '-r', 'fedora-24-x86_64',
'--resultdir', u'/rpms/racket/results_/6.7/1.fc24', '--rebuild',
u'/rpms/racket/-6.7-1.fc24.src.rpm']' returned non-zero exit status 1
Huh? Why is mockbuild looking for /rpms/racket/-6.7-1.fc24.src.rpm ?
/rpms/racket/racket-6.7-1.fc24.src.rpm does exist and renaming to the above
file and then rerunning the fedpkg command works fine.
Turning on verbosity doesn't help much:
Creating repo object from /rpms/racket
Could not determine the remote name: Cmd('git') failed due to: exit code(1)
cmdline: git config --get branch.f24.remote
Falling back to default remote name 'origin'
Running: rpmbuild --define '_sourcedir /rpms/racket' --define '_specdir
/rpms/racket' --define '_builddir /rpms/racket' --define '_srcrpmdir
/rpms/racket' --define '_rpmdir /rpms/racket' --define 'dist .fc24'
--define 'fedora 24' --eval '%undefine rhel' --define 'fc24 1' --nodeps -bs
/rpms/racket/racket.spec
Wrote: /rpms/racket/racket-6.7-1.fc24.src.rpm
Running: mock -r fedora-24-x86_64 --resultdir
/rpms/racket/results_/6.7/1.fc24 --rebuild /rpms/racket/-6.7-1.fc24.src.rpm
INFO: mock.py version 1.3.3 starting (python version = 3.5.2)...
Start: init plugins
INFO: selinux enabled
Finish: init plugins
Start: run
ERROR: Cannot find/open srpm: /rpms/racket/-6.7-1.fc24.src.rpm. Error:
[Errno 2] No such file or directory: '/rpms/racket/-6.7-1.fc24.src.rpm'
Cleaning up mock temporary config directory: None
Could not execute mockbuild: Command '['mock', '-r', 'fedora-24-x86_64',
'--resultdir', u'/rpms/racket/results_/6.7/1.fc24', '--rebuild',
u'/rpms/racket/-6.7-1.fc24.src.rpm']' returned non-zero exit status 1
Traceback (most recent call last):
File "/usr/bin/fedpkg", line 16, in <module>
main()
File "/usr/lib/python2.7/site-packages/fedpkg/__main__.py", line 77, in
main
sys.exit(client.args.command())
File "/usr/lib/python2.7/site-packages/pyrpkg/cli.py", line 1265, in
mockbuild
raise rpkgError(e)
pyrpkg.errors.rpkgError: Command '['mock', '-r', 'fedora-24-x86_64',
'--resultdir', u'/rpms/racket/results_/6.7/1.fc24', '--rebuild',
u'/rpms/racket/-6.7-1.fc24.src.rpm']' returned non-zero exit status 1
The host is running Fedora 24. Any idea what could be causing this?
- Laverne Schrock
7 years, 2 months
389-ds multi master replication not working
by gugankulandaivelu@gmail.com
I tried to setup 389ds multi master replication status. I'm getting this error message on the status bar. I don't receive any error during the replication setup process. Even I got the replication setup process success message window and asked me to check/verify the status on the replication status panel.
In Status panel, I see the below error message:
Last Update Message: Error (-1) Problem connecting to replica - LDAP error: Can't contact LDAP server (connection error)
I don't have any idea what's the reason for this error. Someone please help me to fix it. thanks.
7 years, 2 months
avahi mdns configuration question.
by Robin Laing
Hello,
I am trying to get mdns to work on my local network. I want all the
different computers to broadcast or at least allow their mdns host names
to be found by the router.
As more devices are appearing, I am seeing them in the router list but
not any of the Fedora machines.
I have searched but I cannot find anything that is allowing the router
to get the host name under zeroconfig.
Am I looking at the wrong configuration or is it not possible. The
router sees the computers when they boot into Windows.
Robin
7 years, 2 months
powertop
by Chris Murphy
[root at f25h ~]# ls -l /var/cache/powertop/
total 0
-rw-r--r--. 1 root root 0 Dec 29 14:49 saved_parameters.powertop
-rw-r--r--. 1 root root 0 Dec 29 14:49 saved_results.powertop
These files are always 0 length files. I'm not finding that any of the
calibration runs I've done are actually getting saved.
And each time I do a calibration...
[root at f25h ~]# powertop -c
modprobe cpufreq_stats failedLoaded 0 prior measurements
That suggests there are no measurements. So... is it broken on F25 or
am I missing something? I've asked on the powertop list and there's
been no reply.
--
Chris Murphy
7 years, 2 months
F25 libvirtd complains unsupported config, can't find a VG
by Chris Murphy
i'm seeing this in the journal.
Jan 09 14:20:25 f25h libvirtd[4511]: unsupported configuration: cannot
find any matching source devices for logical volume group 'vg'
Jan 09 14:20:25 f25h libvirtd[4511]: unsupported configuration: cannot
find any matching source devices for logical volume group 'vg'
Jan 09 14:20:25 f25h libvirtd[4511]: internal error: Failed to
autostart storage pool 'vg': unsupported configuration: cannot find
any matching source devices for logical vo
I'm also seeing the VG, which is named 'vg' inactive in virt-manager >
Edit > Connection Details > Storage and it can't be made active, I get
an error:
Error starting pool 'vg': unsupported configuration: cannot find any
matching source devices for logical volume group 'vg'
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 88, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 124, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 83, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/storagepool.py", line 164, in start
self._backend.create(0)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3315, in create
if ret == -1: raise libvirtError ('virStoragePoolCreate() failed',
pool=self)
libvirtError: unsupported configuration: cannot find any matching
source devices for logical volume group 'vg'
However, if I use virsh edit and just specify path to any LV on this
VG, the VM works and uses it without complains.
Soo....it's active as far as LVM is concerned but libvirtd won't
"manipulate" this pool even though it'll use LV's in it, for reasons I
can't figure out.
[root@f25h ~]# pvs
PV VG Fmt Attr PSize PFree
/dev/nvme0n1p7 vg lvm2 a-- 80.43g 47.43g
[root@f25h ~]# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log
Cpy%Sync Convert
macossierra vg -wi-a----- 32.00g
test vg -wi-a----- 1.00g
[root@f25h ~]# vgs
VG #PV #LV #SN Attr VSize VFree
vg 1 2 0 wz--n- 80.43g 47.43g
Any ideas?
--
Chris Murphy
7 years, 2 months