Fedora 20 updates-testing report
The following Fedora 20 Security updates need testing: Age URL 17 https://admin.fedoraproject.org/updates/FEDORA-2013-17828/davfs2-1.4.7-3.fc20 16 https://admin.fedoraproject.org/updates/FEDORA-2013-17866/chicken-4.8.0.4-4.fc20 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18703/dropbear-2013.59-1.fc20 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18705/phpMyAdmin-3.5.8.2-1.fc20 3 https://admin.fedoraproject.org/updates/FEDORA-2013-18877/libtar-1.2.11-27.fc20 1 https://admin.fedoraproject.org/updates/FEDORA-2013-18982/xen-4.3.0-8.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2013-18840/ReviewBoard-1.7.16-2.fc20,python-djblets-0.7.21-1.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2013-19101/scipy-0.12.1-1.fc20 The following Fedora 20 Critical Path updates have yet to be approved: Age URL 9 https://admin.fedoraproject.org/updates/FEDORA-2013-18435/uboot-tools-2013.10-0.5.rc4.fc20 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18709/mdadm-3.3-3.fc20 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18741/python-meh-0.27-1.fc20 1 https://admin.fedoraproject.org/updates/FEDORA-2013-18959/taglib-1.9.1-1.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2013-19099/openssl-1.0.1e-27.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2013-19105/kernel-3.11.5-300.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2013-19106/kde-settings-20-4.fc20,sddm-0.2.0-0.13.20130914git50ca5b20.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2013-19058/gstreamer-plugins-base-0.10.36-6.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2013-19085/pulseaudio-4.0-7.gitf81e3.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2013-19089/gstreamer-0.10.36-6.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2013-19083/pam-1.1.8-1.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2013-19086/openldap-2.4.36-2.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2013-19084/samba-4.1.0-1.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2013-19074/qtwebkit-2.3.3-1.fc20 The following builds have been pushed to Fedora 20 updates-testing certmonger-0.68-1.fc20 gabedit-2.4.7-3.fc20 hmaccalc-0.9.13-1.fc20 kde-settings-20-4.fc20 kernel-3.11.5-300.fc20 krb5-1.11.3-24.fc20 libchewing-0.3.5-1.fc20 libinfinity-0.5.4-4.fc20 libmikmod-3.3.2-2.fc20 mariadb-5.5.33a-2.fc20 mikmod-3.2.3-1.fc20 openssl-1.0.1e-27.fc20 perl-Hash-MoreUtils-0.04-1.fc20 php-pear-1.9.4-23.fc20 python-jsonpatch-1.2-2.fc20 python-warlock-1.0.1-1.fc20 rubygem-excon-0.25.3-1.fc20 rubygem-fog-1.15.0-1.fc20 rubygem-heroku-api-0.3.15-1.fc20 rubygem-shindo-0.3.8-1.fc20 scipy-0.12.1-1.fc20 sddm-0.2.0-0.13.20130914git50ca5b20.fc20 thrift-0.9.1-7.fc20 Details about builds: certmonger-0.68-1.fc20 (FEDORA-2013-19103) Certificate status monitor and PKI enrollment client Update Information: This update allows certmonger to better detect when its attempts to save keys or certificates fail due to lack of permissions. ChangeLog: * Thu Aug 29 2013 Nalin Dahyabhai 0.68-1 - notice when the OpenSSL RNG isn't seeded - notice when saving certificates or keys fails due to filesystem-related permission denial (#996581) References: [ 1 ] Bug #996581 - When getcert cannot create the key or certificate, the error should state permission denied https://bugzilla.redhat.com/show_bug.cgi?id=996581 gabedit-2.4.7-3.fc20 (FEDORA-2013-18960) GUI for computational chemistry Update Information: From upstream changelog: * Bug fixed for reading basis with d,f,.. orbitals from a fchk file. Only fchk file is concerned by this bug (There was no bug for reading from a .log file) ChangeLog: * Mon Oct 14 2013 Dominik Mierzejewski 2.4.7-3 - drop the gtk patch and build with -DENABLE_DEPRECATED - fix crashes when user doesn't select any folder in dialog * Sun Oct 13 2013 Dominik Mierzejewski 2.4.7-2 - drop some erroneous hunks from gtk patch * Sat Oct 12 2013 Dominik Mierzejewski 2.4.7-1 - updated to latest development version (2.4.7) - rebased and updated -gtk patch - fixed some compiler warnings (missing includes) - attempt to fix bug #774594 -
avahi/mDNS in qemu/kvm
Are multiple avahi/mDNS instances supposed to reliably work on one NIC with virtual machines? I'm experiencing hostname resolution failure with avahi about 1 minute after avahi-daemon.service starts. Nothing is recorded in the journal in between working and not working. I've disabled firewalld in the VM and on the host and get the same results. The baremetal host I can ssh to/from without there ever being a problem: ssh chris@f20s.local The qemu/kvm guest, I can ssh to/from intermittently: ssh chris@f20sv.local If I constantly log out and login, it always works, for 3-4 minutes. If I stop doing that for even 20 or seconds, the next attempt I get: ssh: Could not resolve hostname f20sv.local: nodename nor servname provided, or not known When that happens, I can still login the old fashioned way, ssh ch...@192.168.1.xxx and this succeeds. I can then 'systemctl restart avahi-daemon" and for a short while I can once again ssh/scp to my heart's content. Then it stops working. It is almost like a service like a firewall is taking a bit of time to cut it off, but then does so. But firewalld is not running on host or guest. I'm not sure how to troubleshoot this further in the event it's not expected behavior. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Mon, Oct 14, 2013 at 2:41 PM, Eric Blake wrote: > Dunno. Whatever I got by installing F17 with anaconda then > incrementally upgrading through F18, F19, and now F20, and where I set > up my /etc/fstab by copying the same configuration that worked for me > since F12 pre-systemd days. So it might not be ideal, but it's one of > those "it works well enough for me that I'm not going to waste time > tweaking it unless it breaks first" situations. Except that it's > noticeably broken enough at shutdown that I bothered to ask on the list :) > > The corresponding /etc/fstab entry: > > nas:/backup /mnt/backup nfs bg,user,_netdev 0 0 Okay, so the "bg" option is a little different from what most people refer to as automounting, in that it just repeatedly attempts to mount the share until it succeeds, whereas true automounting waits until you attempt to access the mount to even try to mount it. Of course, this distinction matters very little to _you_, but it might indicate what systemd is getting wrong here. I'm curious as to whether systemd even tracks the mount properly in this case. Does `systemctl status mnt-backup.mount` indicate success or failure? If it indicates success, systemd definitely should be tearing down the mount on shutdown. (systemd by design is supposed to reverse Before/After deps for stop operations.) Definitely file a bug in this instance. If it indicates failure, systemd isn't getting informed that this mount actually succeeds. You could file a bug against systemd regarding this, but their answer might just be "use real automounting if you want this to work properly." To do that, switch your "bg" mount option for "x-systemd.automount" and see if it gets unmounted properly on shutdown afterwards. Their answer could just as easily be "yeah, we need to fix this", so please do file the bug anyway, if only for the benefit of others who might run into this. -T.C. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On 10/14/2013 03:27 PM, T.C. Hollingsworth wrote: > On Mon, Oct 14, 2013 at 9:04 AM, Eric Blake wrote: >> I've got a similar problem - I've got my laptop set up to automount an >> NFS share over wifi, and frequently hit a hang during system shutdown >> because systemd allows Networkmanager (and the wifi) to be taken down >> before NFS is fully unmounted, where the system then stalls for several >> minutes waiting for the NFS unmount that is impossible at that point. I >> have no idea where to look at adding a dependency that says that yes, my >> wifi network connection really must have a longer lifetime on BOTH sides >> of the NFS mount point. > > Are you using systemd's automounting logic or plain ol' autofs? Dunno. Whatever I got by installing F17 with anaconda then incrementally upgrading through F18, F19, and now F20, and where I set up my /etc/fstab by copying the same configuration that worked for me since F12 pre-systemd days. So it might not be ideal, but it's one of those "it works well enough for me that I'm not going to waste time tweaking it unless it breaks first" situations. Except that it's noticeably broken enough at shutdown that I bothered to ask on the list :) The corresponding /etc/fstab entry: nas:/backup /mnt/backup nfs bg,user,_netdev 0 0 # systemctl list-dependencies mnt-backup.mount mnt-backup.mount ├─-.mount ├─system.slice └─network-online.target └─NetworkManager-wait-online.service -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Mon, Oct 14, 2013 at 9:04 AM, Eric Blake wrote: > I've got a similar problem - I've got my laptop set up to automount an > NFS share over wifi, and frequently hit a hang during system shutdown > because systemd allows Networkmanager (and the wifi) to be taken down > before NFS is fully unmounted, where the system then stalls for several > minutes waiting for the NFS unmount that is impossible at that point. I > have no idea where to look at adding a dependency that says that yes, my > wifi network connection really must have a longer lifetime on BOTH sides > of the NFS mount point. Are you using systemd's automounting logic or plain ol' autofs? -T.C. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Mon, Oct 14, 2013 at 8:56 AM, Mike Chambers wrote: > Ok, think I've figured out the problem, but might be beyond my expertise > to fix it.. > > 1 - Network Manager is set to come online/start > 2 - Network Manger wait-online shows in log as well here. > 3 - Network Manger device itself shows up (as in I guess drivers and > assigned what name it is called, p5p1 is my wired ethernet). > 4 - Systemd tries here to mount the remote nfs directory, which fails > 5 - Network Manger actually configures itself, via dhcp, to get it's > network settings, such as IP, dns, etc.. > > So it seems, via /var/log/messages that nfs is trying to get mounted > BEFORE the network is completely configured. There are several possibilities here: 1.) DHCP on your network is slw and NetworkManager-wait-online is timing out after the default 30s waiting for it. 2.) NetworkManager-wait-online is just stupid and doesn't wait for DHCP to complete. 3.) NM-wait-online is working fine, but systemd isn't waiting for it for some reason. I believe something in the logs would indicate if it's 1. If that's the case, you can increase the timeout by copying /usr/lib/systemd/system/NetworkManager-wait-online.service to /etc/systemd/system/ (so rpm doesn't overwrite your changes on updates) and increasing the `-t` argument to `nm-online` in that file. If it's 2, file a bug against NetworkManager, which ships the `nm-online` program that is being stupid. :-p If it's 3, systemd obviously deserves the bug. > So no idea which one is wrong, either mounting gets done alot later > (guess I could add to rc.local again like used to until fixed?), or NM > needs to be configured a lot earlier. Well, lets try a more systemd-esque hack that will also identify whether the problem is 2 or 3 as described above. Drop something like this in /etc/systemd/system/really-wait-online.service: -- [Unit] Description=Really wait for the damn network Requisite=NetworkManager.service After=NetworkManager.service Wants=network.target Before=network.target network-online.target [Service] Type=oneshot ExecStart=/bin/bash -c 'until ifconfig p5p1 | grep '192.\168'; do continue; done' TimeoutSec=120 [Install] WantedBy=multi-user.target -- Remember to adjust the network interface and grep string to something that makes sense for your network, and run `systemctl daemon-reload && systemctl enable really-wait-online.service` to enable it when you're done. (And if you're aware of a better method for figuring out DHCP is done than grepping the output of `ifconfig`, feel free to use it. ;-) If mounting works after that, NM-wait-online is really the culprit and NetworkManager deserves the bug. If mounting still fails, systemd is not ordering things right and deserves the bug. And if systemd is to blame, fix your system nao by explicitly ordering your little wait-online service before the mount unit (e.g. mnt-foo.mount) discussed upthread. Just add said mount unit to the end of the Before line in that file. -T.C. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 18 updates-testing report
The following Fedora 18 Security updates need testing: Age URL 177 https://admin.fedoraproject.org/updates/FEDORA-2013-6117/eucalyptus-3.2.2-1.fc18 25 https://admin.fedoraproject.org/updates/FEDORA-2013-17112/hplip-3.13.9-2.fc18 24 https://admin.fedoraproject.org/updates/FEDORA-2013-17195/spice-gtk-0.18-3.fc18 20 https://admin.fedoraproject.org/updates/FEDORA-2013-17431/thunderbird-17.0.9-1.fc18 18 https://admin.fedoraproject.org/updates/FEDORA-2013-17635/wireshark-1.10.2-4.fc18 16 https://admin.fedoraproject.org/updates/FEDORA-2013-17853/davfs2-1.4.7-3.fc18 15 https://admin.fedoraproject.org/updates/FEDORA-2013-17912/chicken-4.8.0.4-4.fc18 15 https://admin.fedoraproject.org/updates/FEDORA-2013-17904/fedmsg-0.7.1-2.fc18 8 https://admin.fedoraproject.org/updates/FEDORA-2013-18401/fping-3.5-3.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18606/dropbear-2013.59-1.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18647/gnupg-1.4.15-1.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18686/mod_fcgid-2.3.9-1.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-18802/phpMyAdmin-3.5.8.2-1.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-18785/libtar-1.2.11-25.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-18774/icu-49.1.1-12.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-18814/gnupg2-2.0.22-1.fc18,libgpg-error-1.11-1.fc18 0 https://admin.fedoraproject.org/updates/FEDORA-2013-19053/xen-4.2.3-4.fc18 The following Fedora 18 Critical Path updates have yet to be approved: Age URL 247 https://admin.fedoraproject.org/updates/FEDORA-2013-2192/nautilus-3.6.3-5.fc18 12 https://admin.fedoraproject.org/updates/FEDORA-2013-18050/gdb-7.5.1-43.fc18 11 https://admin.fedoraproject.org/updates/FEDORA-2013-18164/perl-threads-1.89-1.fc18 10 https://admin.fedoraproject.org/updates/FEDORA-2013-18276/dnsmasq-2.65-8.fc18 8 https://admin.fedoraproject.org/updates/FEDORA-2013-18402/keyutils-1.5.8-1.fc18 8 https://admin.fedoraproject.org/updates/FEDORA-2013-18380/ibus-1.5.4-2.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18607/libxklavier-5.4-1.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18622/selinux-policy-3.11.1-106.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18590/usbmuxd-1.0.8-9.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18680/akonadi-1.10.3-1.fc18,qt-4.8.5-10.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18383/thunderbird-enigmail-1.6-1.fc18,thunderbird-24.0-3.fc18,thunderbird-lightning-2.6-1.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-18814/gnupg2-2.0.22-1.fc18,libgpg-error-1.11-1.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-18774/icu-49.1.1-12.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-18815/sane-backends-1.0.24-1.fc18 0 https://admin.fedoraproject.org/updates/FEDORA-2013-19021/taglib-1.9.1-1.fc18 0 https://admin.fedoraproject.org/updates/FEDORA-2013-19026/python-markupsafe-0.18-1.fc18 The following builds have been pushed to Fedora 18 updates-testing alexandria-0.6.9-7.fc18 anki-2.0.13-1.fc18 cnucnu-0-0.15.20131007git606929ec.fc18 drbdlinks-1.25-1.fc18 kmymoney-4.6.4-1.fc18 mate-document-viewer-1.6.1-6.fc18 mate-file-archiver-1.6.1-0.1.git95ebd69.fc18 mate-power-manager-1.6.3-0.1.gitbc54d96.fc18 mate-screensaver-1.6.1-3.fc18 numatop-1.0.1-5.fc18 perl-Math-NumSeq-65-1.fc18 php-bartlett-PHP-Reflect-1.9.0-1.fc18 php-xcache-3.0.4-1.fc18 python-formencode-1.2.6-1.fc18 python-markupsafe-0.18-1.fc18 qlandkartegt-1.7.5-1.fc18 qpdfview-0.4.6-1.fc18 qtdbf-1.0.0-1.fc18 rubygem-domain_name-0.5.13-2.fc18 taglib-1.9.1-1.fc18 tlock-1.5-8.fc18 xen-4.2.3-4.fc18 xfce4-whiskermenu-plugin-1.1.1-1.fc18 youtube-dl-2013.10.09-1.fc18 Details about builds: alexandria-0.6.9-7.fc18 (FEDORA-2013-19049) Book collection manager Update Information: In some cases cursor position was recorded as negative value, which caused alexandria not launching any more. This new rpm will fix this issue. ChangeLog: * Mon Oct 7 2013 Mamoru TASAKA - 0.6.9-7 - Read negative value as integer in case position has such value (bug 1014295) References: [ 1 ] Bug #1014295 - alexandria won't launch when position has negative value https://bugzilla.redhat.com/show_bug.cgi?id=1014295 ===
Re: Fedora 20 nfs
On 10/14/2013 09:56 AM, Mike Chambers wrote: > On Sun, 2013-10-13 at 18:24 -0700, T.C. Hollingsworth wrote: > >> One thing I forgot that's always an issue...do you use NetworkManager >> or ye olde network service? If it's the former, try running >> `systemctl enable NetworkManager-wait-online` and rebooting. >> Sometimes systemd tries to mount stuff before NM gets the network up. >> (I thought they had fixed this to just do the right thing when remote >> FSes were in the mix nowadays, but maybe I'm mistaken. Or it broke >> again with F20??) > > Ok, think I've figured out the problem, but might be beyond my expertise > to fix it.. > > 1 - Network Manager is set to come online/start > 2 - Network Manger wait-online shows in log as well here. > 3 - Network Manger device itself shows up (as in I guess drivers and > assigned what name it is called, p5p1 is my wired ethernet). > 4 - Systemd tries here to mount the remote nfs directory, which fails > 5 - Network Manger actually configures itself, via dhcp, to get it's > network settings, such as IP, dns, etc.. > > So it seems, via /var/log/messages that nfs is trying to get mounted > BEFORE the network is completely configured. > > So no idea which one is wrong, either mounting gets done alot later > (guess I could add to rc.local again like used to until fixed?), or NM > needs to be configured a lot earlier. I've got a similar problem - I've got my laptop set up to automount an NFS share over wifi, and frequently hit a hang during system shutdown because systemd allows Networkmanager (and the wifi) to be taken down before NFS is fully unmounted, where the system then stalls for several minutes waiting for the NFS unmount that is impossible at that point. I have no idea where to look at adding a dependency that says that yes, my wifi network connection really must have a longer lifetime on BOTH sides of the NFS mount point. -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Sun, 2013-10-13 at 18:24 -0700, T.C. Hollingsworth wrote: > One thing I forgot that's always an issue...do you use NetworkManager > or ye olde network service? If it's the former, try running > `systemctl enable NetworkManager-wait-online` and rebooting. > Sometimes systemd tries to mount stuff before NM gets the network up. > (I thought they had fixed this to just do the right thing when remote > FSes were in the mix nowadays, but maybe I'm mistaken. Or it broke > again with F20??) Ok, think I've figured out the problem, but might be beyond my expertise to fix it.. 1 - Network Manager is set to come online/start 2 - Network Manger wait-online shows in log as well here. 3 - Network Manger device itself shows up (as in I guess drivers and assigned what name it is called, p5p1 is my wired ethernet). 4 - Systemd tries here to mount the remote nfs directory, which fails 5 - Network Manger actually configures itself, via dhcp, to get it's network settings, such as IP, dns, etc.. So it seems, via /var/log/messages that nfs is trying to get mounted BEFORE the network is completely configured. So no idea which one is wrong, either mounting gets done alot later (guess I could add to rc.local again like used to until fixed?), or NM needs to be configured a lot earlier. -- Mike Chambers Madisonville, KY "Best little town on Earth!" -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
[Test-Announce] Fedora 20 Beta Test Compose 4 (TC4) Available Now!
NOTE: The 32- and 64-bit DVDs, the 64-bit LXDE Live, and the 32- and 64-bit Security Spins are over their respective size targets. As per the Fedora 20 schedule [1], Fedora 20 Beta Test Compose 4 (TC4) is now available for testing. Content information, including changes, can be found at https://fedorahosted.org/rel-eng/ticket/5787#comment:5 . Please see the following pages for download links (including delta ISOs) and testing instructions. Normally dl.fedoraproject.org should provide the fastest download, but download-ib01.fedoraproject.org is available as a mirror (with an approximately 1 hour lag) in case of trouble. To use it, just replace "dl" with "download-ib01" in the download URL. Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Base: https://fedoraproject.org/wiki/Test_Results:Current_Base_Test Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Ideally, all Alpha and Beta priority test cases for Installation [2], Base [3], and Desktop [4] should pass in order to meet the Beta Release Criteria [5]. Help is available on #fedora-qa on irc.freenode.net [6], or on the test list [7]. Create Fedora 20 Beta test compose (TC) and release candidate (RC) https://fedorahosted.org/rel-eng/ticket/5787 Current Blocker and Freeze Exception bugs: http://qa.fedoraproject.org/blockerbugs/current [1] http://fedorapeople.org/groups/schedule/f-20/f-20-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Installation_validation_testing [3] https://fedoraproject.org/wiki/QA:Base_validation_testing [4] https://fedoraproject.org/wiki/QA:Desktop_validation_testing [5] https://fedoraproject.org/wiki/Fedora_20_Beta_Release_Criteria [6] irc://irc.freenode.net/fedora-qa [7] https://admin.fedoraproject.org/mailman/listinfo/test signature.asc Description: OpenPGP digital signature ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce-- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 20, lots of virtuoso-t activity
Good day all, since updating to fedora 20, I got KDE version 4.11.2, theres lots of virtuoso-t activity, my mail checks every 2 minutes on 2 of my accounts and it seems that each time it checks mail, its re indexing the entire mail folder. and when I click on an unread mail in kmail, of it goes again, it uses 100% cpu for short while, then stops. While its doing this, kmail can become unresponsive for a few moments. I wonder if this is intentional behavior? or maybe something enabled temporarily until F20 final release? Should I have posted this in the KDE list I'm not sure. anyone else experiencing this? Martin signature.asc Description: This is a digitally signed message part. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F-20 Branched report: 20131014 changes
Compose started at Mon Oct 14 09:15:02 UTC 2013 Broken deps for armhfp -- [blueman] blueman-1.23-7.fc20.armv7hl requires obex-data-server >= 0:0.4.3 blueman-1.23-7.fc20.armv7hl requires gvfs-obexftp [bwm-ng] bwm-ng-0.6-11.1.fc20.armv7hl requires libstatgrab.so.9 [cloud-init] cloud-init-0.7.2-4.fc20.noarch requires dmidecode [cobbler] cobbler-2.4.0-2.fc20.noarch requires syslinux [condor-wallaby] condor-wallaby-client-5.0.3-4.fc20.noarch requires python-qmf >= 0:0.9.1073306 [fawkes] fawkes-plugin-player-0.5.0-12.fc20.armv7hl requires libgeos-3.3.8.so [fts] fts-server-3.1.1-1.fc20.armv7hl requires libactivemq-cpp.so.14 [glpi] glpi-0.84.2-1.fc20.noarch requires php-ZendFramework2-Version glpi-0.84.2-1.fc20.noarch requires php-ZendFramework2-Stdlib glpi-0.84.2-1.fc20.noarch requires php-ZendFramework2-ServiceManager glpi-0.84.2-1.fc20.noarch requires php-ZendFramework2-Loader glpi-0.84.2-1.fc20.noarch requires php-ZendFramework2-I18n glpi-0.84.2-1.fc20.noarch requires php-ZendFramework2-Cache-apc glpi-0.84.2-1.fc20.noarch requires php-ZendFramework2-Cache [gnome-do-plugins] gnome-do-plugins-thunderbird-0.8.4-14.fc20.armv7hl requires thunderbird [gofer] ruby-gofer-0.75-4.fc20.noarch requires rubygem(qpid) >= 0:0.16.0 [gradle] gradle-1.0-18.fc20.noarch requires plexus-container-default [grass] grass-6.4.3-2.fc20.armv7hl requires libgeos-3.3.8.so grass-libs-6.4.3-2.fc20.armv7hl requires libgeos-3.3.8.so [gtkd] gtkd-geany-tags-2.0.0-29.20120815git9ae9181.fc18.noarch requires gtkd = 0:2.0.0-29.20120815git9ae9181.fc18 [kawa] 1:kawa-1.11-5.fc19.armv7hl requires servlet25 [koji] koji-vm-1.8.0-2.fc20.noarch requires python-virtinst [kyua-cli] kyua-cli-0.5-3.fc19.armv7hl requires liblutok.so.0 kyua-cli-tests-0.5-3.fc19.armv7hl requires liblutok.so.0 [monotone] monotone-1.0-11.fc19.armv7hl requires libbotan-1.8.2.so perl-Monotone-1.0-11.fc19.armv7hl requires perl(:MODULE_COMPAT_5.16.2) [mozilla-firetray] mozilla-firetray-thunderbird-0.3.6-0.5.143svn.fc18.1.armv7hl requires thunderbird >= 0:11 [msp430-libc] msp430-libc-20120224-2.fc19.noarch requires msp430-gcc >= 0:4.6.3 [nifti2dicom] nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtksys.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkWidgets.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkVolumeRendering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkViews.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkTextAnalysis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkRendering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkParallel.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkInfovis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkImaging.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkIO.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkHybrid.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGraphics.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGeovis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGenericFiltering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkFiltering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkCommon.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkCharts.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libQVTK.so.5.10 [nocpulse-common] nocpulse-common-2.2.7-2.fc20.noarch requires perl(RHN::DBI) [openbox] gdm-control-3.5.2-2.fc20.armv7hl requires gnome-panel gnome-panel-control-3.5.2-2.fc20.armv7hl requires gnome-panel [openpts] openpts-0.2.6-7.fc20.armv7hl requires tboot [osm2pgsql] osm2pgsql-0.82.0-1.fc20.armv7hl requires libgeos-3.3.8.so [ovirt-engine] ovirt-engine-notification-service-3.1.0-1.fc19.noarch requires classpathx-mail [oyranos] oyranos-libs-0.4.0-7.fc19.armv7hl requires libraw.so.5 [perl-Language-Expr] perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) [perl-MIME-Lite-HTML] perl-MIME-Lite-HTML-1.24-4.fc18.noarch requires perl(:MODULE_COMPAT_5.16.0) [perl-MooseX-TrackDirty-Attributes] perl-MooseX-TrackDirty-Attributes-2.002-2.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) [perl-Padre] perl-Padre-0.90-6.fc18.noarch requires perl(:MODULE_COMPAT_5.16.0) [player] player-3.0.2-33.fc20.armv7hl requires libgeos-3.3.8.so [pure] pure-doc-0.57-4.fc20.noarch requires pure = 0:0.57-4.fc20 [python-basemap] python-basemap-1.0.6-4.fc20.armv7hl requires libgeos-3.3.8.so [python-tag] python-tag-2013.1-1.fc20.armv7hl requires libboost_python.so.1.5
[Test-Announce] 2013-10-14 @ 15:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2013-10-14 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! It's meeting time again! There's Beta stuff to discuss, of course, some follow ups from last week, and I also figured we could chat about Test Day result tracking. Any other agenda topics welcome! This is a reminder of the upcoming QA meeting. Please add any topic suggestions to the meeting wiki page: https://fedoraproject.org/wiki/QA/Meetings/20131014 The current proposed agenda is included below. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 20 Beta status 3. Test Day result tracking 4. Open floor -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin DOT net http://www.happyassassin.net ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F20: systemd-tmpfiles[215]: chmod(/var/log/journal) failed: Permission denied
On 10/14/2013 11:50 AM, Mateusz Marzantowicz wrote: > On 14.10.2013 10:43, Olav Vitters wrote: >> On Fri, Oct 11, 2013 at 09:57:20PM +0200, Mateusz Marzantowicz wrote: >>> systemd-tmpfiles[215]: chmod(/var/log/journal) failed: Permission denied >>> >>> Is it known bug or should I report it? I can't find any similar bug >>> report in bugzilla. >> >> Please file a bugreport. Even if it ends up being a duplicate, you >> searched so that's good enough. Can even mention that you searched for >> duplicates when you file the bug. It can be pretty difficult to find >> duplicates and better a duplicate than to miss a bug. >> > > Thanks for advice. I'll try to gather more data and then file some > usefull report. > > > > Mateusz Marzantowicz > Possibly already reported: https://bugzilla.redhat.com/show_bug.cgi?id=987242 Joachim Backes -- Fedora release 19 (Schrödinger’s Cat) Kernel-3.11.4-201.fc19.x86_64 Joachim Backes https://www-user.rhrk.uni-kl.de/~backes -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F20: systemd-tmpfiles[215]: chmod(/var/log/journal) failed: Permission denied
On 14.10.2013 10:43, Olav Vitters wrote: > On Fri, Oct 11, 2013 at 09:57:20PM +0200, Mateusz Marzantowicz wrote: >> systemd-tmpfiles[215]: chmod(/var/log/journal) failed: Permission denied >> >> Is it known bug or should I report it? I can't find any similar bug >> report in bugzilla. > > Please file a bugreport. Even if it ends up being a duplicate, you > searched so that's good enough. Can even mention that you searched for > duplicates when you file the bug. It can be pretty difficult to find > duplicates and better a duplicate than to miss a bug. > Thanks for advice. I'll try to gather more data and then file some usefull report. Mateusz Marzantowicz -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F20: systemd-tmpfiles[215]: chmod(/var/log/journal) failed: Permission denied
On Fri, Oct 11, 2013 at 09:57:20PM +0200, Mateusz Marzantowicz wrote: > systemd-tmpfiles[215]: chmod(/var/log/journal) failed: Permission denied > > Is it known bug or should I report it? I can't find any similar bug > report in bugzilla. Please file a bugreport. Even if it ends up being a duplicate, you searched so that's good enough. Can even mention that you searched for duplicates when you file the bug. It can be pretty difficult to find duplicates and better a duplicate than to miss a bug. -- Regards, Olav -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Let's stop using wiki for test results
Hi Rolf! I was not around teh internetz over the weekend, but I took the liberty of creating the page for your testday just now. I also put the the results already tracked in the wiki into the app, and added a reference to the tool to the wiki testday. Regards, Joza - Original Message - > From: "Rolf Fokkens" > To: "For testing and quality assurance of Fedora releases" > > Sent: Saturday, October 12, 2013 3:56:31 PM > Subject: Re: Let's stop using wiki for test results > > Hi, > > Tomorrow (sunday) there's an SSD cache Test day. I do like not using the > wiki for testresults, but is this tool online available to be used for > tomorrow's test day? > > Rolf > > > On 10/11/2013 06:53 PM, "Jóhann B. Guðmundsson" wrote: > > On 10/11/2013 04:47 PM, Adam Williamson wrote: > >> Well, 'we' didn't, really. Josef just thought it would be a useful thing > >> to have, so he wrote it, and someone running a test day wound up using > >> it. There was no strategic meeting or grand conspiracy or plan or > >> something. This is how stuff happens in tech, usually: stuff gets done > >> because people just...do it. > > > > Not really but OK > > > >> Now we have seen test days where we used > >> the wiki to track results and test days where we used josef's little > >> tool to track results, and people seem to like the tool, so maybe now > >> we'll make it more clear to people running test days that they have the > >> option of using the tool to track the results. That's really the sum > >> total of what's going on. > > > > Anything beats the wiki really so if it's in ready enough shape we > > should just move to that one instead. > > > > JBG > > -- > test mailing list > test@lists.fedoraproject.org > To unsubscribe: > https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 18 updates-testing report
The following Fedora 18 Security updates need testing: Age URL 177 https://admin.fedoraproject.org/updates/FEDORA-2013-6117/eucalyptus-3.2.2-1.fc18 25 https://admin.fedoraproject.org/updates/FEDORA-2013-17112/hplip-3.13.9-2.fc18 23 https://admin.fedoraproject.org/updates/FEDORA-2013-17195/spice-gtk-0.18-3.fc18 20 https://admin.fedoraproject.org/updates/FEDORA-2013-17431/thunderbird-17.0.9-1.fc18 18 https://admin.fedoraproject.org/updates/FEDORA-2013-17635/wireshark-1.10.2-4.fc18 16 https://admin.fedoraproject.org/updates/FEDORA-2013-17853/davfs2-1.4.7-3.fc18 15 https://admin.fedoraproject.org/updates/FEDORA-2013-17912/chicken-4.8.0.4-4.fc18 15 https://admin.fedoraproject.org/updates/FEDORA-2013-17904/fedmsg-0.7.1-2.fc18 8 https://admin.fedoraproject.org/updates/FEDORA-2013-18401/fping-3.5-3.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18606/dropbear-2013.59-1.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18647/gnupg-1.4.15-1.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18686/mod_fcgid-2.3.9-1.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-18802/phpMyAdmin-3.5.8.2-1.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-18785/libtar-1.2.11-25.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-18822/kernel-3.11.4-101.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-18774/icu-49.1.1-12.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-18814/gnupg2-2.0.22-1.fc18,libgpg-error-1.11-1.fc18 2 https://admin.fedoraproject.org/updates/FEDORA-2013-18911/ReviewBoard-1.7.15-1.fc18,python-djblets-0.7.20-1.fc18 0 https://admin.fedoraproject.org/updates/FEDORA-2013-19053/xen-4.2.3-4.fc18 The following Fedora 18 Critical Path updates have yet to be approved: Age URL 246 https://admin.fedoraproject.org/updates/FEDORA-2013-2192/nautilus-3.6.3-5.fc18 12 https://admin.fedoraproject.org/updates/FEDORA-2013-18050/gdb-7.5.1-43.fc18 11 https://admin.fedoraproject.org/updates/FEDORA-2013-18164/perl-threads-1.89-1.fc18 10 https://admin.fedoraproject.org/updates/FEDORA-2013-18276/dnsmasq-2.65-8.fc18 8 https://admin.fedoraproject.org/updates/FEDORA-2013-18402/keyutils-1.5.8-1.fc18 8 https://admin.fedoraproject.org/updates/FEDORA-2013-18380/ibus-1.5.4-2.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18607/libxklavier-5.4-1.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18622/selinux-policy-3.11.1-106.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18590/usbmuxd-1.0.8-9.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18680/akonadi-1.10.3-1.fc18,qt-4.8.5-10.fc18 4 https://admin.fedoraproject.org/updates/FEDORA-2013-18383/thunderbird-enigmail-1.6-1.fc18,thunderbird-24.0-3.fc18,thunderbird-lightning-2.6-1.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-18814/gnupg2-2.0.22-1.fc18,libgpg-error-1.11-1.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-18774/icu-49.1.1-12.fc18 3 https://admin.fedoraproject.org/updates/FEDORA-2013-18815/sane-backends-1.0.24-1.fc18 0 https://admin.fedoraproject.org/updates/FEDORA-2013-19021/taglib-1.9.1-1.fc18 0 https://admin.fedoraproject.org/updates/FEDORA-2013-19026/python-markupsafe-0.18-1.fc18 The following builds have been pushed to Fedora 18 updates-testing alexandria-0.6.9-7.fc18 anki-2.0.13-1.fc18 cnucnu-0-0.15.20131007git606929ec.fc18 drbdlinks-1.25-1.fc18 kmymoney-4.6.4-1.fc18 mate-document-viewer-1.6.1-6.fc18 mate-file-archiver-1.6.1-0.1.git95ebd69.fc18 mate-power-manager-1.6.3-0.1.gitbc54d96.fc18 mate-screensaver-1.6.1-3.fc18 numatop-1.0.1-5.fc18 perl-Math-NumSeq-65-1.fc18 php-bartlett-PHP-Reflect-1.9.0-1.fc18 php-xcache-3.0.4-1.fc18 python-formencode-1.2.6-1.fc18 python-markupsafe-0.18-1.fc18 qlandkartegt-1.7.5-1.fc18 qpdfview-0.4.6-1.fc18 qtdbf-1.0.0-1.fc18 rubygem-domain_name-0.5.13-2.fc18 taglib-1.9.1-1.fc18 tlock-1.5-8.fc18 xen-4.2.3-4.fc18 xfce4-whiskermenu-plugin-1.1.1-1.fc18 youtube-dl-2013.10.09-1.fc18 Details about builds: alexandria-0.6.9-7.fc18 (FEDORA-2013-19049) Book collection manager Update Information: In some cases cursor position was recorded as negative value, which caused alexandria not launching any more. This new rpm will fix this issue. ChangeLog: * Mon Oct 7 2013 Mamoru TASAKA - 0.6.9-7 - Read negative value as integer in case position has such value (bug 1014295) References: [ 1 ] Bug #1014295 - alexandria won't launch when position has n
