Contribution for beginners
by Varun Sekhar
Hello,
I am Varun Sekhar, a freshman of Computer Science department at Amrita
School of Engineering, Kerala, India.
I have a basic knowledge of Python and C++. The reason for choosing Fedora
is that I have always been fascinated by open-source operating systems. I
am keenly interested to develop and contribute to the Fedora project and be
a member of their widespread community.
Please enlighten me with the procedure to start with the contribution of
Fedora project. Looking forward for a good start.
Thanks,
Varun Sekhar
7 years, 4 months
What to do with vino
by Jiri Eischmann
Hi,
I was going through most frequent crashers in Fedora 25 and vino is in
TOP10. When I looked at it I realized it crashed on Wayland because for
screen sharing you need X. [1]
It's a bit unfortunate that we have vino, which by default doesn't
work, in the default installation and its functionality is exposed in
Control Center. I wonder if it'd make a sense to patch the sharing
module in the control center to check if the session is running on
Wayland and if so, to disable the dialog.
My understanding is that screen sharing is moving to the compositor or
Pinos [2] and vino will be deprecated, but in the meantime we shouldn't
expose its functionality on Wayland.
Jiri
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1394599
[2] https://wiki.gnome.org/Initiatives/Wayland/Remoting
7 years, 4 months
Mac release criteria and testing
by Paul W. Frields
Yesterday the release team agreed to slip the F25 release by a week
due to not being able to fulfill all the release criteria, namely:
https://bugzilla.redhat.com/show_bug.cgi?id=1393846
This bug is one of the criteria that I assume the Workstation group
values, because it helps us bring a working Fedora to people with Mac
hardware. Several Workstation WG members were in the meeting and
agreed this was an important criterion.
The bug was found late because there is a lack of people/time/hardware
for testing Mac-related criteria. One of the QA folks happened to run
the test late and it turned out there was a small possibility our
release could literally break someone's existing OS X/macOS install.
We can argue about whether or not it was OK to block the release based
on this bug. But more importantly this bug illustrates that Fedora
success relies on shared responsibility.
Creating release criteria has helped us create increasingly strong
releases over the last several years. This process has been valiantly
led by the QA team with much success. However, we can't simply add to
criteria and then expect QA to simply "test all the things." It's
incumbent on the WGs to pitch in where it makes sense to ensure
success.
I've taken some steps to help personally with some of this testing
since I have some Mac hardware. And I'm looking to other Workstation
WG members and people with affinity for the desktop to do the same
during the F26 release cycle. If we can't bring together that kind of
effort, we should drop the relevant Mac-related criteria (or call them
best-effort or non-blocking).
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
7 years, 4 months
Re: [Test-Announce] Fedora 25 Candidate RC-1.2 Available Now!
by Adam Williamson
On Wed, 2016-11-09 at 16:02 -0800, rawhide(a)fedoraproject.org wrote:
> According to the schedule [1], Fedora 25 Candidate RC-1.2 is now
> available for testing. Please help us complete all the validation
> testing! For more information on release validation testing, see:
> https://fedoraproject.org/wiki/QA:Release_validation_test_plan
>
> Test coverage information for the current release can be seen at:
> https://www.happyassassin.net/testcase_stats/25
>
> You can see all results, find testing instructions and image download
> locations, and enter results on the Summary page:
>
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.2_Summary
>
> The individual test result pages are:
>
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.2_Installation
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.2_Base
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.2_Server
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.2_Cloud
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.2_Desktop
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.2_Security_Lab
>
> All RC priority test cases for each of these test pages [2] must
> pass in order to meet the RC Release Criteria [3].
>
> Help is available on #fedora-qa on irc.freenode.net [4], or on the
> test list [5].
There are two changes from RC-1.1 in RC-1.2:
libblockdev-1.9-8.fc25 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-76a96e8bf3
selinux-policy-3.13.1-224.fc25 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-f29b746f2e
those fix a couple of partitioning bugs kparal found in RC-1.1:
https://bugzilla.redhat.com/show_bug.cgi?id=1393379
https://bugzilla.redhat.com/show_bug.cgi?id=1393373
Unfortunately both packages can at least *theoretically* affect almost
anything else (selinux-policy for obvious reasons, and libblockdev
because anaconda uses it), so it would be good to re-run as many tests
as we can with this compose. Sorry for the extra work, folks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
7 years, 4 months
Lenovo T440s external display issues
by Wes Gelpi
I have installed F24 on my T440s. I very rarely can get an external monitor
to work outside of my docking station. Whenever I go into a conference room
it won't recognize the external display OR it will recognize it but the
display won't turn on. I have tried everything in the way of
troubleshooting that I can think of. Has anyone else encountered this and
found a solution?
7 years, 4 months
Workstation WG meeting recap 2016-Nov-09
by Paul W. Frields
Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2016-11-09/workstation.2...
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting/2016-11-09/workstation.2...
Log: https://meetbot.fedoraproject.org/fedora-meeting/2016-11-09/workstation.2...
* * *
===============================
#fedora-meeting: Workstation WG
===============================
Meeting started by stickster at 16:00:27 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2016-11-09/workstation.2...
.
Meeting summary
---------------
* Roll call (stickster, 16:00:33)
* WG meeting schedule (stickster, 16:08:11)
* IDEA: Move meeting 2 hours earlier (to 09:00 US-Eastern time)
(stickster, 16:08:31)
* ACTION: stickster set up Doodle poll to see if we can reschedule WG
meetings at a better time (stickster, 16:15:06)
* Release announcement (stickster, 16:16:13)
* LINK:
https://fedoraproject.org/wiki/F25_general_release_announcement
(stickster, 16:16:19)
* thanks mcatanzaro for input, revisions made earlier this morning
(stickster, 16:16:32)
* coredumpctl issue (stickster, 16:22:17)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1341829
(stickster, 16:22:20)
* ACTION: mcatanzaro write up F26 Change page that addresses this bug
(stickster, 16:42:13)
* ACTION: stickster contact SELinux and systemd devs for heads up on
the Change, and see if we can align on an approach (stickster,
16:42:41)
* Open floor (all other business) (stickster, 16:46:17)
* LINK: https://wiki.gnome.org/Design/OS/DownstreamBranding
(stickster, 16:47:18)
* ACTION: stickster put downstream branding first in agenda next
meeting (stickster, 16:51:22)
* ACTION: cschalle_ to propose branding policy (mcatanzaro, 16:55:28)
Meeting ended at 16:59:27 UTC.
Action Items
------------
* stickster set up Doodle poll to see if we can reschedule WG meetings
at a better time
* mcatanzaro write up F26 Change page that addresses this bug
* stickster contact SELinux and systemd devs for heads up on the Change,
and see if we can align on an approach
* stickster put downstream branding first in agenda next meeting
* cschalle_ to propose branding policy
Action Items, by person
-----------------------
* cschalle
* cschalle_ to propose branding policy
* cschalle_
* cschalle_ to propose branding policy
* mcatanzaro
* mcatanzaro write up F26 Change page that addresses this bug
* stickster
* stickster set up Doodle poll to see if we can reschedule WG meetings
at a better time
* stickster contact SELinux and systemd devs for heads up on the
Change, and see if we can align on an approach
* stickster put downstream branding first in agenda next meeting
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* stickster (87)
* mcatanzaro (30)
* mclasen (17)
* zodbot (13)
* kalev (9)
* rdieter (6)
* cschalle (5)
* cschalle_ (3)
* sfix (2)
* Southern_Gentlem (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
7 years, 4 months
Re: [Test-Announce] Fedora 25 Candidate RC-1.1 Available Now!
by Adam Williamson
On Wed, 2016-11-09 at 00:36 -0800, rawhide(a)fedoraproject.org wrote:
> According to the schedule [1], Fedora 25 Candidate RC-1.1 is now
> available for testing. Please help us complete all the validation
> testing! For more information on release validation testing, see:
> https://fedoraproject.org/wiki/QA:Release_validation_test_plan
>
> Test coverage information for the current release can be seen at:
> https://www.happyassassin.net/testcase_stats/25
>
> You can see all results, find testing instructions and image download
> locations, and enter results on the Summary page:
>
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Summary
>
> The individual test result pages are:
>
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Installation
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Base
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Server
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Cloud
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Desktop
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Security_Lab
>
> All RC priority test cases for each of these test pages [2] must
> pass in order to meet the RC Release Criteria [3].
>
> Help is available on #fedora-qa on irc.freenode.net [4], or on the
> test list [5].
>
> Current Blocker and Freeze Exception bugs:
> http://qa.fedoraproject.org/blockerbugs/current
>
> [1] http://fedorapeople.org/groups/schedule/f-25/f-25-quality-tasks.html
> [2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan
> [3] https://fedoraproject.org/wiki/Fedora_25_RC_Release_Criteria
> [4] irc://irc.freenode.net/fedora-qa
> [5] https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/
Hi folks! Sending this along to more lists, with an extra note: the
Fedora 25 Go/No-Go is on Thursday - yes, tomorrow for most of the world
- so we need YOU to help run all the tests! We need to fill out all of
the Alpha, Beta and Final (not 'RC', as the mail says...I should fix
that) tests on all the validation pages. Some particular tests that
it'd be great to have people working on are the Server tests, non-
English installs, and the Desktop 'menus' tests, which basically mean
'install Workstation or KDE and run every single app that's installed
and make sure they all at least basically work'.
If you run into any serious issues, please propose them as Final
blockers, either using blockerbugs:
https://qa.fedoraproject.org/blockerbugs/propose_bug
or simply by marking the bug as 'Blocks: FinalBlocker' (and please add
a comment with an explanation of why you think it should block
release).
Thanks a lot, everyone!
Note, there is one bug currently accepted as a blocker which is not
addressed by this compose:
https://bugzilla.redhat.com/show_bug.cgi?id=1382001
but there is clearly some sentiment to drop its blocker status, so we
decided to go ahead and run a compose and get it tested so if we do
decide to drop that bug from the blocker list, and no other blockers
appear, we can ship.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
7 years, 4 months
Touchpad data needed - 5 min of effort
by Peter Hutterer
Are you using a touchpad frequently during the day? Then please read on, I need
some touchpad usage data and it'll only take you 5 minutes to run the commands
below to gather the data.
If you're technical enough, here's the TLDR:
in screen, run sudo evemu-record > touchpad-recording.evemu, select your
touchpad device and at the end of the day upload a compressed tarball somewhere
and send me the link off-list. thanks.
Otherwise, the steps one-by-one:
Open a a terminal now, then install evemu:
$> sudo dnf install -y evemu screen
Then start screen:
$> screen -S evemu
Now you're inside screen and you can start the recording
$> sudo evemu-record > $HOME/touchpad-recording.evemu
One device will be a touchpad, named "SynPS/2 Synaptics Touchpad" or some other
name that should be identifiable. If you're on a late model Dell, it may be
named DLL0234 or something. Once you selected the device, evemu will start
recording.
Then hit Ctrl+a, then d to detach screen and return to the terminal.
Check that the recording works:
$> tail -f $HOME/touchpad-recording.evemu
Whenever you touch the touchpad, you should see events filling up the screen
now. If so, everything is working. Hit Ctrl+C to quit the 'tail' command. You
can close the terminal now.
The screen session will now sit in the background, recording all your touchpad
events into that file. At the end of the day:
First, open a terminal and restore the screen session:
$> screen -r evemu
Hit Ctrl+C to interrupt the evemu-record process, then type exit to quit
screen. Compress it first so it reduces in size a bit:
$> gzip $HOME/touchpad-recording.evemu
Now upload the newly created $HOME/touchpad-recording.evemu.gz file somewhere
and send me a off-list email with the link so I can grab it.
Thanks heaps.
As for "why" do I need this? I need it to analyse touchpad motion data to get
an idea of what range of finger motion speed is common and expected during
normal usage.
Cheers,
Peter
7 years, 4 months