Re: 'dnf system-upgrade reboot' doesn't do anything
> Following the instructions on
> https://fedoraproject.org/wiki/DNF_system_upgrade
> eventually I reached
> dnf system-upgrade download --refresh --releasever=25
> which apparently completed without error, ending by directing to run
> dnf system-upgrade reboot.
> So, I did, and it booted normally. Nothing is running that isn't supposed to
> be running in a normal boot.
> dnf system-upgrade log
> reports no logs found. The only dnf string in journalctl -b is starting the
> makecache timer. This is not the first time I've tried those wiki page
> instructions exactly like this with same result. What's supposed to be
> happening that isn't?
It's supposed to boot into an offline updates mode, and do the upgrade. Please
file a bug and attach logs ("journalctl -b -1" after you boot into standard
desktop instead of offline updates mode). Thanks.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
[Test-Announce] Announcing the release of Fedora 25 Alpha!
The Fedora Project is pleased to announce the immediate availability of the Fedora 25 Alpha, an important milestone on the road to our Fedora 25 release in November. Download the prerelease from our Get Fedora site: * https://getfedora.org/en/workstation/prerelease/ * https://getfedora.org/en/server/prerelease/ * https://getfedora.org/en/cloud/prerelease/ Or, check out one of our popular variants: * https://spins.fedoraproject.org/prerelease * https://labs.fedoraproject.org/prerelease * https://arm.fedoraproject.org/prerelease == Alternative Architectures == We are also simultaneously releasing the F25 Alpha for Power64 and 64-bit ARM (AArch64). These are available from: https://download.fedoraproject.org/pub/fedora-secondary/releases/test/ 25_Alpha/ == What is the Alpha release? == The Alpha release contains all the features of Fedora 25's editions in a form that anyone can help test. This testing, guided by the Fedora QA team, helps us target and identify bugs. When these bugs are fixed, we make a Beta release available. A Beta release is code-complete and bears a very strong resemblance to the third and final release. The final release of Fedora 25 is expected in November. If you take the time to download and try out the Alpha, you can check and make sure the things that are important to YOU are working. Every bug you find and report doesn't just help you, it improves the experience of millions of Fedora users worldwide! Together, we can make Fedora rock-solid. We have a culture of coordinating new features and pushing fixes upstream as much as we can, and your feedback improves not only Fedora, but Linux and Free software as a whole. * https://fedoraproject.org/wiki/Releases/25/Schedule == Issues and Details == Since this is an alpha release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the mailing list or in #fedora-qa on Freenode. As testing progresses, common issues are tracked on the Common F25 Bugs page. * https://fedoraproject.org/wiki/Common_F25_bugs For tips on reporting a bug effectively, read "how to file a bug report". * https://fedoraproject.org/wiki/How_to_file_a_bug_report == Release Schedule == The full release schedule is available on the Fedora wiki: * https://fedoraproject.org/wiki/Releases/25/Schedule The current schedule calls for a beta release towards the middle of October, and the final release in November. Be aware that these dates are development targets. Some projects release on a set date regardless of feature completeness or bugs; others wait until certain thresholds for functionality or testing are met. Fedora uses a hybrid model, with milestones subject to adjustment. This allows us to make releases with new features and newly- integrated and updated upstream software while also retaining high quality. Enjoy Fedora Release Engineering (Dennis, Peter, Kevin, Mohan, Adam, Randy) signature.asc Description: This is a digitally signed message part. ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/test-annou...@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Announcing the release of Fedora 25 Alpha!
Hi, as desribed in thread: Re: [Test-Announce] Fedora 25 Candidate Alpha-1.2 Available Now! No boot with USB flash medium possible --> dracut I will collect a log and file a bug. Kind regards -Ursprüngliche Mitteilung- Von: Dennis Gilmore An: test-announce Cc: announce ; devel-announce Verschickt: Di, 30 Aug 2016 4:15 pm Betreff: Announcing the release of Fedora 25 Alpha! The Fedora Project is pleased to announce the immediate availability of the Fedora 25 Alpha, an important milestone on the road to our Fedora 25 release in November. Download the prerelease from our Get Fedora site: * https://getfedora.org/en/workstation/prerelease/ * https://getfedora.org/en/server/prerelease/ * https://getfedora.org/en/cloud/prerelease/ Or, check out one of our popular variants: * https://spins.fedoraproject.org/prerelease * https://labs.fedoraproject.org/prerelease * https://arm.fedoraproject.org/prerelease == Alternative Architectures == We are also simultaneously releasing the F25 Alpha for Power64 and 64-bit ARM (AArch64). These are available from: https://download.fedoraproject.org/pub/fedora-secondary/releases/test/ 25_Alpha/ == What is the Alpha release? == The Alpha release contains all the features of Fedora 25's editions in a form that anyone can help test. This testing, guided by the Fedora QA team, helps us target and identify bugs. When these bugs are fixed, we make a Beta release available. A Beta release is code-complete and bears a very strong resemblance to the third and final release. The final release of Fedora 25 is expected in November. If you take the time to download and try out the Alpha, you can check and make sure the things that are important to YOU are working. Every bug you find and report doesn't just help you, it improves the experience of millions of Fedora users worldwide! Together, we can make Fedora rock-solid. We have a culture of coordinating new features and pushing fixes upstream as much as we can, and your feedback improves not only Fedora, but Linux and Free software as a whole. * https://fedoraproject.org/wiki/Releases/25/Schedule == Issues and Details == Since this is an alpha release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the mailing list or in #fedora-qa on Freenode. As testing progresses, common issues are tracked on the Common F25 Bugs page. * https://fedoraproject.org/wiki/Common_F25_bugs For tips on reporting a bug effectively, read "how to file a bug report". * https://fedoraproject.org/wiki/How_to_file_a_bug_report == Release Schedule == The full release schedule is available on the Fedora wiki: * https://fedoraproject.org/wiki/Releases/25/Schedule The current schedule calls for a beta release towards the middle of October, and the final release in November. Be aware that these dates are development targets. Some projects release on a set date regardless of feature completeness or bugs; others wait until certain thresholds for functionality or testing are met. Fedora uses a hybrid model, with milestones subject to adjustment. This allows us to make releases with new features and newly- integrated and updated upstream software while also retaining high quality. Enjoy Fedora Release Engineering (Dennis, Peter, Kevin, Mohan, Adam, Randy)--announce mailing listannounce@lists.fedoraproject.orghttps://lists.fedoraproject.org/admin/lists/annou...@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Problems updating to F25 (usdisk2.service restarting regularly and kde file dialogs slow)
Hi,
I have initially reported this problem to fedora kde list but I am
bringing the issue here since it seems to be more general.
I have updated my laptop to F25 using the dnf plugin,
the process was smooth and uneventful. I have initially installed kde-live
from F24 beta and I have been upgrading it since.
All seems to work with some small exceptions that I am reporting here:
Plasma (kde) is slow to show up, as is sddm and any file dialog. If I use e.g.
LyX and open a file using the menu, File->Open, I will wait several minutes
before the dialog shows and as soon as it shows the program will work
normally. This is consistent
Reading the journal I see initially:
Unable to fix SELinux security context of /dev/shm/lldpad.state: Permission
denied
Unable to fix SELinux security context of /run/systemd/inaccessible/fifo:
Permission denied
Unable to fix SELinux security context of /run/systemd/inaccessible/blk:
Permission denied
Unable to fix SELinux security context of /run/systemd/inaccessible/chr:
Permission denied
and later
systemd[1]: Starting Disk Manager...
audit[1193]: AVC avc: denied { read } for pid=1193 comm="udisksd"
name="sr0" dev="devtmpfs"...
udisksd[1193]: Error probing device: Error opening device file /dev/sr0:
Permission denied (udisks-error-quark, 0)
(4 more lines)
udisksd[1193]: udisks daemon version 2.6.2 exiting
systemd[1]: Started Disk Manager
...
so udisk2.service is restarted lots of times.
Rebooting with selinux=0 in grub fixes all this issues.
Where (to what component) should I report this?
--
José Abílio
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Problems updating to F25 (usdisk2.service restarting regularly and kde file dialogs slow)
On Tue, 2016-08-30 at 18:30 +0100, José Abílio Matos wrote:
> Hi,
> I have initially reported this problem to fedora kde list but I am
> bringing the issue here since it seems to be more general.
>
> I have updated my laptop to F25 using the dnf plugin,
> the process was smooth and uneventful. I have initially installed kde-live
> from F24 beta and I have been upgrading it since.
>
> All seems to work with some small exceptions that I am reporting here:
>
> Plasma (kde) is slow to show up, as is sddm and any file dialog. If I use
> e.g.
> LyX and open a file using the menu, File->Open, I will wait several minutes
> before the dialog shows and as soon as it shows the program will work
> normally. This is consistent
>
>
> Reading the journal I see initially:
>
> Unable to fix SELinux security context of /dev/shm/lldpad.state: Permission
> denied
> Unable to fix SELinux security context of /run/systemd/inaccessible/fifo:
> Permission denied
> Unable to fix SELinux security context of /run/systemd/inaccessible/blk:
> Permission denied
> Unable to fix SELinux security context of /run/systemd/inaccessible/chr:
> Permission denied
We already have reports for all of these, IIRC.
> and later
> systemd[1]: Starting Disk Manager...
> audit[1193]: AVC avc: denied { read } for pid=1193 comm="udisksd"
> name="sr0" dev="devtmpfs"...
> udisksd[1193]: Error probing device: Error opening device file /dev/sr0:
> Permission denied (udisks-error-quark, 0)
> (4 more lines)
> udisksd[1193]: udisks daemon version 2.6.2 exiting
> systemd[1]: Started Disk Manager
> ...
>
> so udisk2.service is restarted lots of times.
>
> Rebooting with selinux=0 in grub fixes all this issues.
>
> Where (to what component) should I report this?
selinux-policy , but there's actually a procedure for reporting SELinux
denials. You should be able to find an app called 'SELinux
Troubleshooter' in the system menus. Run that, and it should show the
denial(s) there. For each denial you can click 'Troubleshoot' and then
'Report Bug', and it should help you to file a bug report which will
include all the necessary information - and if there's already a
report, it'll direct you to that bug instead of filing a duplicate.
Thanks!
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Announcing the release of Fedora 25 Alpha!
Hi, filed bug: https://bugzilla.redhat.com//show_bug.cgi?id=1371661 wanted to add rdsosreport.txt, but is 1,9MB in size, this will not work, sorry Kind regards -Ursprüngliche Mitteilung- Von: Joerg Lechner An: users ; test ; awilliam Verschickt: Di, 30 Aug 2016 5:42 pm Betreff: Re: Announcing the release of Fedora 25 Alpha! Hi, as desribed in thread: Re: [Test-Announce] Fedora 25 Candidate Alpha-1.2 Available Now! No boot with USB flash medium possible --> dracut I will collect a log and file a bug. Kind regards -Ursprüngliche Mitteilung- Von: Dennis Gilmore An: test-announce Cc: announce ; devel-announce Verschickt: Di, 30 Aug 2016 4:15 pm Betreff: Announcing the release of Fedora 25 Alpha! The Fedora Project is pleased to announce the immediate availability of the Fedora 25 Alpha, an important milestone on the road to our Fedora 25 release in November. Download the prerelease from our Get Fedora site: * https://getfedora.org/en/workstation/prerelease/ * https://getfedora.org/en/server/prerelease/ * https://getfedora.org/en/cloud/prerelease/ Or, check out one of our popular variants: * https://spins.fedoraproject.org/prerelease * https://labs.fedoraproject.org/prerelease * https://arm.fedoraproject.org/prerelease == Alternative Architectures == We are also simultaneously releasing the F25 Alpha for Power64 and 64-bit ARM (AArch64). These are available from: https://download.fedoraproject.org/pub/fedora-secondary/releases/test/ 25_Alpha/ == What is the Alpha release? == The Alpha release contains all the features of Fedora 25's editions in a form that anyone can help test. This testing, guided by the Fedora QA team, helps us target and identify bugs. When these bugs are fixed, we make a Beta release available. A Beta release is code-complete and bears a very strong resemblance to the third and final release. The final release of Fedora 25 is expected in November. If you take the time to download and try out the Alpha, you can check and make sure the things that are important to YOU are working. Every bug you find and report doesn't just help you, it improves the experience of millions of Fedora users worldwide! Together, we can make Fedora rock-solid. We have a culture of coordinating new features and pushing fixes upstream as much as we can, and your feedback improves not only Fedora, but Linux and Free software as a whole. * https://fedoraproject.org/wiki/Releases/25/Schedule == Issues and Details == Since this is an alpha release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the mailing list or in #fedora-qa on Freenode. As testing progresses, common issues are tracked on the Common F25 Bugs page. * https://fedoraproject.org/wiki/Common_F25_bugs For tips on reporting a bug effectively, read "how to file a bug report". * https://fedoraproject.org/wiki/How_to_file_a_bug_report == Release Schedule == The full release schedule is available on the Fedora wiki: * https://fedoraproject.org/wiki/Releases/25/Schedule The current schedule calls for a beta release towards the middle of October, and the final release in November. Be aware that these dates are development targets. Some projects release on a set date regardless of feature completeness or bugs; others wait until certain thresholds for functionality or testing are met. Fedora uses a hybrid model, with milestones subject to adjustment. This allows us to make releases with new features and newly- integrated and updated upstream software while also retaining high quality. Enjoy Fedora Release Engineering (Dennis, Peter, Kevin, Mohan, Adam, Randy)--announce mailing listannounce@lists.fedoraproject.orghttps://lists.fedoraproject.org/admin/lists/annou...@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Announcing the release of Fedora 25 Alpha!
On Tue, 2016-08-30 at 14:21 -0400, Joerg Lechner wrote: > Hi, > filed bug: > https://bugzilla.redhat.com//show_bug.cgi?id=1371661 > wanted to add rdsosreport.txt, but is 1,9MB in size, this will not work, sorry > Kind regards Sure it should. BZ accepts attachments bigger than that. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Problems updating to F25 (usdisk2.service restarting regularly and kde file dialogs slow)
On Tue, Aug 30, 2016 at 11:30 AM, José Abílio Matos wrote:
> Hi,
> I have initially reported this problem to fedora kde list but I am
> bringing the issue here since it seems to be more general.
>
> I have updated my laptop to F25 using the dnf plugin,
> the process was smooth and uneventful. I have initially installed kde-live
> from F24 beta and I have been upgrading it since.
>
> All seems to work with some small exceptions that I am reporting here:
>
> Plasma (kde) is slow to show up, as is sddm and any file dialog. If I use e.g.
> LyX and open a file using the menu, File->Open, I will wait several minutes
> before the dialog shows and as soon as it shows the program will work
> normally. This is consistent
>
>
> Reading the journal I see initially:
>
> Unable to fix SELinux security context of /dev/shm/lldpad.state: Permission
> denied
> Unable to fix SELinux security context of /run/systemd/inaccessible/fifo:
> Permission denied
> Unable to fix SELinux security context of /run/systemd/inaccessible/blk:
> Permission denied
> Unable to fix SELinux security context of /run/systemd/inaccessible/chr:
> Permission denied
>
> and later
> systemd[1]: Starting Disk Manager...
> audit[1193]: AVC avc: denied { read } for pid=1193 comm="udisksd"
> name="sr0" dev="devtmpfs"...
> udisksd[1193]: Error probing device: Error opening device file /dev/sr0:
> Permission denied (udisks-error-quark, 0)
> (4 more lines)
> udisksd[1193]: udisks daemon version 2.6.2 exiting
> systemd[1]: Started Disk Manager
> ...
>
> so udisk2.service is restarted lots of times.
>
> Rebooting with selinux=0 in grub fixes all this issues.
You should use enforcing=0 instead. selinux=0 disables selinux
entirely, will force a relabel next time it's enabled, and means the
unenforced denials aren't reported. So it makes it harder to
troubleshoot.
--
Chris Murphy
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Fedora 25-20160830.n.0 compose check report
Missing expected images: Cloud_base raw-xz i386 Atomic raw-xz x86_64 Failed openQA tests: 16/89 (x86_64), 5/17 (i386) ID: 31297 Test: x86_64 Workstation-live-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/31297 ID: 31298 Test: x86_64 Workstation-live-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/31298 ID: 31304 Test: x86_64 Workstation-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/31304 ID: 31305 Test: x86_64 Workstation-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/31305 ID: 31306 Test: i386 Workstation-live-iso install_default URL: https://openqa.fedoraproject.org/tests/31306 ID: 31307 Test: i386 Workstation-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/31307 ID: 31308 Test: x86_64 Atomic-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/31308 ID: 31309 Test: x86_64 KDE-live-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/31309 ID: 31310 Test: x86_64 KDE-live-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/31310 ID: 31316 Test: i386 KDE-live-iso install_default URL: https://openqa.fedoraproject.org/tests/31316 ID: 31333 Test: x86_64 Server-dvd-iso realmd_join_cockpit URL: https://openqa.fedoraproject.org/tests/31333 ID: 31341 Test: x86_64 universal install_repository_http_graphical URL: https://openqa.fedoraproject.org/tests/31341 ID: 31360 Test: x86_64 universal install_iscsi URL: https://openqa.fedoraproject.org/tests/31360 ID: 31374 Test: x86_64 universal upgrade_desktop_64bit URL: https://openqa.fedoraproject.org/tests/31374 ID: 31377 Test: x86_64 universal upgrade_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/31377 ID: 31379 Test: x86_64 universal upgrade_2_desktop_64bit URL: https://openqa.fedoraproject.org/tests/31379 ID: 31380 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/31380 ID: 31381 Test: x86_64 universal upgrade_2_kde_64bit URL: https://openqa.fedoraproject.org/tests/31381 ID: 31382 Test: x86_64 universal upgrade_2_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/31382 ID: 31394 Test: i386 universal upgrade_desktop_32bit URL: https://openqa.fedoraproject.org/tests/31394 ID: 31395 Test: i386 universal upgrade_2_desktop_32bit URL: https://openqa.fedoraproject.org/tests/31395 Passed openQA tests: 63/89 (x86_64), 12/17 (i386), 2/2 (arm) Skipped openQA tests: 10 of 108 -- Mail generated by check-compose: https://git.fedorahosted.org/cgit/fedora-qa.git/tree/check-compose -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Fedora Rawhide-20160830.n.0 compose check report
Missing expected images: Cloud_base raw-xz i386 Atomic raw-xz x86_64 Failed openQA tests: 33/89 (x86_64), 6/17 (i386), 1/2 (arm) ID: 31187 Test: x86_64 Everything-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/31187 ID: 31189 Test: x86_64 Workstation-live-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/31189 ID: 31190 Test: x86_64 Workstation-live-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/31190 ID: 31196 Test: x86_64 Workstation-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/31196 ID: 31197 Test: x86_64 Workstation-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/31197 ID: 31198 Test: i386 Workstation-live-iso install_default URL: https://openqa.fedoraproject.org/tests/31198 ID: 31199 Test: i386 Workstation-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/31199 ID: 31200 Test: x86_64 Atomic-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/31200 ID: 31201 Test: x86_64 KDE-live-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/31201 ID: 31202 Test: x86_64 KDE-live-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/31202 ID: 31208 Test: i386 KDE-live-iso install_default URL: https://openqa.fedoraproject.org/tests/31208 ID: 31209 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/31209 ID: 31212 Test: x86_64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/31212 ID: 31214 Test: x86_64 Server-dvd-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/31214 ID: 31220 Test: x86_64 Server-dvd-iso install_repository_nfs_graphical URL: https://openqa.fedoraproject.org/tests/31220 ID: 31221 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller URL: https://openqa.fedoraproject.org/tests/31221 ID: 31223 Test: x86_64 Server-dvd-iso server_cockpit_default URL: https://openqa.fedoraproject.org/tests/31223 ID: 31236 Test: x86_64 universal install_delete_pata@uefi URL: https://openqa.fedoraproject.org/tests/31236 ID: 31240 Test: x86_64 universal install_multi@uefi URL: https://openqa.fedoraproject.org/tests/31240 ID: 31252 Test: x86_64 universal install_iscsi URL: https://openqa.fedoraproject.org/tests/31252 ID: 31253 Test: x86_64 universal install_package_set_kde URL: https://openqa.fedoraproject.org/tests/31253 ID: 31254 Test: x86_64 universal install_simple_encrypted@uefi URL: https://openqa.fedoraproject.org/tests/31254 ID: 31255 Test: x86_64 universal install_simple_free_space@uefi URL: https://openqa.fedoraproject.org/tests/31255 ID: 31256 Test: x86_64 universal install_multi_empty@uefi URL: https://openqa.fedoraproject.org/tests/31256 ID: 31257 Test: x86_64 universal install_software_raid@uefi URL: https://openqa.fedoraproject.org/tests/31257 ID: 31258 Test: x86_64 universal install_delete_partial@uefi URL: https://openqa.fedoraproject.org/tests/31258 ID: 31259 Test: x86_64 universal install_btrfs@uefi URL: https://openqa.fedoraproject.org/tests/31259 ID: 31260 Test: x86_64 universal install_ext3@uefi URL: https://openqa.fedoraproject.org/tests/31260 ID: 31261 Test: x86_64 universal install_xfs@uefi URL: https://openqa.fedoraproject.org/tests/31261 ID: 31262 Test: x86_64 universal install_lvmthin@uefi URL: https://openqa.fedoraproject.org/tests/31262 ID: 31263 Test: x86_64 universal install_no_swap@uefi URL: https://openqa.fedoraproject.org/tests/31263 ID: 31266 Test: x86_64 universal upgrade_desktop_64bit URL: https://openqa.fedoraproject.org/tests/31266 ID: 31269 Test: x86_64 universal upgrade_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/31269 ID: 31271 Test: x86_64 universal upgrade_2_desktop_64bit URL: https://openqa.fedoraproject.org/tests/31271 ID: 31272 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/31272 ID: 31273 Test: x86_64 universal upgrade_2_kde_64bit URL: https://openqa.fedoraproject.org/tests/31273 ID: 31274 Test: x86_64 universal upgrade_2_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/31274 ID: 31286 Test: i386 universal upgrade_desktop_32bit URL: https://openqa.fedoraproject.org/tests/31286 ID: 31287 Test: i386 universal upgrade_2_desktop_32bit URL: https://openqa.fedoraproject.org/tests/31287 ID: 31288 Test: i386 universal install_package_set_kde URL: https://openqa.fedoraproject.org/tests/31288 Passed openQA tests: 42/89 (x86_64), 11/17 (i386) Skipped openQA tests: 13 of 108 -- Mail generated by check-compose: https://git.fedorahosted.org/cgit/fedora-qa.git/tree/check-compose -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists
Re: Fedora Rawhide-20160830.n.0 compose check report
On Tue, 2016-08-30 at 19:38 +, Fedora compose checker wrote: > Missing expected images: > > Cloud_base raw-xz i386 > Atomic raw-xz x86_64 > > Failed openQA tests: 33/89 (x86_64), 6/17 (i386), 1/2 (arm) So today we got a new anaconda which breaks when booted in UEFI: https://bugzilla.redhat.com/show_bug.cgi?id=1371653 and the 'Welcome' app on Workstation live seems to be crashing: https://bugzilla.redhat.com/show_bug.cgi?id=1371681 also, SDDM redesigned its damn self again so the KDE tests fail on the login screen; I'll fix that needle. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: 'dnf system-upgrade reboot' doesn't do anything
Kamil Paral composed on 2016-08-30 06:24 (UTC-0400):
>> Following the instructions on
>> https://fedoraproject.org/wiki/DNF_system_upgrade
>> eventually I reached
>> dnf system-upgrade download --refresh --releasever=25
>> which apparently completed without error, ending by directing to run
>> dnf system-upgrade reboot.
>> So, I did, and it booted normally. Nothing is running that isn't supposed to
>> be running in a normal boot.
>> dnf system-upgrade log
>> reports no logs found. The only dnf string in journalctl -b is starting the
>> makecache timer. This is not the first time I've tried those wiki page
>> instructions exactly like this with same result. What's supposed to be
>> happening that isn't?
> It's supposed to boot into an offline updates mode, and do the upgrade.
> Please file a bug and attach logs ("journalctl -b -1" after you boot into
> standard desktop instead of offline updates mode). Thanks.
What I was looking for is the process that triggers "offline updates mode".
If it involves the bootloader, I know whatever it may be simply doesn't
exist. This is a multiboot installation, so no Fedora bootloader is involved
in its boot process. If not bootloader related, I'll go ahead and file a bug,
or even if it is, but you indicate you want one anyway.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: 'dnf system-upgrade reboot' doesn't do anything
On Tue, Aug 30, 2016 at 3:19 PM, Felix Miata wrote:
> Kamil Paral composed on 2016-08-30 06:24 (UTC-0400):
>
>>> Following the instructions on
>>> https://fedoraproject.org/wiki/DNF_system_upgrade
>>> eventually I reached
>>> dnf system-upgrade download --refresh --releasever=25
>>> which apparently completed without error, ending by directing to run
>>> dnf system-upgrade reboot.
>>> So, I did, and it booted normally. Nothing is running that isn't supposed to
>>> be running in a normal boot.
>>> dnf system-upgrade log
>>> reports no logs found. The only dnf string in journalctl -b is starting the
>>> makecache timer. This is not the first time I've tried those wiki page
>>> instructions exactly like this with same result. What's supposed to be
>>> happening that isn't?
>
>> It's supposed to boot into an offline updates mode, and do the upgrade.
>> Please file a bug and attach logs ("journalctl -b -1" after you boot into
>> standard desktop instead of offline updates mode). Thanks.
>
> What I was looking for is the process that triggers "offline updates mode".
> If it involves the bootloader, I know whatever it may be simply doesn't
> exist. This is a multiboot installation, so no Fedora bootloader is involved
> in its boot process. If not bootloader related, I'll go ahead and file a bug,
> or even if it is, but you indicate you want one anyway.
https://www.freedesktop.org/software/systemd/man/systemd.offline-updates.html
What triggers it is the creation of /system-update symlink and a
reboot. Then systemd picks that up and for that boot considers
system-update.target the default target.
--
Chris Murphy
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Problems updating to F25 (usdisk2.service restarting regularly and kde file dialogs slow)
On Tuesday, August 30, 2016 1:00:45 PM WEST Chris Murphy wrote: > You should use enforcing=0 instead. selinux=0 disables selinux > entirely, will force a relabel next time it's enabled, and means the > unenforced denials aren't reported. So it makes it harder to > troubleshoot. Thanks for the remainder Chris, it has been sometime since I had to deal with these issues that I forgot all the fine details and mixed the calls. :-) One of the niceties of your remark is that now Dan (Walsh) will not hate me. ;-) -- José Abílio -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: 'dnf system-upgrade reboot' doesn't do anything
Chris Murphy composed on 2016-08-30 15:31 (UTC-0600): Felix Miata wrote: What I was looking for is the process that triggers "offline updates mode". If it involves the bootloader, I know whatever it may be simply doesn't exist. This is a multiboot installation, so no Fedora bootloader is involved in its boot process. If not bootloader related, I'll go ahead and file a bug, or even if it is, but you indicate you want one anyway. https://www.freedesktop.org/software/systemd/man/systemd.offline-updates.html What triggers it is the creation of /system-update symlink and a reboot. Then systemd picks that up and for that boot considers system-update.target the default target. So apparently the kernel cmdline can be involved, and the only bug appears to be that the wiki page has no boot stanza admonition that the cmdline must not include anything to avoid booting to the temporary default target (in this case "3", which is a parameter I include on most of my kernel cmdlines). Last line on vtty1 ATM is "[OK] Reached target System Update". There's no way apparent to ensure anything is actually happening at this point, no login prompts or anything else on other vttys. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Problems updating to F25 (usdisk2.service restarting regularly and kde file dialogs slow)
On Tuesday, August 30, 2016 10:36:33 AM WEST Adam Williamson wrote: > selinux-policy , but there's actually a procedure for reporting SELinux > denials. You should be able to find an app called 'SELinux > Troubleshooter' in the system menus. Run that, and it should show the > denial(s) there. For each denial you can click 'Troubleshoot' and then > 'Report Bug', and it should help you to file a bug report which will > include all the necessary information - and if there's already a > report, it'll direct you to that bug instead of filing a duplicate. > > Thanks! Thank you Adam. Known were https://bugzilla.redhat.com/show_bug.cgi?id=1370459 https://bugzilla.redhat.com/show_bug.cgi?id=1367280 https://bugzilla.redhat.com/show_bug.cgi?id=1370292 and a new one to the party SELinux is preventing udisksd from 'ioctl' accesses on the blk_file /dev/sr0. https://bugzilla.redhat.com/show_bug.cgi?id=1371687 -- José Abílio -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: 'dnf system-upgrade reboot' doesn't do anything
On Tue, Aug 30, 2016 at 4:08 PM, Felix Miata wrote: > Chris Murphy composed on 2016-08-30 15:31 (UTC-0600): > >> Felix Miata wrote: > > >>> What I was looking for is the process that triggers "offline updates >>> mode". >>> If it involves the bootloader, I know whatever it may be simply doesn't >>> exist. This is a multiboot installation, so no Fedora bootloader is >>> involved >>> in its boot process. If not bootloader related, I'll go ahead and file a >>> bug, >>> or even if it is, but you indicate you want one anyway. > > >> >> https://www.freedesktop.org/software/systemd/man/systemd.offline-updates.html > > >> What triggers it is the creation of /system-update symlink and a >> reboot. Then systemd picks that up and for that boot considers >> system-update.target the default target. > > > So apparently the kernel cmdline can be involved, and the only bug appears > to be that the wiki page has no boot stanza admonition that the cmdline must > not include anything to avoid booting to the temporary default target (in > this case "3", which is a parameter I include on most of my kernel > cmdlines). Anything that overrides default.target is supposed to be temporary. To make it the default, and therefore maintain compatibility with system upgrades: systemctl set-default multi-user.target In effect the upgrade fails because there are two conflicting temporary default overrides: /system-updates and the 3. -- Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: 'dnf system-upgrade reboot' doesn't do anything
Chris Murphy composed on 2016-08-30 16:13 (UTC-0600): Anything that overrides default.target is supposed to be temporary. To Not everything gets used as it's "supposed to be" used. With a dozen or more installations spread across dozens of machines, a digit in a stanza constitutes a keyword in answering the question "what will happen if I proceed with this" when looking at the selected boot menu item. make it the default, and therefore maintain compatibility with system upgrades: systemctl set-default multi-user.target That was probably done already. I'm still waiting to see evidence that the upgrade process is actually proceeding, at least 35 minutes after having "Reached target System Update" show up on the screen. In effect the upgrade fails because there are two conflicting temporary default overrides: /system-updates and the 3. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: 'dnf system-upgrade reboot' doesn't do anything [solved]
Felix Miata composed on 2016-08-30 18:44 (UTC-0400): I'm still waiting to see evidence that the upgrade process is actually proceeding, at least 35 minutes after having "Reached target System Update" show up on the screen. Success. E7500 Core2Duo 2.93GHz CPU. About 54 minutes long boot according to journal timestamps. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Fedora 25 updates-testing report
The following Fedora 25 Security updates need testing: Age URL 18 https://bodhi.fedoraproject.org/updates/FEDORA-2016-f4a443888b tomcat-8.0.36-2.fc25 18 https://bodhi.fedoraproject.org/updates/FEDORA-2016-9b17661de5 jasper-1.900.1-33.fc25 13 https://bodhi.fedoraproject.org/updates/FEDORA-2016-4dedc6ec3d firewalld-0.4.3.3-1.fc25 8 https://bodhi.fedoraproject.org/updates/FEDORA-2016-d1408c3ba3 ca-certificates-2016.2.9-1.1.fc25 5 https://bodhi.fedoraproject.org/updates/FEDORA-2016-9b3ed5f170 chicken-4.11.0-3.fc25 1 https://bodhi.fedoraproject.org/updates/FEDORA-2016-49e1e93a66 phpMyAdmin-4.6.4-2.fc25 1 https://bodhi.fedoraproject.org/updates/FEDORA-2016-9299ce1c7d mediawiki-1.27.1-1.fc25 1 https://bodhi.fedoraproject.org/updates/FEDORA-2016-125ea34ff9 keepass-2.34-1.fc25 1 https://bodhi.fedoraproject.org/updates/FEDORA-2016-46d09daeff libksba-1.3.5-1.fc25 The following Fedora 25 Critical Path updates have yet to be approved: Age URL 18 https://bodhi.fedoraproject.org/updates/FEDORA-2016-d1392ad5ad nss-3.26.0-1.0.fc25 nss-softokn-3.26.0-1.0.fc25 nss-util-3.26.0-1.0.fc25 18 https://bodhi.fedoraproject.org/updates/FEDORA-2016-9b17661de5 jasper-1.900.1-33.fc25 12 https://bodhi.fedoraproject.org/updates/FEDORA-2016-672bb93f5a libfm-1.2.4-6.D20160627git2a537414de.fc25 8 https://bodhi.fedoraproject.org/updates/FEDORA-2016-d1408c3ba3 ca-certificates-2016.2.9-1.1.fc25 7 https://bodhi.fedoraproject.org/updates/FEDORA-2016-cf4cb4e3f7 spatialite-tools-4.3.0-13.fc25 sqlite-3.14.1-1.fc25 5 https://bodhi.fedoraproject.org/updates/FEDORA-2016-37c9db36c2 dracut-044-77.fc25 5 https://bodhi.fedoraproject.org/updates/FEDORA-2016-cbdde50ec4 selinux-policy-3.13.1-211.fc25 3 https://bodhi.fedoraproject.org/updates/FEDORA-2016-5e40d80b1c livecd-tools-23.4-1.fc25 3 https://bodhi.fedoraproject.org/updates/FEDORA-2016-4976a748a1 libtasn1-4.9-1.fc25 3 https://bodhi.fedoraproject.org/updates/FEDORA-2016-de1f4e692b elfutils-0.167-1.fc25 3 https://bodhi.fedoraproject.org/updates/FEDORA-2016-f695073a52 xorg-x11-server-1.18.4-4.fc25 2 https://bodhi.fedoraproject.org/updates/FEDORA-2016-e4e1add318 pcmanfm-1.2.4-3.fc25 2 https://bodhi.fedoraproject.org/updates/FEDORA-2016-bf60f55f04 lxsession-0.5.2-11.D20160817git699c1695c2.fc25 1 https://bodhi.fedoraproject.org/updates/FEDORA-2016-439c23e9bb hwdata-0.292-1.fc25 1 https://bodhi.fedoraproject.org/updates/FEDORA-2016-66cab49b1f gnutls-3.5.3-2.fc25 1 https://bodhi.fedoraproject.org/updates/FEDORA-2016-383ce09620 xorg-x11-xinit-1.3.4-12.fc25 0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-38e924ab91 libtdb-1.3.11-1.fc25 0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-ca42901c9b kernel-4.8.0-0.rc4.git0.1.fc25 0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-4f0cc1cc10 pcre-8.39-3.fc25 0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-7f4512e707 iso-codes-3.70-1.fc25 0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-1d28afd486 krb5-1.14.3-8.fc25 0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-dd69d33a8b mutter-3.21.90-3.fc25 0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-788a7edfd7 NetworkManager-1.4.0-2.fc25 network-manager-applet-1.4.0-1.fc25 The following builds have been pushed to Fedora 25 updates-testing NetworkManager-1.4.0-2.fc25 R-littler-0.3.1-1.fc25 ardour5-5.3.0-1.fc25 beignet-1.2.0-1.fc25 cAudio-2.3.1-3.fc25 clatd-1.4-2.fc25 cpuid-20160814-1.fc25 cqrlog-2.0.2-1.fc25 criu-2.5-1.fc25 entr-3.6-7.fc25 feedreader-1.6.2-1.fc25 fluid-0.8.0-1.fc25 fmt-3.0.0-1.fc25 gap-pkg-guava-3.13.1-2.fc25 gonvert-0.2.39-1.fc25 greenisland-0.8.1-1.fc25 hawaii-icon-theme-0.8.0-1.fc25 hawaii-shell-0.8.0-1.fc25 hawaii-system-preferences-0.8.0-1.fc25 hawaii-widget-styles-0.8.0-1.fc25 hawaii-workspace-0.8.1-1.fc25 hplip-3.16.8-1.fc25 iso-codes-3.70-1.fc25 kde-connect-1.0-1.fc25 kernel-4.8.0-0.rc4.git0.1.fc25 kgb-bot-1.31-9.fc25 krb5-1.14.3-8.fc25 lasem-0.4.3-4.fc25 libhawaii-0.8.0-1.fc25 libinput-1.4.2-1.fc25 libpst-0.6.68-1.fc25 libtdb-1.3.11-1.fc25 metamath-0.134-1.fc25 mingw-libtasn1-4.9-1.fc25 mpc-0.28-1.fc25 mutter-3.21.90-3.fc25 network-manager-applet-1.4.0-1.fc25 nfs-ganesha-2.4.0-0.17rc1.fc25 nodejs-6.5.0-103.fc25 nodejs-buffertools-2.1.3-13.fc25.1 nodejs-fs-ext-0.5.0-10.fc25.1 nodejs-gdal-0.9.2-2.fc25.1 nodejs-i2c-0.2.3-2.fc25 nodejs-iconv-2.2.1-2.fc25 nodejs-libxmljs-0.18.0-2.fc25 nodejs-mapnik-3.5.12-3.fc25 nodejs-node-expat-2.3.11-9.fc25.1 nodejs-node-stringprep-0.7.3-11.fc25.1 nodejs-sqlite3-3.1.4-2.fc25 nodejs-zipfile-0.5.9-8.fc25.1 parallel-20160722-2.fc25 pcre-8.39-3.fc25 perl-Data-Dump-Streamer-2.40-1.fc25 perl-MIME-tools-5.50
Re: Self-introduction: Akinsola
On Mon, 2016-08-29 at 15:59 +, Akinsola wrote: > Hi Everyone, > > I am intrigued by my decision to join the QA Group, I have always > wanted to give back to the community that gives me much more than I > would have ever give back. I have some experience in System > Administration and Software development mainly Java, Ruby but I do > experiment a log with python e.t.c > > I am Akinsola, 32 years old, currently lives in Lagos,Nigeria. I > work more like a DevOps in Software Consulting firm in Lagos Nigeria. > I have used Linux all my professional life of not more than 5years. > > I would appreciate if I am accepted to this group and help in anyway > I can. Hi, and welcome, Akinsola! I have approved your QA group membership :) Thanks for volunteering, and do let us know if you need any help or have any ideas! :) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Testing idea: kernel 4.7 for Fedora 23 / Fedora 24
Hi folks! Just thought I'd send out a testing idea for anyone who's looking for something they can do. We currently have kernel 4.7 in updates-testing for Fedora 23 and Fedora 24: 23 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-f1adaaadc6 24 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-2e5ebfed6d it's always good to get new kernel releases tested on as much hardware as possible, so if you haven't done it yet, please try updating the kernel on any machines you have running Fedora 23 or 24. This command should do it: dnf --enablerepo=updates-testing update kernel* then you can reboot, and check if all your hardware and your normal use of the system works OK with the new kernel. If it does, give positive feedback for the update; if not, file a bug and give negative feedback for the update, with a link to your bug report. Testing kernel updates is nice and safe, because even if it doesn't work well, you can just reboot and pick an older kernel from the boot menu - Fedora will always keep three kernels installed, so you have a fallback if the newest one doesn't work right. Thanks everyone! :) Just as a quick note on other testing topics: for Fedora 25 validation, we'll start getting nightly composes 'nominated' for testing again soon, working towards the Beta release; Beta freeze is 2016-09-27, so a month or so to go before we start thinking about Beta RCs. The Fedora 25 Test Days should also be starting up soon - Sumantro is away right now, but I expect we'll start seeing announcements soon, so look out for those! And of course, we can always test updates (not just the kernel updates) for 23, 24 and 25. Happy testing :) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Testing idea: kernel 4.7 for Fedora 23 / Fedora 24
Hi, tried dnf --enablerepo=updates-testing update kernel* for F24, did't get kernel 4.7. Have I to enable too something with Bodhi? Kind regards -Original Message- From: Adam Williamson To: For testing and quality assurance of Fedora releases Sent: Wed, Aug 31, 2016 8:19 am Subject: Testing idea: kernel 4.7 for Fedora 23 / Fedora 24 Hi folks! Just thought I'd send out a testing idea for anyone who'slooking for something they can do.We currently have kernel 4.7 in updates-testing for Fedora 23 andFedora 24:23 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-f1adaaadc624 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-2e5ebfed6dit's always good to get new kernel releases tested on as much hardwareas possible, so if you haven't done it yet, please try updating thekernel on any machines you have running Fedora 23 or 24. This commandshould do it:dnf --enablerepo=updates-testing update kernel*then you can reboot, and check if all your hardware and your normal useof the system works OK with the new kernel. If it does, give positivefeedback for the update; if not, file a bug and give negative feedbackfor the update, with a link to your bug report. Testing kernel updatesis nice and safe, because even if it doesn't work well, you can justreboot and pick an older kernel from the boot menu - Fedora will alwayskeep three kernels installed, so you have a fallback if the newest onedoesn't work right.Thanks everyone! :)Just as a quick note on other testing topics: for Fedora 25 validation,we'll start getting nightly composes 'nominated' for testing againsoon, working towards the Beta release; Beta freeze is 2016-09-27, so amonth or so to go before we start thinking about Beta RCs. The Fedora25 Test Days should also be starting up soon - Sumantro is away rightnow, but I expect we'll start seeing announcements soon, so look outfor those! And of course, we can always test updates (not just thekernel updates) for 23, 24 and 25. Happy testing :)--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
