Fedora Rawhide-20180919.n.0 compose check report
No missing expected images. Failed openQA tests: 8/132 (x86_64), 1/24 (i386), 1/2 (arm) New failures (same test did not fail in Rawhide-20180917.n.1): ID: 283832 Test: x86_64 Everything-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/283832 ID: 283833 Test: x86_64 Everything-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/283833 ID: 283838 Test: x86_64 Workstation-live-iso base_update_cli URL: https://openqa.fedoraproject.org/tests/283838 ID: 283890 Test: x86_64 universal install_kickstart_firewall_disabled URL: https://openqa.fedoraproject.org/tests/283890 ID: 283895 Test: x86_64 universal install_blivet_no_swap@uefi URL: https://openqa.fedoraproject.org/tests/283895 ID: 283918 Test: x86_64 universal install_kickstart_user_creation URL: https://openqa.fedoraproject.org/tests/283918 ID: 283949 Test: i386 universal install_blivet_lvmthin URL: https://openqa.fedoraproject.org/tests/283949 Old failures (same test failed in Rawhide-20180917.n.1): ID: 283846 Test: x86_64 Workstation-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/283846 ID: 283862 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/283862 ID: 283868 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/283868 Soft failed openQA tests: 3/132 (x86_64), 2/24 (i386) (Tests completed, but using a workaround for a known bug) New soft failures (same test did not soft fail in Rawhide-20180917.n.1): ID: 283836 Test: x86_64 Workstation-live-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/283836 ID: 283837 Test: x86_64 Workstation-live-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/283837 Old soft failures (same test soft failed in Rawhide-20180917.n.1): ID: 283830 Test: i386 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/283830 ID: 283831 Test: i386 Server-dvd-iso install_default URL: https://openqa.fedoraproject.org/tests/283831 ID: 283909 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/283909 Passed openQA tests: 121/132 (x86_64), 21/24 (i386) New passes (same test did not pass in Rawhide-20180917.n.1): ID: 283817 Test: x86_64 Server-dvd-iso install_repository_nfs_graphical URL: https://openqa.fedoraproject.org/tests/283817 ID: 283851 Test: i386 Workstation-live-iso install_default URL: https://openqa.fedoraproject.org/tests/283851 ID: 283854 Test: x86_64 KDE-live-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/283854 ID: 283859 Test: x86_64 KDE-live-iso install_no_user URL: https://openqa.fedoraproject.org/tests/283859 ID: 283865 Test: x86_64 KDE-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/283865 ID: 283888 Test: x86_64 universal install_arabic_language URL: https://openqa.fedoraproject.org/tests/283888 ID: 283907 Test: x86_64 universal upgrade_desktop_64bit URL: https://openqa.fedoraproject.org/tests/283907 ID: 283922 Test: x86_64 universal install_no_swap@uefi URL: https://openqa.fedoraproject.org/tests/283922 ID: 283929 Test: x86_64 universal upgrade_2_desktop_64bit URL: https://openqa.fedoraproject.org/tests/283929 ID: 283930 Test: x86_64 universal upgrade_2_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/283930 ID: 283934 Test: x86_64 universal support_server URL: https://openqa.fedoraproject.org/tests/283934 ID: 283938 Test: x86_64 universal install_multi@uefi URL: https://openqa.fedoraproject.org/tests/283938 ID: 283940 Test: x86_64 universal upgrade_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/283940 ID: 283942 Test: x86_64 universal install_iscsi URL: https://openqa.fedoraproject.org/tests/283942 ID: 283943 Test: x86_64 universal install_kickstart_nfs URL: https://openqa.fedoraproject.org/tests/283943 ID: 283950 Test: i386 universal upgrade_2_desktop_32bit URL: https://openqa.fedoraproject.org/tests/283950 ID: 283951 Test: i386 universal upgrade_desktop_32bit URL: https://openqa.fedoraproject.org/tests/283951 Skipped openQA tests: 1 of 158 Installed system changes in test x86_64 Server-boot-iso install_default: System load changed from 1.53 to 1.41 Previous test data: https://openqa.fedoraproject.org/tests/282051#downloads Current test data: https://openqa.fedoraproject.org/tests/283804#downloads Installed system changes in test x86_64 Server-boot-iso install_default@uefi: System load changed from 1.84 to 1.63 Previous test data: https://openqa.fedoraproject.org/tests/282052#downloads Current test data: https://openqa.fedoraproject.org/tests/283805#downloads Installed system changes in test x86_64 Server-dvd-iso install_default_upload:
Fedora 29-20180919.n.0 compose check report
No missing expected images. Failed openQA tests: 3/132 (x86_64), 2/24 (i386), 1/2 (arm) ID: 284048 Test: x86_64 Workstation-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/284048 ID: 284064 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/284064 ID: 284069 Test: i386 KDE-live-iso install_default URL: https://openqa.fedoraproject.org/tests/284069 ID: 284070 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/284070 ID: 284136 Test: x86_64 universal support_server URL: https://openqa.fedoraproject.org/tests/284136 ID: 284153 Test: i386 universal upgrade_desktop_32bit URL: https://openqa.fedoraproject.org/tests/284153 Soft failed openQA tests: 4/132 (x86_64), 2/24 (i386) (Tests completed, but using a workaround for a known bug) ID: 284006 Test: x86_64 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/284006 ID: 284007 Test: x86_64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/284007 ID: 284032 Test: i386 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/284032 ID: 284033 Test: i386 Server-dvd-iso install_default URL: https://openqa.fedoraproject.org/tests/284033 ID: 284038 Test: x86_64 Workstation-live-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/284038 ID: 284111 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/284111 Passed openQA tests: 123/132 (x86_64), 20/24 (i386) Skipped openQA tests: 2 of 158 -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: F29-beta - Policykit Agent error VNC access to Xfce DE
On 9/21/18 11:14 PM, Robert Moskowitz wrote: > > > On 9/21/18 11:02 AM, Ed Greshko wrote: >> On 9/21/18 9:14 PM, Robert Moskowitz wrote: >>> I have had this problem pre beta images. This is the F29-armfhp code base. >>> >>> I am running vnc server as a service. I have edited the xstartup to have: >>> >>> # exec /etc/X11/xinit/xinitrc >>> exec /bin/sh /etc/xdg/xfce4/xinitrc >>> xrdb $HOME/.Xresources >>> startxfce4 & >>> >>> Note that currently, the is no .Xresources file. >> I do not know why you're doing that. But, I haven't. >> >>> When I connect to the system after a fresh boot or vncserver restart I get >>> a dialog >>> with: >>> >>> Error XFCE PolicyKit Agent >>> >>> Ed Greshko reported on the Fedora list (as I thought this was a more general >>> VNC/Xfce error having nothing to do with the beta) that he does not get >>> this error, >>> but he is NOT running vncserver as a service. Rather from an SSH session. >> I have configured by f28 system to run vncsever as a service and I see the >> error >> you're reporting. >> >> I believe I understand why the error is presented. >> >> If you start the vncserver you'll see something like this >> >> polkitd 706 1 0 22:31 ? 00:00:02 /usr/lib/polkit-1/polkitd >> --no-debug >> egreshko 3527 3497 2 22:58 ? 00:00:00 /usr/libexec/xfce-polkit >> >> running >> >> When you make a vnc client connection, you get the error and then you'll see >> only >> >> polkitd 706 1 0 22:31 ? 00:00:03 /usr/lib/polkit-1/polkitd >> --no-debug >> >> running. /usr/libexec/xfce-polkit has crashed. Why? I have no idea at >> 23:00. > > My F28 install is right now doing its dnf update which will take a bit. But > I was > setting what starts at startup via Settings > Session and Startup > > And I noticed that polkit is started there. I bet if you turn that off, > things MAY > get better. Of course then console login will not have polkit. So perhaps > vncserver should NOT be running polkit? > > After a bit of testing and a bit of googling the answer is. vncserver and polkit don't play nice when vncserver is started as a service as described in /lib/systemd/system/vncserver@.service. The issue is not confined to Xfce. The same basic problem exists when the spin used in KDE. As mentioned elsewhere, if you ssh into the system and start vncserver manually then everything works "normally" for the most part. It seems nobody has done much to attempt to fix the problem from what I can tell. That being said, a workaround is described here https://forums.fedoraforum.org/showthread.php?316905-PolicyKit-failed-over-headless-VNC=1809280#post1809280 With the other alternative to be having your vnc client (remmina can do it) issue a pre-command via ssh to start the vncserver manually. Of course you'll to have "authorized_keys" on the vncserver system side to make this seamless. -- Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell them, then tell them what you told them." signature.asc Description: OpenPGP digital signature ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On Fri, 21 Sep 2018 14:56:07 -0400
"pmkel...@frontier.com" wrote:
> BTW does doing network install mean I have to have a server setup to
> serve the installs?
I think you are mixing two different install methods. There is a
netinstall image, that has a barebones Fedora that gets installed, and
allows the installation of all other software from the
Fedora repositories over the internet. I use this because it is small,
and I just install the barebones and some essential packages like vim
and such. I then boot into the newly installed Fedora and install what
I want from the repositories. This used to be possible to do by
installing a small file in /boot, bfo.lkrn, and booting directly from
the image that was desired.
https://boot.fedoraproject.org/index
Unfortunately, as Charles said, it doesn't seem to work anymore. It
was great. Just put a stanza in grub.cfg, boot and select it, and
everything was downloaded from the internet. No need for media at
all. I suppose it just got to be too much trouble to maintain. It
doesn't crash or anything, but I think the links are out of date.
menuentry 'Boot BFO' --class gnu-linux --class gnu --class os {
linux16 /bfo.lkrn
}
There is also a net install using a central server for many machines.
That is what Samuel was referring to. All the machines are installed
using a script and a standard image, pulling everything off the local
network instead of the internet. I don't think that is what you want
if you were installing from DVD.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: F29-beta - Policykit Agent error VNC access to Xfce DE
On 9/21/18 11:02 AM, Ed Greshko wrote: On 9/21/18 9:14 PM, Robert Moskowitz wrote: I have had this problem pre beta images. This is the F29-armfhp code base. I am running vnc server as a service. I have edited the xstartup to have: # exec /etc/X11/xinit/xinitrc exec /bin/sh /etc/xdg/xfce4/xinitrc xrdb $HOME/.Xresources startxfce4 & Note that currently, the is no .Xresources file. I do not know why you're doing that. But, I haven't. When I connect to the system after a fresh boot or vncserver restart I get a dialog with: Error XFCE PolicyKit Agent Ed Greshko reported on the Fedora list (as I thought this was a more general VNC/Xfce error having nothing to do with the beta) that he does not get this error, but he is NOT running vncserver as a service. Rather from an SSH session. I have configured by f28 system to run vncsever as a service and I see the error you're reporting. I believe I understand why the error is presented. If you start the vncserver you'll see something like this polkitd 706 1 0 22:31 ? 00:00:02 /usr/lib/polkit-1/polkitd --no-debug egreshko 3527 3497 2 22:58 ? 00:00:00 /usr/libexec/xfce-polkit running When you make a vnc client connection, you get the error and then you'll see only polkitd 706 1 0 22:31 ? 00:00:03 /usr/lib/polkit-1/polkitd --no-debug running. /usr/libexec/xfce-polkit has crashed. Why? I have no idea at 23:00. Since I could not get my F28 working for vnc login to Xfce, I went back to my F29 image. I disabled polkit startup in the Xfce startup widget and rebooted. Now I don't get the PolicyKit error, but no change in being able to mount an USB drive or unlock printer config to add a printer. So I suspect that Polkit should be left on in Xfce, but get the xstartup right so it does not also run polkit. Which gets back to an earlier thread: We DON'T know how to run DE other than Gnome for vncserver. It would be very nice for some guidance on this. And with this, past time to shutdown. Catch you later. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On 9/21/18 3:40 PM, Samuel Sieb wrote: On 9/21/18 12:35 PM, Samuel Sieb wrote: On 9/21/18 11:56 AM, pmkel...@frontier.com wrote: BTW does doing network install mean I have to have a server setup to serve the installs? I only ask because right now my knowledge of servers (now to set them up and maintain them) is zero and there doesn't seem to be any automatic tools to help. I got a copy of Fedora 28 server. I tried to set it up to serve some data files and failed. After a couple tries I just implemented file sharing and kept the commonly used stuff in one of the PCs Public directory. Yes, it requires a dhcp server, tftp server, and web server. If you eventually get around to trying to set it up, I would be happy to help. There's also https://boot.fedoraproject.org/ but I can't get it to work. Oh, in this long email thread, I've lost track of people. I thought you were the person I was discussing PXE with earlier. As Adam mentioned, for a basic network install, you can use USB. But in general, however you are currently installing with a DVD, you can do the same with a USB stick. Just write the iso image to it. For this list, this has really been an involved thread. I was the one you were talkiong to about PXE earlier. Not pmkelly. That said, If you put the Netinstall iso image on a bootable media (bootable for your system), and have decent net access speed, you let Netinstall do its thing to get everything NOT on the iso image from the repos. Nothing to maintain locally. Just potentially a lot of downloads if you do a lot of build testing. Minimally, you can build a local apache server and rsync the current repos to that. Then point the Netinstall there. Of course you need IP access in both cases which means DHCP etc. About time to sign off for the weekend and Sunday night starts Succos, so not much from me until Wednesday. Have a good time all. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On Fri, Sep 21, 2018 at 12:35:17PM -0700, Samuel Sieb wrote: > >BTW does doing network install mean I have to have a server setup > >to serve the installs? I only ask because right now my knowledge > >of servers (now to set them up and maintain them) is zero and > >there doesn't seem to be any automatic tools to help. I got a copy > >of Fedora 28 server. I tried to set it up to serve some data files > >and failed. After a couple tries I just implemented file sharing > >and kept the commonly used stuff in one of the PCs Public > >directory. > Yes, it requires a dhcp server, tftp server, and web server. If you > eventually get around to trying to set it up, I would be happy to > help. Doing a PXE install means that. But doing a network install booting from a USB stick (or, eh, a CD/DVD) doesn't need any local infrastructure. Just a route to Fedora mirrors. -- Matthew Miller Fedora Project Leader ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On 9/21/18 12:39 PM, Robert Moskowitz wrote: On 9/21/18 3:35 PM, Samuel Sieb wrote: On 9/21/18 11:56 AM, pmkel...@frontier.com wrote: BTW does doing network install mean I have to have a server setup to serve the installs? I only ask because right now my knowledge of servers (now to set them up and maintain them) is zero and there doesn't seem to be any automatic tools to help. I got a copy of Fedora 28 server. I tried to set it up to serve some data files and failed. After a couple tries I just implemented file sharing and kept the commonly used stuff in one of the PCs Public directory. Yes, it requires a dhcp server, tftp server, and web server. If you eventually get around to trying to set it up, I would be happy to help. There's also https://boot.fedoraproject.org/ but I can't get it to work. You mean remote access to the repos won't work as it does for the production netinstall? Not that I have too much of a problem rsyncing the updates, but I have always done my netinstalls from the mirrors. Just to be clear, I was referring to setting up a PXE boot network install, not a standard boot off a DVD or USB drive. The web server is needed to load the installer image, although possibly that could be loaded over tftp as well. Also the kickstart file would be on the web server if you use one. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On 9/21/18 12:35 PM, Samuel Sieb wrote: On 9/21/18 11:56 AM, pmkel...@frontier.com wrote: BTW does doing network install mean I have to have a server setup to serve the installs? I only ask because right now my knowledge of servers (now to set them up and maintain them) is zero and there doesn't seem to be any automatic tools to help. I got a copy of Fedora 28 server. I tried to set it up to serve some data files and failed. After a couple tries I just implemented file sharing and kept the commonly used stuff in one of the PCs Public directory. Yes, it requires a dhcp server, tftp server, and web server. If you eventually get around to trying to set it up, I would be happy to help. There's also https://boot.fedoraproject.org/ but I can't get it to work. Oh, in this long email thread, I've lost track of people. I thought you were the person I was discussing PXE with earlier. As Adam mentioned, for a basic network install, you can use USB. But in general, however you are currently installing with a DVD, you can do the same with a USB stick. Just write the iso image to it. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On 9/21/18 3:35 PM, Samuel Sieb wrote: On 9/21/18 11:56 AM, pmkel...@frontier.com wrote: BTW does doing network install mean I have to have a server setup to serve the installs? I only ask because right now my knowledge of servers (now to set them up and maintain them) is zero and there doesn't seem to be any automatic tools to help. I got a copy of Fedora 28 server. I tried to set it up to serve some data files and failed. After a couple tries I just implemented file sharing and kept the commonly used stuff in one of the PCs Public directory. Yes, it requires a dhcp server, tftp server, and web server. If you eventually get around to trying to set it up, I would be happy to help. There's also https://boot.fedoraproject.org/ but I can't get it to work. You mean remote access to the repos won't work as it does for the production netinstall? Not that I have too much of a problem rsyncing the updates, but I have always done my netinstalls from the mirrors. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On 9/21/18 11:56 AM, pmkel...@frontier.com wrote: BTW does doing network install mean I have to have a server setup to serve the installs? I only ask because right now my knowledge of servers (now to set them up and maintain them) is zero and there doesn't seem to be any automatic tools to help. I got a copy of Fedora 28 server. I tried to set it up to serve some data files and failed. After a couple tries I just implemented file sharing and kept the commonly used stuff in one of the PCs Public directory. Yes, it requires a dhcp server, tftp server, and web server. If you eventually get around to trying to set it up, I would be happy to help. There's also https://boot.fedoraproject.org/ but I can't get it to work. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: F29 Beta 1.5 problem
On Fri, 2018-09-21 at 08:49 -0400, pmkel...@frontier.com wrote: > Yesterday afternoon (9/20), I did a clean install of F29 Beta 1.5 onto > bare metal via DVD. The PC is a Lenovo M59P with an E8400 processor. The > ISO had been check-summed and passed. The PC booted fine and the media > test ran and passed. Anaconda ran perfectly and the install completed > normally. I did a restart, logged in, and allowed the lock to time out. > > The fan on this system rarely runs at all, but in a few hours of sitting > idle the fan came on. I logged in and started the system monitor and > noted the both core0 and core1 were trading off running at 100%. The > trade cycle was running between 20 and 30 seconds. Sometimes they would > both run at 50% for a few seconds. When I looked at the processes, > gnome-software was the problem. I let the lock time out and left the > system overnight. This morning (9/21) the fan was running full speed and > both core0 and core1 was stuck hard at 100%. Again gnome-software was > the problem. I wanted to see if anything else would run so I started > Rhythm box. There were delays getting it going, but it did start and > worked (radio stream) with no apparent gaps in the audio. When I checked > the Resources and processes, apparently gnome-software was sharing with > Rhythm Box, but only what Rhythm Box needed. When I closed Rhythm Box, > gnome-software went back to taking 90+% of the core0 and core1 cycles. > > I just did a restart and the system returned to normal (fan not > running). This time I'm not going to login. I'm just going to let it sit > and see what happens. > > This is the same problem I found a few days ago with B 1.3 I wrote about > it then, but it was a day later, after a reminder that I wrote and > called out gnome-software. mschwendt reported much the same in the thread "Neverending CPU usage by gnome-software and packagekit". I wonder if software/pk is getting stuck somehow, or doing something far more often than it should. Can one of you post the output of 'sudo journalctl -b -u packagekit', perhaps? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On Fri, 2018-09-21 at 14:56 -0400, pmkel...@frontier.com wrote: > > On 9/21/18 1:30 PM, Adam Williamson wrote: > > On Thu, 2018-09-20 at 22:35 -0400, Harold Dost wrote: > > > Is having this as a test criteria *that* burdensome? > > > > Yes, frankly. Not a lot of testers even keep a DVD-RW drive and media > > around any more. It takes like a half hour just to write all the media > > for testing, then another few hours to run complete installs from them > > all (since optical media are *slow*). > > > > If it's not burdensome, why does no-one except the paid RH folks ever > > seem to run the test? And usually at the last minute, at that? > > > > I've had to buy three DVD-RW drives *solely for the purpose of being > > able to test this* (they keep dying, the things aren't terribly > > reliable). And I keep a spindle of media around, again, solely for the > > purpose of testing this, I don't use them for anything else. (In fact > > I've nearly run out, so if we keep this criteria, I'm gonna have to go > > out and blow some money on some more media I won't ever use for > > anything but testing this). > > > > If people outside of the RH team ever actually ran this test, I'd be > > more in favour of keeping it, but I don't think any of the people > > speaking up about how vital this is to them have ever actually chipped > > in and run the test before. > > > > Well, I know I'm an exception, I only test workstation live, I don't > test every drop, and I know that no one is requiring me to, but I > actually spend money on DVD media to help out with testing. Yes, I know > that someday DVDs will go away and I'll have to figure out this network > install thing, but for right now I use them because it's what I'm > comfortable doing. Thanks for that. > BTW does doing network install mean I have to have a server setup to > serve the installs? I am not sure what you mean by 'network install' exactly. If you mean PXE stuff, you don't need to know that to replace DVDs. You can just replace DVDs with a USB stick. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Fedora 29 compose report: 20180919.n.0 changes
OLD: Fedora-29-20180918.n.0 NEW: Fedora-29-20180919.n.0 = SUMMARY = Added images:2 Dropped images: 3 Added packages: 0 Dropped packages:0 Upgraded packages: 1 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 14.86 MiB Size of downgraded packages: 0 B Size change of upgraded packages: 1.27 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Python_Classroom vagrant-libvirt i386 Path: Labs/i386/images/Fedora-Python-Classroom-Vagrant-29-20180919.n.0.i386.vagrant-libvirt.box Image: Python_Classroom vagrant-virtualbox i386 Path: Labs/i386/images/Fedora-Python-Classroom-Vagrant-29-20180919.n.0.i386.vagrant-virtualbox.box = DROPPED IMAGES = Image: Cloud_Base qcow2 s390x Path: Cloud/s390x/images/Fedora-Cloud-Base-29-20180918.n.0.s390x.qcow2 Image: Cloud_Base raw-xz s390x Path: Cloud/s390x/images/Fedora-Cloud-Base-29-20180918.n.0.s390x.raw.xz Image: Container_Base docker s390x Path: Container/s390x/images/Fedora-Container-Base-29-20180918.n.0.s390x.tar.xz = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: pki-core-10.6.6-2.fc29 Old package: pki-core-10.6.6-1.fc29 Summary: PKI Core Package RPMs: pki-base pki-base-java pki-ca pki-console pki-javadoc pki-kra pki-ocsp pki-server pki-symkey pki-tks pki-tools pki-tps python3-pki Size: 14.86 MiB Size change: 1.27 MiB Changelog: * Mon Sep 10 2018 Dennis Gilmore - 10.6.6-2 - add back aarch64 support as esc is now built for aarch64 = DOWNGRADED PACKAGES = ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: F29-beta - Policykit Agent error VNC access to Xfce DE
On 9/21/18 11:02 AM, Ed Greshko wrote: On 9/21/18 9:14 PM, Robert Moskowitz wrote: I have had this problem pre beta images. This is the F29-armfhp code base. I am running vnc server as a service. I have edited the xstartup to have: # exec /etc/X11/xinit/xinitrc exec /bin/sh /etc/xdg/xfce4/xinitrc xrdb $HOME/.Xresources startxfce4 & Note that currently, the is no .Xresources file. I do not know why you're doing that. But, I haven't. When I connect to the system after a fresh boot or vncserver restart I get a dialog with: Error XFCE PolicyKit Agent Ed Greshko reported on the Fedora list (as I thought this was a more general VNC/Xfce error having nothing to do with the beta) that he does not get this error, but he is NOT running vncserver as a service. Rather from an SSH session. I have configured by f28 system to run vncsever as a service and I see the error you're reporting. I believe I understand why the error is presented. If you start the vncserver you'll see something like this polkitd 706 1 0 22:31 ? 00:00:02 /usr/lib/polkit-1/polkitd --no-debug egreshko 3527 3497 2 22:58 ? 00:00:00 /usr/libexec/xfce-polkit running When you make a vnc client connection, you get the error and then you'll see only polkitd 706 1 0 22:31 ? 00:00:03 /usr/lib/polkit-1/polkitd --no-debug running. /usr/libexec/xfce-polkit has crashed. Why? I have no idea at 23:00. I can't get vncserver started on my F28-arm image: # systemctl -l --no-pager status vncserver@:1 ● vncserver@:1.service - Remote desktop service (VNC) Loaded: loaded (/etc/systemd/system/vncserver@:1.service; enabled; vendor preset: disabled) Active: failed (Result: timeout) since Fri 2018-09-21 14:56:31 EDT; 2min 42s ago Process: 698 ExecStart=/usr/bin/vncserver -autokill :1 (code=exited, status=0/SUCCESS) Process: 639 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill :1 > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS) Sep 21 14:56:30 localhost com.redhat.imsettings[783]: [ 1537556190.857400]: GLib-GIO[878]: WARNING **: Error releasing name com.redhat.imsettings: The connection is closed Sep 21 14:56:30 localhost com.redhat.imsettings[783]: [ 1537556190.862384]: GLib-GIO[878]: CRITICAL **: Error while sending AddMatch() message: The connection is closed Sep 21 14:56:30 localhost com.redhat.imsettings[783]: [ 1537556190.85]: GLib-GIO[878]: CRITICAL **: Error while sending AddMatch() message: The connection is closed Sep 21 14:56:30 localhost com.redhat.imsettings[783]: [ 1537556190.870845]: IMSettings-Daemon[878]: INFO: Unloading imesttings module: gsettings Sep 21 14:56:30 localhost com.redhat.imsettings[783]: [ 1537556190.875148]: IMSettings-Daemon[878]: INFO: Stopping the main process for IBus [pid: 1145] Sep 21 14:56:30 localhost com.redhat.imsettings[783]: [ 1537556190.880760]: IMSettings-Daemon[878]: INFO: Sent a signal to stop /usr/bin/ibus-daemon [pid: 1145, time: 2018-09-21T18:56:30.880703Z] Sep 21 14:56:30 localhost com.redhat.imsettings[783]: [ 1537556190.883669]: IMSettings-Daemon[878]: INFO: imsettings-daemon is shut down. Sep 21 14:56:30 localhost pulseaudio[1042]: PulseAudio information vanished from X11! Sep 21 14:56:31 localhost systemd[1]: vncserver@:1.service: Failed with result 'timeout'. Sep 21 14:56:31 localhost systemd[1]: Failed to start Remote desktop service (VNC). How do I get it to not try and start pulseaudio? ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On Thu, Sep 20, 2018 at 09:24:56PM +, Rick Stevens wrote: > Ok, so ISO images would still be produced and could be burned to OM > for installation. There just isn't any guarantee (at release) that the > OM would actually boot and one could squawk it if it didn't and not be > poo-poo'd about it. I might be able to survive that, assuming that the > fixes for the unbootability (is that a word?) were timely. Yep, that's pretty much it. > I'm sorry for opening such a storm of messages here. I'm just a bit > sensitive to this as I'm the one that generally gets poked with the > sharp, pointy stick when the defecation hits the impeller around here. Heh, thanks. I can relate :) -- Matthew Miller Fedora Project Leader ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On Fri, Sep 21, 2018 at 02:23:24PM +0200, Kamil Paral wrote: > Speaking for I believe most of the QA team: "We'd be happy to". Testing > optical boot is a major PITA. The decision is not ours, though, but I > assume it belongs to the groups owning the media currently blocking optical > boot. Which is Spins SIG for Everything netinst and Workstation WG for > Workstation Live [1] (to be clear, nothing else is currently covered by > that criterion, just those two images). > > One more thing, Matthew, are you proposing we drop this for F30, or > immediately for F29? Immediately for F29, because realistically if it comes down to this as the only issue, I will advocate very passionately for releasing anyway. -- Matthew Miller Fedora Project Leader ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On 9/21/18 1:30 PM, Adam Williamson wrote: On Thu, 2018-09-20 at 22:35 -0400, Harold Dost wrote: Is having this as a test criteria *that* burdensome? Yes, frankly. Not a lot of testers even keep a DVD-RW drive and media around any more. It takes like a half hour just to write all the media for testing, then another few hours to run complete installs from them all (since optical media are *slow*). If it's not burdensome, why does no-one except the paid RH folks ever seem to run the test? And usually at the last minute, at that? I've had to buy three DVD-RW drives *solely for the purpose of being able to test this* (they keep dying, the things aren't terribly reliable). And I keep a spindle of media around, again, solely for the purpose of testing this, I don't use them for anything else. (In fact I've nearly run out, so if we keep this criteria, I'm gonna have to go out and blow some money on some more media I won't ever use for anything but testing this). If people outside of the RH team ever actually ran this test, I'd be more in favour of keeping it, but I don't think any of the people speaking up about how vital this is to them have ever actually chipped in and run the test before. Well, I know I'm an exception, I only test workstation live, I don't test every drop, and I know that no one is requiring me to, but I actually spend money on DVD media to help out with testing. Yes, I know that someday DVDs will go away and I'll have to figure out this network install thing, but for right now I use them because it's what I'm comfortable doing. BTW does doing network install mean I have to have a server setup to serve the installs? I only ask because right now my knowledge of servers (now to set them up and maintain them) is zero and there doesn't seem to be any automatic tools to help. I got a copy of Fedora 28 server. I tried to set it up to serve some data files and failed. After a couple tries I just implemented file sharing and kept the commonly used stuff in one of the PCs Public directory. Have a Great Day! Pat (tablepc) ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Nvidia and Fedora current state
On 9/21/18 10:20 AM, Michael Schwendt wrote: On Fri, 21 Sep 2018 17:33:11 +0200, Michael Schwendt wrote: A few days later, and GNOME Shell is hardly usable anymore. Mouse lag, stuttering, wiindow usage taking seconds, itt gets slower and slower. Just watch these typos as a result of trying to compose this email. Spontaneous key repetition because of major lag. F29 Rebooted a few times, and suddently the symptoms are gone again. It's like something doesn't initialize correctly when it happens. Are you using Wayland or Xorg? ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On Fri, 2018-09-21 at 13:52 -0400, Harold Dost wrote: > On Fri, Sep 21, 2018 at 1:30 PM Adam Williamson > wrote: > > On Thu, 2018-09-20 at 22:35 -0400, Harold Dost wrote: > > > Is having this as a test criteria *that* burdensome? > > > > Yes, frankly. Not a lot of testers even keep a DVD-RW drive and media > > around any more. It takes like a half hour just to write all the media > > for testing, then another few hours to run complete installs from them > > all (since optical media are *slow*). > > > > If it's not burdensome, why does no-one except the paid RH folks ever > > seem to run the test? And usually at the last minute, at that? > > > > I've had to buy three DVD-RW drives *solely for the purpose of being > > able to test this* (they keep dying, the things aren't terribly > > reliable). And I keep a spindle of media around, again, solely for the > > purpose of testing this, I don't use them for anything else. (In fact > > I've nearly run out, so if we keep this criteria, I'm gonna have to go > > out and blow some money on some more media I won't ever use for > > anything but testing this). > > > > If people outside of the RH team ever actually ran this test, I'd be > > more in favour of keeping it, but I don't think any of the people > > speaking up about how vital this is to them have ever actually chipped > > in and run the test before. > > -- > > Adam Williamson > > Fedora QA Community Monkey > > IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net > > http://www.happyassassin.net > > ___ > > test mailing list -- test@lists.fedoraproject.org > > To unsubscribe send an email to test-le...@lists.fedoraproject.org > > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org > > I want to make sure that I'm on the same page. > > Based on: > > Yes. We do not have 'burning optical discs from Fedora must work' in > > the release criteria, and never have. What we have in the release > > criteria is this: > > "Release-blocking live and dedicated installer images must boot when > > written to optical media of an appropriate size" > > Matthew is proposing that we drop that. > > Would it be calculable based on the ISO size whether it would author > correctly (only in terms of size) with out needing to burn it to a > real disk? Then burning to a disk would not be necessary, but prevents > the image from becoming overly bloated. No. See the other subthread where a couple of bugs from the Fedora 21 era showed that it's possible for ISO files to boot fine from USB, or when attached to a VM, but not boot when written to an actual optical disc. We already have a size check test which is automated, but just ensuring the ISO file is not larger than a physical CD or DVD is not sufficient to be sure it actually boots. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On Fri, Sep 21, 2018 at 1:30 PM Adam Williamson wrote: > > On Thu, 2018-09-20 at 22:35 -0400, Harold Dost wrote: > > Is having this as a test criteria *that* burdensome? > > Yes, frankly. Not a lot of testers even keep a DVD-RW drive and media > around any more. It takes like a half hour just to write all the media > for testing, then another few hours to run complete installs from them > all (since optical media are *slow*). > > If it's not burdensome, why does no-one except the paid RH folks ever > seem to run the test? And usually at the last minute, at that? > > I've had to buy three DVD-RW drives *solely for the purpose of being > able to test this* (they keep dying, the things aren't terribly > reliable). And I keep a spindle of media around, again, solely for the > purpose of testing this, I don't use them for anything else. (In fact > I've nearly run out, so if we keep this criteria, I'm gonna have to go > out and blow some money on some more media I won't ever use for > anything but testing this). > > If people outside of the RH team ever actually ran this test, I'd be > more in favour of keeping it, but I don't think any of the people > speaking up about how vital this is to them have ever actually chipped > in and run the test before. > -- > Adam Williamson > Fedora QA Community Monkey > IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net > http://www.happyassassin.net > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org I want to make sure that I'm on the same page. Based on: >Yes. We do not have 'burning optical discs from Fedora must work' in > the release criteria, and never have. What we have in the release > criteria is this: > "Release-blocking live and dedicated installer images must boot when > written to optical media of an appropriate size" > Matthew is proposing that we drop that. Would it be calculable based on the ISO size whether it would author correctly (only in terms of size) with out needing to burn it to a real disk? Then burning to a disk would not be necessary, but prevents the image from becoming overly bloated. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On 9/21/18 1:30 PM, Adam Williamson wrote: On Thu, 2018-09-20 at 22:35 -0400, Harold Dost wrote: Is having this as a test criteria *that* burdensome? Yes, frankly. Not a lot of testers even keep a DVD-RW drive and media around any more. It takes like a half hour just to write all the media for testing, then another few hours to run complete installs from them all (since optical media are *slow*). If it's not burdensome, why does no-one except the paid RH folks ever seem to run the test? And usually at the last minute, at that? I've had to buy three DVD-RW drives *solely for the purpose of being able to test this* (they keep dying, the things aren't terribly reliable). And I keep a spindle of media around, again, solely for the purpose of testing this, I don't use them for anything else. (In fact I've nearly run out, so if we keep this criteria, I'm gonna have to go out and blow some money on some more media I won't ever use for anything but testing this). If people outside of the RH team ever actually ran this test, I'd be more in favour of keeping it, but I don't think any of the people speaking up about how vital this is to them have ever actually chipped in and run the test before. My challenge is a physical system to test on. I can do armv7 testing; I have 3 Cubies here on my desk for various tests, and it is easy to swap out media. But x86_64 testing? I only have my 2 Lenovo x120e systems. I am going to have to test k3b writing again and if the bug is not fixed (it is in F29), implement Ed's workaround already as that is the only thing I need my old F24 system for. And it is OK for testing as the fan is dying. I have to hit ebay up for a Lenovo x141. So perhaps mid-next month I can do some netinstall testing from OM. Oh, yesterday I found out that my Juniper firewall uses some old TLS crypto that FF on F28 does not like. So I either have to upgrade its firmware, turn off TLS, or disable this FF check. ARGH! Shows how long it has been since I have had to log in and check something on it. That SSG5 just runs. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Fedora rawhide compose report: 20180919.n.0 changes
OLD: Fedora-Rawhide-20180917.n.1 NEW: Fedora-Rawhide-20180919.n.0 = SUMMARY = Added images:0 Dropped images: 4 Added packages: 6 Dropped packages:115 Upgraded packages: 115 Downgraded packages: 0 Size of added packages: 38.74 MiB Size of dropped packages:40.32 MiB Size of upgraded packages: 4.31 GiB Size of downgraded packages: 0 B Size change of upgraded packages: -10.74 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = Image: Scientific vagrant-virtualbox x86_64 Path: Labs/x86_64/images/Fedora-Scientific-Vagrant-Rawhide-20180917.n.1.x86_64.vagrant-virtualbox.box Image: Mate live x86_64 Path: Spins/x86_64/iso/Fedora-MATE_Compiz-Live-x86_64-Rawhide-20180917.n.1.iso Image: Scientific vagrant-libvirt x86_64 Path: Labs/x86_64/images/Fedora-Scientific-Vagrant-Rawhide-20180917.n.1.x86_64.vagrant-libvirt.box Image: Container_Base docker s390x Path: Container/s390x/images/Fedora-Container-Base-Rawhide-20180917.n.1.s390x.tar.xz = ADDED PACKAGES = Package: psftools-1.0.10-2.fc30 Summary: Conversion tools for .PSF fonts RPMs:psftools Size:2.57 MiB Package: rubygem-jekyll-email-protect-1.1.0-1.fc30 Summary: A simple liquid filter which converts emails into percent-encoded strings RPMs:rubygem-jekyll-email-protect rubygem-jekyll-email-protect-doc Size:233.36 KiB Package: rubygem-jekyll-git-authors-0.2.1-1.fc30 Summary: Jekyll plugin that adds git authors into your page RPMs:rubygem-jekyll-git-authors rubygem-jekyll-git-authors-doc Size:244.77 KiB Package: rust-dirs-1.0.3-1.fc30 Summary: Platform abstractions for common directories RPMs:rust-dirs-devel Size:20.74 KiB Package: twa-1.3.1-1.fc30 Summary: Tiny web auditor with strong opinions RPMs:twa Size:14.71 KiB Package: upm-1.7.0-2.fc30 Summary: A high level library for sensors and actuators RPMs:nodejs-upm python3-upm upm upm-devel Size:35.66 MiB = DROPPED PACKAGES = Package: PyQuante-1.6.5-12.fc29 Summary: Python Quantum Chemistry RPMs:PyQuante PyQuante-libint Size:5.81 MiB Package: PySBIG-0.04-21.fc28 Summary: PySBIG can read SBIG CCD files RPMs:PySBIG Size:141.42 KiB Package: PythonCard-0.8.2-21.fc29 Summary: PythonCard GUI construction toolkit RPMs:PythonCard Size:2.58 MiB Package: bugyou-0.2.2-6.fc29 Summary: Automatic Bug Reporting Tool RPMs:bugyou Size:27.53 KiB Package: bzr-fastimport-0.13.0-13.fc29 Summary: Bzr plugin for fast loading of data from other VCS tools RPMs:bzr-fastimport Size:138.18 KiB Package: bzrtools-2.6.0-10.fc28 Summary: Collection of utilities and plugins for Bazaar-NG RPMs:bzrtools Size:886.37 KiB Package: clusterPy-0.9.9-17.fc29 Summary: Library of spatially constrained clustering algorithms RPMs:clusterPy Size:132.59 KiB Package: ekmukta-fonts-1.2.2-8.fc29 Summary: A Unicode compliant mono-linear typeface RPMs:ekmukta-fonts Size:1.01 MiB Package: gitolite-2.3.1-18.fc29 Summary: Highly flexible server for git directory version tracker RPMs:gitolite Size:165.90 KiB Package: gmpy-1.17-14.fc29 Summary: A Python interface to the GNU Multiple Precision Arithmetic Library RPMs:gmpy Size:546.98 KiB Package: hgsubversion-1.8.7-2.fc27 Summary: Mercurial extension for working with Subversion repositories RPMs:hgsubversion Size:188.24 KiB Package: ixpdimm_sw-01.00.00.2422-4.fc29 Summary: API for development of IXPDIMM management utilities RPMs:invm-frameworks invm-frameworks-devel ixpdimm-cli ixpdimm-data ixpdimm-devel ixpdimm-monitor libixpdimm libixpdimm-cim libixpdimm-cli Size:4.00 MiB Package: pycryptopp-0.6.0.1206569328141510525648634803928199668821045408958-15.fc29 Summary: Python wrappers for the Crypto++ library RPMs:pycryptopp Size:1015.67 KiB Package: pygtkchart-0-0.15.gitg8a56364.fc29 Summary: A GTK chart widget written in Python RPMs:pygtkchart Size:1.26 MiB Package: pyip-0.7-17.fc29 Summary: Python assembling/disassembling of raw ip packets RPMs:pyip Size:35.93 KiB Package: pylibpcap-0.6.4-17.fc29 Summary: A Python module for libpcap RPMs:pylibpcap Size:224.01 KiB Package: python-HTMLgen-2.2.2-32.fc30 Summary: A class library for the generation of HTML documents RPMs:python2-htmlgen Size:336.09 KiB Package: python-ImcSdk-0.7.2-10.fc29 Summary: Python SDK for Cisco IMC RPMs:python2-ImcSdk Size:228.12 KiB Package: python-Lightbox-2.1-19.fc29 Summary: Lightbox photo display widget RPMs:python2-lightbox Size:176.78 KiB Package: python-PSI-0.3-0.19.b2.fc29 Summary: Shows real time system information in python RPMs:python2-psi Size:364.46 KiB Package: python-SocksiPy-1.00-18.fc29 Summary: A Python SOCKS module RPMs:python2-socksipy Size:19.28 KiB Package: python-TornadIO2-0.0.4-14.fc29 Summary: Socket.io server on top of Tornado framework RPMs:python2-tornadio2 Size:48.53 KiB
Re: proposal: drop optical media from release criteria
On Thu, 2018-09-20 at 22:35 -0400, Harold Dost wrote: > Is having this as a test criteria *that* burdensome? Yes, frankly. Not a lot of testers even keep a DVD-RW drive and media around any more. It takes like a half hour just to write all the media for testing, then another few hours to run complete installs from them all (since optical media are *slow*). If it's not burdensome, why does no-one except the paid RH folks ever seem to run the test? And usually at the last minute, at that? I've had to buy three DVD-RW drives *solely for the purpose of being able to test this* (they keep dying, the things aren't terribly reliable). And I keep a spindle of media around, again, solely for the purpose of testing this, I don't use them for anything else. (In fact I've nearly run out, so if we keep this criteria, I'm gonna have to go out and blow some money on some more media I won't ever use for anything but testing this). If people outside of the RH team ever actually ran this test, I'd be more in favour of keeping it, but I don't think any of the people speaking up about how vital this is to them have ever actually chipped in and run the test before. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Nvidia and Fedora current state
On Fri, 21 Sep 2018 17:33:11 +0200, Michael Schwendt wrote: > A few days later, and GNOME Shell is hardly usable anymore. > Mouse lag, stuttering, wiindow usage taking seconds, > itt gets slower and slower. Just watch these typos > as a result of trying to compose this email. Spontaneous > key repetition because of major lag. > > F29 Rebooted a few times, and suddently the symptoms are gone again. It's like something doesn't initialize correctly when it happens. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Nvidia and Fedora current state
A few days later, and GNOME Shell is hardly usable anymore. Mouse lag, stuttering, wiindow usage taking seconds, itt gets slower and slower. Just watch these typos as a result of trying to compose this email. Spontaneous key repetition because of major lag. F29 ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: F29-beta - Policykit Agent error VNC access to Xfce DE
On 9/21/18 11:02 AM, Ed Greshko wrote: On 9/21/18 9:14 PM, Robert Moskowitz wrote: I have had this problem pre beta images. This is the F29-armfhp code base. I am running vnc server as a service. I have edited the xstartup to have: # exec /etc/X11/xinit/xinitrc exec /bin/sh /etc/xdg/xfce4/xinitrc xrdb $HOME/.Xresources startxfce4 & Note that currently, the is no .Xresources file. I do not know why you're doing that. But, I haven't. When I connect to the system after a fresh boot or vncserver restart I get a dialog with: Error XFCE PolicyKit Agent Ed Greshko reported on the Fedora list (as I thought this was a more general VNC/Xfce error having nothing to do with the beta) that he does not get this error, but he is NOT running vncserver as a service. Rather from an SSH session. I have configured by f28 system to run vncsever as a service and I see the error you're reporting. I believe I understand why the error is presented. If you start the vncserver you'll see something like this polkitd 706 1 0 22:31 ? 00:00:02 /usr/lib/polkit-1/polkitd --no-debug egreshko 3527 3497 2 22:58 ? 00:00:00 /usr/libexec/xfce-polkit running When you make a vnc client connection, you get the error and then you'll see only polkitd 706 1 0 22:31 ? 00:00:03 /usr/lib/polkit-1/polkitd --no-debug running. /usr/libexec/xfce-polkit has crashed. Why? I have no idea at 23:00. My F28 install is right now doing its dnf update which will take a bit. But I was setting what starts at startup via Settings > Session and Startup And I noticed that polkit is started there. I bet if you turn that off, things MAY get better. Of course then console login will not have polkit. So perhaps vncserver should NOT be running polkit? ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On Fri, Sep 21, 2018 at 8:33 AM Kamil Paral wrote: > > On Fri, Sep 21, 2018 at 6:17 AM Chris Murphy wrote: >> >> On Thu, Sep 20, 2018 at 8:36 PM Harold Dost wrote: >> > >> > Is having this as a test criteria *that* burdensome? Similar to another >> > blocker that was being proposed, maybe it's not something that _must_ be >> > tested, but if it's known to be broken that it should block a final. Maybe >> > I'm missing something, but unless the image is over the capacity of a DVD, >> > what would prevent the success of an installation? >> >> We did have a bug a couple years ago or so, where the ISO written to >> USB booted fine, but when burned to optical media wouldn't boot >> anything including VM. It was a bootloader bug, if I recall correctly >> - pretty sure it hit BIOS firmware only, not UEFI. >> >> But yeah it does sound reasonable to have the same "if it's known to >> be broken" then block, similar to the request for printing. > > > There is one difference. Those criteria that we block on yet don't test (at > all or in full extent) in the QA team are usually those that are too > impractical to test centrally. Ensuring that all important printer drivers > work falls into that category, similarly to ensuring all important graphics > cards work, etc. There's no way without community involvement we could ever > cover everything important. > > Optical booting is a different story, that can be tested, and quite easily > (making sure it works on one system usually means it works everywhere - > although there have been exceptions to the rule in the past), it just takes > annoyingly long. And unlike broken printers or to a certain extent broken > graphical drivers, we can't fix this with an update, we'd have to create a > new compose (and make another full round of testing), which we never do. So > although I'd love to get rid of optical media testing, if we keep it in the > criteria, I'm not comfortable with ignoring it inside the QA team and I > believe the test coverage for it would still need to be considered mandatory > in that case. > > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org +1 ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: F29-beta - Policykit Agent error VNC access to Xfce DE
On 9/21/18 9:14 PM, Robert Moskowitz wrote: > I have had this problem pre beta images. This is the F29-armfhp code base. > > I am running vnc server as a service. I have edited the xstartup to have: > > # exec /etc/X11/xinit/xinitrc > exec /bin/sh /etc/xdg/xfce4/xinitrc > xrdb $HOME/.Xresources > startxfce4 & > > Note that currently, the is no .Xresources file. I do not know why you're doing that. But, I haven't. > > When I connect to the system after a fresh boot or vncserver restart I get a > dialog > with: > > Error XFCE PolicyKit Agent > > Ed Greshko reported on the Fedora list (as I thought this was a more general > VNC/Xfce error having nothing to do with the beta) that he does not get this > error, > but he is NOT running vncserver as a service. Rather from an SSH session. I have configured by f28 system to run vncsever as a service and I see the error you're reporting. I believe I understand why the error is presented. If you start the vncserver you'll see something like this polkitd 706 1 0 22:31 ? 00:00:02 /usr/lib/polkit-1/polkitd --no-debug egreshko 3527 3497 2 22:58 ? 00:00:00 /usr/libexec/xfce-polkit running When you make a vnc client connection, you get the error and then you'll see only polkitd 706 1 0 22:31 ? 00:00:03 /usr/lib/polkit-1/polkitd --no-debug running. /usr/libexec/xfce-polkit has crashed. Why? I have no idea at 23:00. -- Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell them, then tell them what you told them." signature.asc Description: OpenPGP digital signature ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
F29-armfhp-Xfce-beta so slow compared to F28-armfhp-Xfce
We had a thread earlier about how slow the DE is in the F29 beta and how the an SELinux update made it 'better'. It did, but... I am building a F28-armfhp image for my Cubieboard2. And WOW is it peppier than F29. Initial Setup: On F29, the mouse is jumpy and when I finally can get to click on add root password, the Setup screen rolls up like a shade to reveal the password screen. Same with setting up a user account. On F28, quick mouse response and I really don't see the shift to reveal the password or user account screens. The change is that fast. Also the initial loading of the DE is much faster on F28 than F29. And logging into the actual session and getting the initial workspace setup. Plus the mouse remains jumpy on F29, but not at all on F28. This is all on the same Cubieboard2. Worst. In my F29 testing, I have the image on a HD (Cubies have a native sata interface) and the F28 testing is all on a uSD. One difference I can note on the images is that F28 has a swap partition whereas F29 does not. But that F28 swap is on the uSD. Once I got F29 configured for vncserver, the vnc to Xfce DE has good performance. I consider the F29-armhfp Xfce DE performance bad to unacceptable. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: F29-beta - Policykit Agent error VNC access to Xfce DE
More issues think are related to this: I cannot mount a USB drive. I cannot unlock Printer Settings to setup a printer. So maybe eventhough task 934 is polkit, something is not running right? On 9/21/18 9:14 AM, Robert Moskowitz wrote: I have had this problem pre beta images. This is the F29-armfhp code base. I am running vnc server as a service. I have edited the xstartup to have: # exec /etc/X11/xinit/xinitrc exec /bin/sh /etc/xdg/xfce4/xinitrc xrdb $HOME/.Xresources startxfce4 & Note that currently, the is no .Xresources file. When I connect to the system after a fresh boot or vncserver restart I get a dialog with: Error XFCE PolicyKit Agent Ed Greshko reported on the Fedora list (as I thought this was a more general VNC/Xfce error having nothing to do with the beta) that he does not get this error, but he is NOT running vncserver as a service. Rather from an SSH session. See below service status that 934 is the plokit. Perhaps the login is trying to run a second copy? What might be causing this condition? I am going to build a F28 system and see what it does... # systemctl -l --no-pager status vncserver@:1 ● vncserver@:1.service - Remote desktop service (VNC) Loaded: loaded (/etc/systemd/system/vncserver@:1.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2018-06-22 11:12:56 EDT; 2 months 30 days ago Process: 707 ExecStart=/usr/bin/vncserver -autokill :1 (code=exited, status=0/SUCCESS) Process: 670 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill :1 > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS) Main PID: 728 (Xvnc) Tasks: 119 (limit: 4315) Memory: 200.2M CGroup: /system.slice/system-vncserver.slice/vncserver@:1.service ├─ 728 /usr/bin/Xvnc :1 -auth /home/rgm/.Xauthority -desktop localhost:1 (rgm) -fp catalogue:/etc/X11/fontpath.d -geometry 1024x768 -pn -rfbauth /home/rgm/.vnc/passwd -rfbport 5901 -rfbwait 3 ├─ 744 sh -c (/home/rgm/.vnc/xstartup; /usr/bin/vncserver -kill :1) >> '/home/rgm/.vnc/localhost:1.log' 2>&1 & ├─ 745 /bin/sh /etc/xdg/xfce4/xinitrc ├─ 756 xfce4-session ├─ 763 /usr/bin/dbus-launch --sh-syntax --exit-with-session xfce4-session ├─ 783 /usr/bin/dbus-daemon --syslog --fork --print-pid 6 --print-address 8 --session ├─ 841 /usr/libexec/at-spi-bus-launcher ├─ 855 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 ├─ 859 /usr/libexec/at-spi2-registryd --use-gnome-session ├─ 862 /usr/lib/xfce4/xfconf/xfconfd ├─ 883 /usr/bin/ssh-agent -s ├─ 889 /usr/bin/gpg-agent --sh --daemon --write-env-file /home/rgm/.cache/gpg-agent-info ├─ 895 xfwm4 ├─ 903 xfce4-panel ├─ 906 Thunar --daemon ├─ 910 xfdesktop ├─ 916 /usr/bin/python3 /usr/bin/seapplet ├─ 921 xscreensaver -no-splash ├─ 923 /usr/libexec/geoclue-2.0/demos/agent ├─ 925 nm-applet ├─ 934 /usr/libexec/xfce-polkit ├─ 935 xfsettingsd ├─ 943 xfce4-power-manager ├─ 960 abrt-applet ├─ 965 /usr/libexec/gvfsd ├─ 980 /usr/libexec/imsettings-daemon ├─ 982 /usr/lib/xfce4/notifyd/xfce4-notifyd ├─1058 /usr/bin/pulseaudio --start ├─1202 /usr/bin/ibus-daemon -r --xim ├─1205 /usr/libexec/dconf-service ├─1231 /usr/libexec/ibus-dconf ├─1235 /usr/libexec/ibus-ui-gtk3 ├─1238 /usr/libexec/ibus-extension-gtk3 ├─1244 /usr/libexec/ibus-x11 --kill-daemon ├─1250 /usr/libexec/ibus-portal ├─1323 /usr/libexec/ibus-engine-simple ├─1326 /usr/lib/xfce4/panel/wrapper-2.0 /usr/lib/xfce4/panel/plugins/libsystray.so 6 14680072 systray Notification Area Area where notification icons appear ├─1328 /usr/lib/xfce4/panel/wrapper-2.0 /usr/lib/xfce4/panel/plugins/libactions.so 2 14680073 actions Action Buttons Log out, lock or other system actions ├─1379 /usr/libexec/gvfs-udisks2-volume-monitor ├─1421 /usr/libexec/gvfs-mtp-volume-monitor ├─1436 /usr/libexec/gvfsd-trash --spawner :1.12 /org/gtk/gvfs/exec_spaw/0 └─1443 /usr/libexec/gvfsd-metadata Sep 21 08:32:35 localhost org.freedesktop.thumbnails.Thumbnailer1[783]: Registered thumbailer gsf-office-thumbnailer -i %i -o %o -s %s Sep 21 08:32:35 localhost org.freedesktop.thumbnails.Thumbnailer1[783]: Registered thumbailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o Sep 21 08:32:35 localhost org.freedesktop.thumbnails.Thumbnailer1[783]: Registered thumbailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o Sep 21 08:32:35 localhost dbus-daemon[783]: [session uid=1000 pid=762] Activating service name='org.gtk.vfs.UDisks2VolumeMonitor' requested by ':1.31' (uid=1000 pid=1366 comm="/usr/lib/tumbler-1/tumblerd "
Java 8,10,11 Test Day 2018-09-26
Hey All, Many of you might have been using Java in one form other. Java folks and Fedora QA is hosting a Java Test Day later this week. We want you to test the different versions of Java and test if your application and your general system is working as expected. This instalment of Fedora Test Day will focus on OpenJDK 11 and OpenJDK 10. Currently we have java-1.8.0-openjdk as main JDK in Fedora. It accompanied java-1.7.0-openjdk as JRE for a year, and replaced it in buildroot in F21 All the information is on the wiki[1] for more information. Please test and submit your reports! [1]https://fedoraproject.org/wiki/Test_Day:2018-09-26:java_8,_10_and_11_testday Thanks //sumantro ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
[Test-Announce] Java 8,10,11 Test Day 2018-09-26
Hey All, Many of you might have been using Java in one form other. Java folks and Fedora QA is hosting a Java Test Day later this week. We want you to test the different versions of Java and test if your application and your general system is working as expected. This instalment of Fedora Test Day will focus on OpenJDK 11 and OpenJDK 10. Currently we have java-1.8.0-openjdk as main JDK in Fedora. It accompanied java-1.7.0-openjdk as JRE for a year, and replaced it in buildroot in F21 All the information is on the wiki[1] for more information. Please test and submit your reports! [1]https://fedoraproject.org/wiki/Test_Day:2018-09-26:java_8,_10_and_11_testday Thanks //sumantro ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org
F29-beta - Policykit Agent error VNC access to Xfce DE
I have had this problem pre beta images. This is the F29-armfhp code base. I am running vnc server as a service. I have edited the xstartup to have: # exec /etc/X11/xinit/xinitrc exec /bin/sh /etc/xdg/xfce4/xinitrc xrdb $HOME/.Xresources startxfce4 & Note that currently, the is no .Xresources file. When I connect to the system after a fresh boot or vncserver restart I get a dialog with: Error XFCE PolicyKit Agent Ed Greshko reported on the Fedora list (as I thought this was a more general VNC/Xfce error having nothing to do with the beta) that he does not get this error, but he is NOT running vncserver as a service. Rather from an SSH session. See below service status that 934 is the plokit. Perhaps the login is trying to run a second copy? What might be causing this condition? I am going to build a F28 system and see what it does... # systemctl -l --no-pager status vncserver@:1 ● vncserver@:1.service - Remote desktop service (VNC) Loaded: loaded (/etc/systemd/system/vncserver@:1.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2018-06-22 11:12:56 EDT; 2 months 30 days ago Process: 707 ExecStart=/usr/bin/vncserver -autokill :1 (code=exited, status=0/SUCCESS) Process: 670 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill :1 > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS) Main PID: 728 (Xvnc) Tasks: 119 (limit: 4315) Memory: 200.2M CGroup: /system.slice/system-vncserver.slice/vncserver@:1.service ├─ 728 /usr/bin/Xvnc :1 -auth /home/rgm/.Xauthority -desktop localhost:1 (rgm) -fp catalogue:/etc/X11/fontpath.d -geometry 1024x768 -pn -rfbauth /home/rgm/.vnc/passwd -rfbport 5901 -rfbwait 3 ├─ 744 sh -c (/home/rgm/.vnc/xstartup; /usr/bin/vncserver -kill :1) >> '/home/rgm/.vnc/localhost:1.log' 2>&1 & ├─ 745 /bin/sh /etc/xdg/xfce4/xinitrc ├─ 756 xfce4-session ├─ 763 /usr/bin/dbus-launch --sh-syntax --exit-with-session xfce4-session ├─ 783 /usr/bin/dbus-daemon --syslog --fork --print-pid 6 --print-address 8 --session ├─ 841 /usr/libexec/at-spi-bus-launcher ├─ 855 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 ├─ 859 /usr/libexec/at-spi2-registryd --use-gnome-session ├─ 862 /usr/lib/xfce4/xfconf/xfconfd ├─ 883 /usr/bin/ssh-agent -s ├─ 889 /usr/bin/gpg-agent --sh --daemon --write-env-file /home/rgm/.cache/gpg-agent-info ├─ 895 xfwm4 ├─ 903 xfce4-panel ├─ 906 Thunar --daemon ├─ 910 xfdesktop ├─ 916 /usr/bin/python3 /usr/bin/seapplet ├─ 921 xscreensaver -no-splash ├─ 923 /usr/libexec/geoclue-2.0/demos/agent ├─ 925 nm-applet ├─ 934 /usr/libexec/xfce-polkit ├─ 935 xfsettingsd ├─ 943 xfce4-power-manager ├─ 960 abrt-applet ├─ 965 /usr/libexec/gvfsd ├─ 980 /usr/libexec/imsettings-daemon ├─ 982 /usr/lib/xfce4/notifyd/xfce4-notifyd ├─1058 /usr/bin/pulseaudio --start ├─1202 /usr/bin/ibus-daemon -r --xim ├─1205 /usr/libexec/dconf-service ├─1231 /usr/libexec/ibus-dconf ├─1235 /usr/libexec/ibus-ui-gtk3 ├─1238 /usr/libexec/ibus-extension-gtk3 ├─1244 /usr/libexec/ibus-x11 --kill-daemon ├─1250 /usr/libexec/ibus-portal ├─1323 /usr/libexec/ibus-engine-simple ├─1326 /usr/lib/xfce4/panel/wrapper-2.0 /usr/lib/xfce4/panel/plugins/libsystray.so 6 14680072 systray Notification Area Area where notification icons appear ├─1328 /usr/lib/xfce4/panel/wrapper-2.0 /usr/lib/xfce4/panel/plugins/libactions.so 2 14680073 actions Action Buttons Log out, lock or other system actions ├─1379 /usr/libexec/gvfs-udisks2-volume-monitor ├─1421 /usr/libexec/gvfs-mtp-volume-monitor ├─1436 /usr/libexec/gvfsd-trash --spawner :1.12 /org/gtk/gvfs/exec_spaw/0 └─1443 /usr/libexec/gvfsd-metadata Sep 21 08:32:35 localhost org.freedesktop.thumbnails.Thumbnailer1[783]: Registered thumbailer gsf-office-thumbnailer -i %i -o %o -s %s Sep 21 08:32:35 localhost org.freedesktop.thumbnails.Thumbnailer1[783]: Registered thumbailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o Sep 21 08:32:35 localhost org.freedesktop.thumbnails.Thumbnailer1[783]: Registered thumbailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o Sep 21 08:32:35 localhost dbus-daemon[783]: [session uid=1000 pid=762] Activating service name='org.gtk.vfs.UDisks2VolumeMonitor' requested by ':1.31' (uid=1000 pid=1366 comm="/usr/lib/tumbler-1/tumblerd " label="system_u:system_r:unconfined_service_t:s0") Sep 21 08:32:38 localhost dbus-daemon[783]: [session uid=1000 pid=762] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor' Sep 21 08:32:39 localhost dbus-daemon[783]: [session
F29 Beta 1.5 problem
Yesterday afternoon (9/20), I did a clean install of F29 Beta 1.5 onto bare metal via DVD. The PC is a Lenovo M59P with an E8400 processor. The ISO had been check-summed and passed. The PC booted fine and the media test ran and passed. Anaconda ran perfectly and the install completed normally. I did a restart, logged in, and allowed the lock to time out. The fan on this system rarely runs at all, but in a few hours of sitting idle the fan came on. I logged in and started the system monitor and noted the both core0 and core1 were trading off running at 100%. The trade cycle was running between 20 and 30 seconds. Sometimes they would both run at 50% for a few seconds. When I looked at the processes, gnome-software was the problem. I let the lock time out and left the system overnight. This morning (9/21) the fan was running full speed and both core0 and core1 was stuck hard at 100%. Again gnome-software was the problem. I wanted to see if anything else would run so I started Rhythm box. There were delays getting it going, but it did start and worked (radio stream) with no apparent gaps in the audio. When I checked the Resources and processes, apparently gnome-software was sharing with Rhythm Box, but only what Rhythm Box needed. When I closed Rhythm Box, gnome-software went back to taking 90+% of the core0 and core1 cycles. I just did a restart and the system returned to normal (fan not running). This time I'm not going to login. I'm just going to let it sit and see what happens. This is the same problem I found a few days ago with B 1.3 I wrote about it then, but it was a day later, after a reminder that I wrote and called out gnome-software. Have a Great Day! Pat ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On Fri, Sep 21, 2018 at 6:17 AM Chris Murphy wrote: > On Thu, Sep 20, 2018 at 8:36 PM Harold Dost wrote: > > > > Is having this as a test criteria *that* burdensome? Similar to another > blocker that was being proposed, maybe it's not something that _must_ be > tested, but if it's known to be broken that it should block a final. Maybe > I'm missing something, but unless the image is over the capacity of a DVD, > what would prevent the success of an installation? > > We did have a bug a couple years ago or so, where the ISO written to > USB booted fine, but when burned to optical media wouldn't boot > anything including VM. It was a bootloader bug, if I recall correctly > - pretty sure it hit BIOS firmware only, not UEFI. > > But yeah it does sound reasonable to have the same "if it's known to > be broken" then block, similar to the request for printing. There is one difference. Those criteria that we block on yet don't test (at all or in full extent) in the QA team are usually those that are too impractical to test centrally. Ensuring that all important printer drivers work falls into that category, similarly to ensuring all important graphics cards work, etc. There's no way without community involvement we could ever cover everything important. Optical booting is a different story, that can be tested, and quite easily (making sure it works on one system usually means it works everywhere - although there have been exceptions to the rule in the past), it just takes annoyingly long. And unlike broken printers or to a certain extent broken graphical drivers, we can't fix this with an update, we'd have to create a new compose (and make another full round of testing), which we never do. So although I'd love to get rid of optical media testing, if we keep it in the criteria, I'm not comfortable with ignoring it inside the QA team and I believe the test coverage for it would still need to be considered mandatory in that case. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On Thu, Sep 20, 2018 at 8:17 PM Matthew Miller wrote: > On Thu, Sep 20, 2018 at 01:49:20PM -0400, Matthew Miller wrote: > > Justification: > http://newsthump.com/2018/05/21/man-decides-to-keep-box-of-cables-hes-has-since-2002-for-another-year/ > > More seriously: I don't think there are any systems in the audiences > targeted by our release-blocking deliverables which are not better served > by > booting from USB media. > Speaking for I believe most of the QA team: "We'd be happy to". Testing optical boot is a major PITA. The decision is not ours, though, but I assume it belongs to the groups owning the media currently blocking optical boot. Which is Spins SIG for Everything netinst and Workstation WG for Workstation Live [1] (to be clear, nothing else is currently covered by that criterion, just those two images). One more thing, Matthew, are you proposing we drop this for F30, or immediately for F29? [1] https://fedoraproject.org/wiki/Releases/29/ReleaseBlocking ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Introduction
Hi, My name is Ludovic. Paul-Muadib on freenode. I've been using OSS since 2000ish. I'm emplyed by mozilla as root , before that I was the QA lead for Thunderbird and for Joost a video startup company. I've used linux on and off since 1996 (kernel 1.3.88) with slackware/Debian/RHEL/CentOS - I've also played with things like Tru64, HP-UX and friends. I'm joigning the QA list, cause I like running the kernel-test and the wiki needs some edits (like using pyhton3-fedora). I don't have much free time but I have interest in non x86 hardware, 28mm platisc soldier and photography. I usually sign my emails (but have not setup this adrees back on a proper email client since I've reinstalled my machine. Ludo -- https://www.hirlimann.net/Ludovic/carnet/ ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
