Re: F29 Xfce ibus systray widget?
On 9/28/18 11:26 AM, Robert Moskowitz wrote: > Maybe this is only in the armhfp build, but I have a 'new' widget on my > systray. > About says it is for ibus. > > What is this? Why was it added as a default item with F29. I do not have it > on my > F28 x86_64 notebook. ibus stands for Intelligent Input Bus. A method for multilingual input. We use in on our systems to input Chinese, Japanese, and Korean. Not sure why it would be enabled on your system. On my F29 system it was not enabled by default. To deselect it, you can go to your menu under Applications--->Settings--->Input Method Selector and pick "none" -- 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 Xfce ibus systray widget?
Maybe this is only in the armhfp build, but I have a 'new' widget on my systray. About says it is for ibus. What is this? Why was it added as a default item with F29. I do not have it on my F28 x86_64 notebook. thanks ___ 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 beta printing to HP8600 works
We had a thread on printing testing recently. I just installed my HP8600 (all-in-one inkjet), accessed via port 9100, on my F29 setup. It seems to be working. No problems with the little testing I did. ___ 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: How do I find out what was changed in tigervnc-server-1.9.0-3.fc29
On 9/27/18 2:55 PM, Adam Williamson wrote: On Thu, 2018-09-27 at 11:11 -0400, Robert Moskowitz wrote: I want to know if my polkit problem has been fixed without having to do all the changes to test this... You can look in Koji. Go to https://koji.fedoraproject.org/ , then type 'tigervnc*' in the search box, you'll get to: https://koji.fedoraproject.org/koji/packageinfo?packageID=7868 Where you can see the 1.9.0-3.fc29 build. Click on it, and you should get to: https://koji.fedoraproject.org/koji/buildinfo?buildID=1147505 scroll down a bit on that page and you'll find the changelog: * Tue Sep 25 2018 Jan Grulich - 1.9.0-3 - Do not crash passwd when using malloc perturb checks Resolves: bz#1631483 I will make a note of this for future cases. Meanwhile back to writing a bug report on vncserver. ___ 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: How do I find out what was changed in tigervnc-server-1.9.0-3.fc29
On Thu, 2018-09-27 at 11:11 -0400, Robert Moskowitz wrote: > I want to know if my polkit problem has been fixed without having to do > all the changes to test this... You can look in Koji. Go to https://koji.fedoraproject.org/ , then type 'tigervnc*' in the search box, you'll get to: https://koji.fedoraproject.org/koji/packageinfo?packageID=7868 Where you can see the 1.9.0-3.fc29 build. Click on it, and you should get to: https://koji.fedoraproject.org/koji/buildinfo?buildID=1147505 scroll down a bit on that page and you'll find the changelog: * Tue Sep 25 2018 Jan Grulich - 1.9.0-3 - Do not crash passwd when using malloc perturb checks Resolves: bz#1631483 -- 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: F29 / Rawhide - Bogus ssh host key mismatch errors mentioning "rsa-sha2-256"
On Thu, 2018-09-27 at 11:18 -0400, Robert Moskowitz wrote: > > On 9/25/18 1:27 AM, Adam Williamson wrote: > > Hey folks! Just a heads up, if anyone on F29 or Rawhide finds that > > suddenly ssh connections are failing, claiming the host key does not > > match and asking for a 'rsa-sha2-256' key: a mysterious hero known only > > as 'sedrubal' figured out that this is caused by a crypto-policies > > update, this one - > > > > https://bodhi.fedoraproject.org/updates/FEDORA-2018-854e0caf7b > > > > you can get back to normal by downgrading back to this build: > > > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1133273 > > > > (for both F29 and Rawhide). We've got enough negative karma on the > > update now that it should be removed from updates-testing on the next > > push, but some folks will have got the update already. I'll ask tmraz > > if he can either fix it promptly or revert it temporarily, for Rawhide > > users. > > > > Sorry for the trouble! > > You mean like this I am getting in my ssh started vncserver that I > worked so hard on yesterday? > > # 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: exit-code) since Fri 2018-06-22 11:12:54 > EDT; 3 months 5 days ago >Process: 682 ExecStart=/bin/sh -c /usr/bin/ssh -i .ssh/id_rsa_vnchack > localhost /usr/bin/vncserver -fg :1 (code=exited, status=255) >Process: 655 ExecStartPre=/bin/sh -c /usr/bin/ssh -i > .ssh/id_rsa_vnchack localhost /usr/bin/vncserver -kill :1 > /dev/null > 2>&1 || : (code=exited, status=0/SUCCESS) > Main PID: 682 (code=exited, status=255) > > Jun 22 11:12:54 localhost sh[682]: It is also possible that a host key > has just been changed. > Jun 22 11:12:54 localhost sh[682]: The fingerprint for the RSA key sent > by the remote host is > Jun 22 11:12:54 localhost sh[682]: > SHA256:bxBBsme1XjvFo5g25XfSRhUMbk7JVl9Bdp8zp7vPTHs. > Jun 22 11:12:54 localhost sh[682]: Please contact your system administrator. > Jun 22 11:12:54 localhost sh[682]: Add correct host key in > /home/rgm/.ssh/known_hosts to get rid of this message. > Jun 22 11:12:54 localhost sh[682]: Offending ECDSA key in > /home/rgm/.ssh/known_hosts:1 > Jun 22 11:12:54 localhost sh[682]: RSA host key for localhost has > changed and you have requested strict checking. > Jun 22 11:12:54 localhost sh[682]: Host key verification failed. > Jun 22 11:12:54 localhost systemd[1]: vncserver@:1.service: Main process > exited, code=exited, status=255/n/a > Jun 22 11:12:54 localhost systemd[1]: vncserver@:1.service: Failed with > result 'exit-code'. Yup, looks like the same problem. > I see I upgraded openssh yesterday evening: > > Upgraded: openssh-7.8p1-1.fc29.armv7hl > > And now I got: openssh-server-7.8p1-3.fc29.armv7hl > > and I could start vncserver via ssh. It would actually be an update to crypto-policies that fixed it, not openssh. > thanks for identifying the problem and getting it fixed so promptly. Thanks, but I can't take the credit: that goes to sedrubal (who first pointed it out in the update) and mcatanzaro (who pinged me about it) :) -- 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: F29 / Rawhide - Bogus ssh host key mismatch errors mentioning "rsa-sha2-256"
On Thu, Sep 27, 2018 at 10:23 AM Adam Williamson wrote: > > Hey folks! Just a heads up, if anyone on F29 or Rawhide finds that > suddenly ssh connections are failing, claiming the host key does not > match and asking for a 'rsa-sha2-256' key: a mysterious hero known only > as 'sedrubal' figured out that this is caused by a crypto-policies > update, this one - > > https://bodhi.fedoraproject.org/updates/FEDORA-2018-854e0caf7b > > you can get back to normal by downgrading back to this build: > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1133273 > > (for both F29 and Rawhide). We've got enough negative karma on the > update now that it should be removed from updates-testing on the next > push, but some folks will have got the update already. I'll ask tmraz > if he can either fix it promptly or revert it temporarily, for Rawhide > users. > Alternately, pull the fixed version from https://bodhi.fedoraproject.org/updates/FEDORA-2018-95580e520c which is headed for stable on the next push. ___ 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: Add release announcement post to Go/No-Go criteria
On Tue, Sep 25, 2018 at 4:35 PM Ben Cotton wrote: > With today's Beta release, the release announcement post for Fedora > Magazine was not ready. As a result, the announcement went out a > little late and then only due to a drop-everything effort (thanks, > stickster!). We have a proposal to add a fourth criterion for the > Go/No-Go decision, beginning with F29 Final: > > 4. The release announcement post for Fedora Magazine is substantially > complete > I dont think its a good idea, for the reasons Kevin has mentioned. Also, if the article is not ready and thats the only criteria that is not satisfied, we will just punt the decision to Friday (which happened before) since no one likes to block the release on it. I guess we can just consider as a soft criteria and if its not ready, we will just ask people to help marketing team and get the article ready by Friday or Monday. > > As a reminder, these are the existing criteria: > > 1. No remaining blocker bugs > 2. Release candidate compose is available > 3. Test matrices for [milestone = Alpha, Beta, Final] are fully completed > > -- > Ben Cotton > Fedora Program Manager > TZ=America/Indiana/Indianapolis > ___ > devel mailing list -- de...@lists.fedoraproject.org > To unsubscribe send an email to devel-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/de...@lists.fedoraproject.org > ___ 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: Add release announcement post to Go/No-Go criteria
On Tue, Sep 25, 2018 at 04:29:51PM -0700, Adam Williamson wrote: > The readiness meeting is only run *once* - if we slip at the first > go/no-go, we don't run another readiness meeting after the second one. > (I don't know why that is, though.) Huh. That seems like maybe the problem. Readiness state can change in either direction for most of the things we need ready. -- 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: F29 / Rawhide - Bogus ssh host key mismatch errors mentioning "rsa-sha2-256"
On 9/25/18 1:27 AM, Adam Williamson wrote: Hey folks! Just a heads up, if anyone on F29 or Rawhide finds that suddenly ssh connections are failing, claiming the host key does not match and asking for a 'rsa-sha2-256' key: a mysterious hero known only as 'sedrubal' figured out that this is caused by a crypto-policies update, this one - https://bodhi.fedoraproject.org/updates/FEDORA-2018-854e0caf7b you can get back to normal by downgrading back to this build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1133273 (for both F29 and Rawhide). We've got enough negative karma on the update now that it should be removed from updates-testing on the next push, but some folks will have got the update already. I'll ask tmraz if he can either fix it promptly or revert it temporarily, for Rawhide users. Sorry for the trouble! You mean like this I am getting in my ssh started vncserver that I worked so hard on yesterday? # 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: exit-code) since Fri 2018-06-22 11:12:54 EDT; 3 months 5 days ago Process: 682 ExecStart=/bin/sh -c /usr/bin/ssh -i .ssh/id_rsa_vnchack localhost /usr/bin/vncserver -fg :1 (code=exited, status=255) Process: 655 ExecStartPre=/bin/sh -c /usr/bin/ssh -i .ssh/id_rsa_vnchack localhost /usr/bin/vncserver -kill :1 > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS) Main PID: 682 (code=exited, status=255) Jun 22 11:12:54 localhost sh[682]: It is also possible that a host key has just been changed. Jun 22 11:12:54 localhost sh[682]: The fingerprint for the RSA key sent by the remote host is Jun 22 11:12:54 localhost sh[682]: SHA256:bxBBsme1XjvFo5g25XfSRhUMbk7JVl9Bdp8zp7vPTHs. Jun 22 11:12:54 localhost sh[682]: Please contact your system administrator. Jun 22 11:12:54 localhost sh[682]: Add correct host key in /home/rgm/.ssh/known_hosts to get rid of this message. Jun 22 11:12:54 localhost sh[682]: Offending ECDSA key in /home/rgm/.ssh/known_hosts:1 Jun 22 11:12:54 localhost sh[682]: RSA host key for localhost has changed and you have requested strict checking. Jun 22 11:12:54 localhost sh[682]: Host key verification failed. Jun 22 11:12:54 localhost systemd[1]: vncserver@:1.service: Main process exited, code=exited, status=255/n/a Jun 22 11:12:54 localhost systemd[1]: vncserver@:1.service: Failed with result 'exit-code'. I see I upgraded openssh yesterday evening: Upgraded: openssh-7.8p1-1.fc29.armv7hl And now I got: openssh-server-7.8p1-3.fc29.armv7hl and I could start vncserver via ssh. thanks for identifying the problem and getting it fixed so promptly. ___ 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
How do I find out what was changed in tigervnc-server-1.9.0-3.fc29
I want to know if my polkit problem has been fixed without having to do all the changes to test this... thanks ___ 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 Gnome Install process - A pain
A hostname field would be nice, I don't have issues setting one after the fact though. Github: https://github.com/Sadin | Pagure: https://pagure.io/user/sadin | Twitter: https://twitter.com/sadinzs | Mastodon: https://mastodon.social/@sadinzs On Thu, Sep 27, 2018 at 11:01 AM Stephen Gallagher wrote: > On Sat, Sep 22, 2018 at 9:41 PM Ed Greshko wrote: > > > > This will probably be considered a "minor" pain. And, since I don't use > GNOME except > > in a VM for testing, I guess it is. > > > > I'd just like to go on record to say I dislike a few things about the > install process. > > > > 1. There is no option to set the hostname during install. > > > > There is, but it's non-obvious. You have to set it in GNOME Settings > before running the installer. I've complained about this in the past > as well. > > > 2. User creation is delayed until first boot and at the time of > creation there is no > > option to specify the UID and GID. So, if you're like me, and use > existing > > NFS services and your primary user doesn't have 1000/1000 for them you > have to either > > know to create an initial throw away account or manually make changes > > later. > > Or use FreeIPA/Active Directory to manage users and enroll as a client > instead. This is generally a better idea than manually copying IDs > around every time you deploy a new machine. > ___ > 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 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 / Rawhide - Bogus ssh host key mismatch errors mentioning "rsa-sha2-256"
On Thu, Sep 27, 2018 at 9:22 AM Adam Williamson wrote: > Hey folks! Just a heads up, if anyone on F29 or Rawhide finds that > suddenly ssh connections are failing, claiming the host key does not > match and asking for a 'rsa-sha2-256' key: a mysterious hero known only > as 'sedrubal' figured out that this is caused by a crypto-policies > update, this one - > > https://bodhi.fedoraproject.org/updates/FEDORA-2018-854e0caf7b > > you can get back to normal by downgrading back to this build: > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1133273 > > (for both F29 and Rawhide). We've got enough negative karma on the > update now that it should be removed from updates-testing on the next > push, but some folks will have got the update already. I'll ask tmraz > if he can either fix it promptly or revert it temporarily, for Rawhide > users. > This may not be limited to F29... I noticed this on F28 several weeks ago and had to go in and remove entries from known_hosts... Thanks, Richard ___ 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
I am back for a few days... On 9/21/18 7:26 PM, Ed Greshko wrote: 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 That is a fairly nasty hack. 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. I guess it is time for a bug report. Though I seem to recall a comment about a lack of activity on maintaining tiger-vncserver... Perhaps it is time to look into the alternatives... ___ 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: Self-introduction: Julian Schlüntz
- Original Message -
> From: "Julian Schlüntz"
> To: test@lists.fedoraproject.org
> Sent: Thursday, July 12, 2018 1:16:51 AM
> Subject: Self-introduction: Julian Schlüntz
>
> Hello everyone,
>
> my name is Julian Schlüntz, I have been using Fedora for a long time (I
> think since Fedora Core 3) and it is time I started contributing. I like
> testing stuff and figuring out problems, so I figured QA would be the
> right place for me.
>
> I am from Germany, 31 years old and have some development experience.
> My IRC nickname is 'gapophustu'.
>
> Cheers
>
> ___
> 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/message/TD4X6OWRRG4PJ4GTYTZQFLRVBOJJXKPQ/
>
Hey Julian!
Welcome to Fedora QA, It will be great if you apply for qa FAS group. If you
have, I have sponsored you by now.
You can start off by testing updates in [http://bodhi.fedoraproject.org/] for
Fedora 27, Fedora 28, and Fedora 29. Update testing is where a tester tests a
package and gives out a +1 Karma for PASS and -1 Karma for FAIL. You can go to
bodhi.fedoraproject.org where you can sort the packages with Fedora Releases
and tags viz "pending" & "testing". You can read much about update testing here
[1]. You can also, use fedora-easy-karma for giving out feedbacks.
you can start with Release Validation testing. In Release Validation all you
need to do is to check the nightly/TC/RC against certain criteria. For example,
let's take the latest compose (Fedora 29 Branched 20180923), you can run test
cases which are mentioned [2] and submit your results in the test matrix.
Note that each of the test cases[3] will have "How to test" section which will
have the steps (to be executed sequentially) and if the results match with the
expected results you can mark it as pass by editing the wiki page
{{result|PASS|}} . Always make sure to check for "Associated
release criterion" which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.
You can always find the ‘current’ validation pages using these addresses:
https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test
For Automation, you can start looking at
Taskotron[https://fedoraproject.org/wiki/Taskotron]
and Open QA[https://fedoraproject.org/wiki/OpenQA].
https://fedoraproject.org/wiki/QA:Updates_Testing
https://fedoraproject.org/wiki/Test_Results:Fedora_29_Branched_20180923.n.0_Summary?rd=Test_Results:Current_Summary
https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
https://bugzilla.redhat.com/
Feel free to ping us on IRC if you need any help #fedora-qa@freenode.
We have test days coming happening now which is a nice place to start, please
stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day
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
Re: To join Fedora testing and quality assurance
Thanks a lot Sumantro Mukherjee, I will go through the resources you shared
and let you know.
On Wed 26 Sep, 2018, 2:25 PM Sumantro Mukherjee,
wrote:
>
>
> - Original Message -
> > From: "Abdul Rehman"
> > To: test@lists.fedoraproject.org
> > Sent: Wednesday, September 5, 2018 11:28:56 PM
> > Subject: To join Fedora testing and quality assurance
> >
> > Hi,
> > I am currently testing on Screen keyboard of Fedora using OpenQA and I
> found
> > a bug which I would like to discuss on the list. So request to join me in
> > the list.
> >
> > --
> > Regards,
> > Abdul Rehman Quadri
> >
> > ___
> > 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
> >
> Hey Abdul!
>
> Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
> you have, I have sponsored you by now.
>
> I think you already had a word with Adamw but here's something more you
> can look into, if you are looking to contribute to Fedora QA. :)
>
> You can start off by testing updates in [http://bodhi.fedoraproject.org/]
> for Fedora 27, Fedora 28, and Fedora 29. Update testing is where a tester
> tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL.
> You can go to bodhi.fedoraproject.org where you can sort the packages
> with Fedora Releases and tags viz "pending" & "testing". You can read much
> about update testing here [1]. You can also, use fedora-easy-karma for
> giving out feedbacks.
>
>
> you can start with Release Validation testing. In Release Validation all
> you need to do is to check the nightly/TC/RC against certain criteria. For
> example, let's take the latest compose (Fedora 29 Branched 20180923), you
> can run test cases which are mentioned [2] and submit your results in the
> test matrix.
>
> Note that each of the test cases[3] will have "How to test" section which
> will have the steps (to be executed sequentially) and if the results match
> with the expected results you can mark it as pass by editing the wiki page
> {{result|PASS|}} . Always make sure to check for "Associated
> release criterion" which can be found on the top of test case page, if your
> test case fails you can mark it fail by editing the wiki page
> {{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.
>
>
> You can always find the ‘current’ validation pages using these addresses:
>
> https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
> https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
> https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
> https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
> https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test
>
>
> For Automation, you can start looking at Taskotron[
> https://fedoraproject.org/wiki/Taskotron]
> and Open QA[https://fedoraproject.org/wiki/OpenQA].
>
>
>
> https://fedoraproject.org/wiki/QA:Updates_Testing
>
> https://fedoraproject.org/wiki/Test_Results:Fedora_29_Branched_20180923.n.0_Summary?rd=Test_Results:Current_Summary
> https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
> https://bugzilla.redhat.com/
>
> Feel free to ping us on IRC if you need any help #fedora-qa@freenode.
>
>
> We have test days coming happening now which is a nice place to start,
> please stay tuned to the @test list and help us testing!
> The current test day can be found on
> https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
> Test days schedule can be found on the fedocal
> https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day
>
> 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 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
Seems to be working - Re: F29-beta - Policykit Agent error VNC access to Xfce DE
It seems to be working... I kind of followed: https://forums.fedoraforum.org/showthread.php?316905-PolicyKit-failed-over-headless-VNC=1809280#post1809280 They don't give all the steps for setting up the ssh connection, but I figured out a working set of steps. Made my service file as they show and I am connected. I only had the password prompt from the vnc client. I inserted a USB drive and went to mount it. Polkit prompted me for my password (I am in group wheel), and after I provided it, the drive is mounted. Don't know what it might take if the user is not in wheel. Now on to other testing. And to write a bug report What a MESS! On 9/21/18 7:26 PM, Ed Greshko wrote: 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. ___ 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 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
Hello My name is Neda, I am 36 years old, and I am all new here! I live in Belgrade, the capitol of Serbia. I am also all new in QA, but I am very excited and eager to learn new things and to contribute to Fedora community. I have some experience in use case testing (writing and executing use cases), and I also have an ISTQB foundation level certificate in software testing, which basically means that I know what software testing is about, but I'm lacking practical experience and I need to learn much more. I am hoping that contributing to Fedora will be useful both to the community and to myself. I have little experience with Linux, but as I already stated, I'm an eager learner... Thank you for accepting me into your community, and I hope I will manage, even though I'm gonna need some help in the beginning to understand how things work around here. Wish you all the best! Neda Dzakic Mirkovic IRC: heda96 ___ 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 Gnome Install process - A pain
On Sat, Sep 22, 2018 at 9:41 PM Ed Greshko wrote: > > This will probably be considered a "minor" pain. And, since I don't use > GNOME except > in a VM for testing, I guess it is. > > I'd just like to go on record to say I dislike a few things about the install > process. > > 1. There is no option to set the hostname during install. > There is, but it's non-obvious. You have to set it in GNOME Settings before running the installer. I've complained about this in the past as well. > 2. User creation is delayed until first boot and at the time of creation > there is no > option to specify the UID and GID. So, if you're like me, and use existing > NFS services and your primary user doesn't have 1000/1000 for them you have > to either > know to create an initial throw away account or manually make changes > later. Or use FreeIPA/Active Directory to manage users and enroll as a client instead. This is generally a better idea than manually copying IDs around every time you deploy a new machine. ___ 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: Add release announcement post to Go/No-Go criteria
+1 - I'm on the mailing lists and I didn't even see the GO announcement for the beta! On Tue, Sep 25, 2018 at 1:35 PM, Ben Cotton wrote: > With today's Beta release, the release announcement post for Fedora > Magazine was not ready. As a result, the announcement went out a > little late and then only due to a drop-everything effort (thanks, > stickster!). We have a proposal to add a fourth criterion for the > Go/No-Go decision, beginning with F29 Final: > > 4. The release announcement post for Fedora Magazine is substantially complete > > As a reminder, these are the existing criteria: > > 1. No remaining blocker bugs > 2. Release candidate compose is available > 3. Test matrices for [milestone = Alpha, Beta, Final] are fully completed > > -- > Ben Cotton > Fedora Program Manager > TZ=America/Indiana/Indianapolis > ___ > 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 -- Mastering DFS Analytics https://leanpub.com/masteringdfsanalytics Markovs of the world, unite! You have nothing to lose but your chains! ___ 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: Self-Introduction: Ryan Himmelwright
- Original Message -
> From: "Ryan Himmelwright"
> To: test@lists.fedoraproject.org
> Sent: Wednesday, July 18, 2018 6:22:30 AM
> Subject: Self-Introduction: Ryan Himmelwright
>
> Hi Everyone,
>
> My name is Ryan Himmelwright and often go by himmAllRight on the
> internet and IRC. Outside the web, I've spent the last few years in the
> greater Boston area, but have recently moved to Durham NC (both USA).
>
> I have been lurking around the various Fedora groups over the last few
> years, but have never fully taken the plunge into a project. I am
> interested in becoming more involved with the QA group, in particular to
> help develop some of the testing tools (in addition to some package
> testing).
>
> I am a Linux and open source enthusiast and have been using Linux as my
> main driver for over 8 years now. I work as a software developer that
> unfortunately builds web applications to run on Windows (I don't get it
> either). I primarily use Common Lisp at my day job to develop large,
> automated, build systems, but am also familiar with Python, R, Go, and a
> bit of C. While I spend my work day in Windows, I use my early mornings
> and weekends learning everything I can about Linux. I am hoping to
> finally put some of those skills to use with the Fedora community .
>
>
> - Ryan
> ___
> 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/message/LCIFSAGAJXK2CIEOWRQQ7Z57S34PVHXP/
>
Hey Ryan,
Welcome to Fedora QA, It will be great if you apply for qa FAS group. If you
have, I have sponsored you by now.
You can start off by testing updates in [http://bodhi.fedoraproject.org/] for
Fedora 27, Fedora 28, and Fedora 29. Update testing is where a tester tests a
package and gives out a +1 Karma for PASS and -1 Karma for FAIL. You can go to
bodhi.fedoraproject.org where you can sort the packages with Fedora Releases
and tags viz "pending" & "testing". You can read much about update testing here
[1]. You can also, use fedora-easy-karma for giving out feedbacks.
you can start with Release Validation testing. In Release Validation all you
need to do is to check the nightly/TC/RC against certain criteria. For example,
let's take the latest compose (Fedora 29 Branched 20180923), you can run test
cases which are mentioned [2] and submit your results in the test matrix.
Note that each of the test cases[3] will have "How to test" section which will
have the steps (to be executed sequentially) and if the results match with the
expected results you can mark it as pass by editing the wiki page
{{result|PASS|}} . Always make sure to check for "Associated
release criterion" which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.
You can always find the ‘current’ validation pages using these addresses:
https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test
For Automation, you can start looking at
Taskotron[https://fedoraproject.org/wiki/Taskotron]
and Open QA[https://fedoraproject.org/wiki/OpenQA].
https://fedoraproject.org/wiki/QA:Updates_Testing
https://fedoraproject.org/wiki/Test_Results:Fedora_29_Branched_20180923.n.0_Summary?rd=Test_Results:Current_Summary
https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
https://bugzilla.redhat.com/
Feel free to ping us on IRC if you need any help #fedora-qa@freenode.
We have test days coming happening now which is a nice place to start, please
stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day
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
Re: Proposal: Add release announcement post to Go/No-Go criteria
On Tue, 2018-09-25 at 18:37 -0400, Matthew Miller wrote: > On Tue, Sep 25, 2018 at 04:35:09PM -0400, Ben Cotton wrote: > > With today's Beta release, the release announcement post for Fedora > > Magazine was not ready. As a result, the announcement went out a > > little late and then only due to a drop-everything effort (thanks, > > stickster!). We have a proposal to add a fourth criterion for the > > Go/No-Go decision, beginning with F29 Final: > > Isn't this supposed to be the point of the release-readiness meeting that > follows go/no-go? The readiness meeting is only run *once* - if we slip at the first go/no-go, we don't run another readiness meeting after the second one. (I don't know why that is, though.) -- 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
F29 / Rawhide - Bogus ssh host key mismatch errors mentioning "rsa-sha2-256"
Hey folks! Just a heads up, if anyone on F29 or Rawhide finds that suddenly ssh connections are failing, claiming the host key does not match and asking for a 'rsa-sha2-256' key: a mysterious hero known only as 'sedrubal' figured out that this is caused by a crypto-policies update, this one - https://bodhi.fedoraproject.org/updates/FEDORA-2018-854e0caf7b you can get back to normal by downgrading back to this build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1133273 (for both F29 and Rawhide). We've got enough negative karma on the update now that it should be removed from updates-testing on the next push, but some folks will have got the update already. I'll ask tmraz if he can either fix it promptly or revert it temporarily, for Rawhide users. Sorry for the trouble! -- 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
Introduction - Michael Erwin
Hi Everyone, Name here is Michael Erwin, FAS: nabooengineer, IRC: michael_t_erwin. Longtime Linux user, been on *NIX for 40+ years. I focus on HA, DR & performance on my day job, and hope to help in some small way if possible. Thank all of you for your hard work! -- -me Michael Erwin This email is RFC 1925 compliant and composed on 99.9% recycled electrons, so please print responsibly. ___ 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
Hello My name is Neda, I am 36 years old, and I am all new here! I live in Belgrade, the capitol of Serbia. I am also all new in QA, but am very excited and eager to learn new things and to contribute to Fedora community. I have some experience in use case testing, and I also have an ISTQB foundation level certificate in software testing, which basically means that I know what software testing is about, but I'm lacking some serious practical experience and I need and want to learn much more. Also, I'm currently learning some Java basics and app testing on my own. Fedora is a big and complex project and I am hoping that contributing to it will be useful both to Fedora community and to myself. I would like to thank you for accepting me into your community and I am very excited to be a part of it! Best regards! Neda Džakić Mirković You can contact me through: IRC nick: heda96 e-mail: hed...@gmail.com ___ 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
