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/
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 on 2018-09-26.
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_test…
As usual, the test day will be in #fedora-test-day@freenode
Thanks
//sumantro
Fedora QA
==================================
#fedora-meeting: Fedora QA Meeting
==================================
Meeting started by adamw at 15:01:33 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting/2018-09-24/fedora-qa.2018-…
.
Meeting summary
---------------
* Roll call (adamw, 15:01:41)
* Previous meeting follow-up (adamw, 15:14:00)
* no action items from previous meeting (adamw, 15:14:40)
* Fedora 29 status (adamw, 15:14:51)
* Beta was signed off and is shipping tomorrow (adamw, 15:14:58)
* folks have run into a variety of niggles with it, but nothing really
bad was discovered late, happily (adamw, 15:15:16)
* Common Bugs needs creating and writing, i'll do that today (adamw,
15:18:16)
* Final freeze starts 2018-10-09 (adamw, 15:20:58)
* Final go/no-go is scheduled for 2018-10-18 (adamw, 15:21:15)
* Proposed release criteria discussion (optical discs, printing, fwraid)
(adamw, 15:32:57)
* the current proposals were discussed, we don't have enough people
present to form a clear decision on accepting any particular
proposal, so we just talked through them for a while (adamw,
15:53:06)
* Test Day status (adamw, 15:53:52)
* LINK:
https://fedoraproject.org/wiki/Test_Day:2018-09-20_Silverblue_Testday
-- saw fairly good amount of testing with about 70+ testers. We have
Java 8,10,11 test day coming up on 2018-09-26
https://fedoraproject.org/wiki/Test_Day:2018-09-26:java_8,_10_and_11_testday.
(sumantro, 15:53:54)
* Silverblue Test Day had a good turnout with 70+ testers (adamw,
15:56:03)
* Java (09-26), Cloud/Atomic (10-01), DNF (10-03) and GNOME 3.30
(10-05) are all coming up (adamw, 15:56:29)
* Open floor (adamw, 15:59:38)
* ACTION: adamw to work on better meeting time management (adamw,
15:59:56)
* ACTION: adamw to make sure jlanda's PRs on fedora-qa get reviewed
(adamw, 16:06:14)
Meeting ended at 16:07:59 UTC.
Action Items
------------
* adamw to work on better meeting time management
* adamw to make sure jlanda's PRs on fedora-qa get reviewed
Action Items, by person
-----------------------
* adamw
* adamw to work on better meeting time management
* adamw to make sure jlanda's PRs on fedora-qa get reviewed
* jlanda
* adamw to make sure jlanda's PRs on fedora-qa get reviewed
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* adamw (84)
* cmurf (36)
* Southern_Gentlem (15)
* jlanda (14)
* sumantro (10)
* zodbot (6)
* coremodule (6)
* bcotton (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
On 9/23/18 1:16 PM, Chris Murphy wrote:
> I would keep testing other things, and try to break it, and file bugs
> or report it on test@ if you're confused about some behavior.
>
> On Sun, Sep 23, 2018 at 6:29 AM, pmkellly(a)frontier.com
> <pmkellly(a)frontier.com> wrote:
>>
>> On 9/22/18 12:32 PM, Chris Murphy wrote:
>>>
>>> On Sat, Sep 22, 2018 at 7:49 AM pmkellly(a)frontier.com
>>> <pmkellly(a)frontier.com> wrote:
>>>
>>>> I decided to go ahead to try doing some testing. The runaway mode was
>>>> still running when I started testing things. First I did the desktop
>>>> browser tests and they passed. Then I did the desktop terminal tests and
>>>> they also passed. Then I ran the desktop update graphical tests using
>>>> the Software application. The application started fine and I could get
>>>> to the Updates screen okay, but when I clicked the Refresh button, after
>>>> a few seconds I got a gray colored pop up that said it could not
>>>> continue and a long list of errors. The pop up does not support Copy so
>>>> I didn't capture the details. I closed the Software application and
>>>> tried to reopen it. The window came up but the usual graphics and text
>>>> was not present. I restarted the PC to get out of the runaway mode and
>>>> then I was able to run the update graphical test to completion and it
>>>> passed.
>>>>
>>>> It seems that this gnome-software runaway mode does more than just use
>>>> up cycles. I am discontinuing testing. Please let me know if there is
>>>> something more you want me to do / try.
>>>
>>>
>>> I see a lot of these in your journal:
>>>
>>> Sep 22 10:03:40 f29h.local packagekitd[1104]: g_object_ref: assertion
>>> 'G_IS_OBJECT (object)' failed
>>>
>>> I see them in mine as well, no idea if they're related to the runaway
>>> process. What I'm seeing is packagekit using about 9% CPU when it's
>>> downloading metadata (refreshing repo and app info); and using a more
>>> than 100% CPU when it's downloading files.
>>>
>>> So I filed this:
>>> g_object_ref spewing in journal bug
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1631968
>>>
>>> It's probably a gtk thing but I've set the component to packagekit
>>> since it's the one doing the spewing.
>>>
>>> Also, you can disable the background downloading of updated packages
>>> by packagekit with:
>>>
>>> $ gsettings set org.gnome.software download-updates false
>>>
>>> This is a per user setting. You still get metadata refresh, you can
>>> still use Gnome Software to install/remove and update applications, it
>>> just won't download any packages in the background, and so you also
>>> won't get any notifications for updates. You can either use Gnome
>>> Software or dnf to manually apply updates.
>>>
>>>
>>
>> In regard to the update: As I wrote yesterday, after a restart to stop the
>> runaway. the Update Graphical test was run with Software successfully and
>> the updates were installed. I also used dnf to look at the history and
>> listed some of the changed / replaced packages.
>>
>> Well, there had not been a recurrence of the runaway from when the updates
>> were run to when I wrote last yesterday. After that the machine set logged
>> in, but locked for the rest of the day and overnight. The runaway has not
>> recurred. Since it always recurred within such a period, I am guessing that
>> one of the updates fixed the problem. I should have noted yesterday that
>> neither packagekit nor gnome-software were among the package names seen in
>> the history list yesterday.
>>
>> Any ideas? I will continue leaving the machine idle with no changes,
>> updates, or testing until I hear back on what, if anything, I should do
>> next.
>>
>> Have a Great Day!
>>
>> Pat (tablepc)
>>
>
>
>
I ran the non-coconut test cases with no failures with the exception of
keyring. I don't use that and am not familiar with how to use it so I
always skip that one since I don't want to generate false failures. I
observed no failures or anomalies while running the test cases.
Then I decided to configure the machine to be like my in use machines.
First I ran the software uninstalls and installs script.
After I ran the software script and did a restart, I started getting
three SELinux alerts that I never got before. So far, these occur only
when I do a restart and are 100% repeatable.
process=boltd, acc=create, dir=power
process=boltd, acc=add_name, dir=power
process=boltd, acc=write, dir=boltd
I have never seen this before and I have no idea if this is a bug or
purely the result of software that was uninstalled, or software that got
installed.
Then I ran the settings script and it ran fine with no additional
problems noted. I just started dead or alive testing the applications
with no additional problems found so far. The gnome-software runaway has
not repeated.
I was there was a update for gnome-shell so I ran that. After the
restart I still got the same SELinux alerts. Weather is one of the
applications I uninstall. I thought maybe in this version that
libgweather was uninstalled too. That library seems to be used lots of
places and I thought if it was gone that might be the root of the
SELinux alerts, but I looked and libgweather is still installed. I also
tried turning off all of the gnome-shell extensions that get installed.
I still got the same SELinux alerts after a restart.
Any ideas? I have attached the scripts I use in case you would like to
look at them.
Have a Great Day!
Pat
Crossposting
test@
desktop@
Hi,
I keep getting this weird behavior on Fedora 29 for which there are no
journal messages at all. This is the setup:
1. on battery power
2. Settings>Power>Blank Power = 5 minutes
3. Settings>Power>Dim Screen when inactive = On
4. Settings>Power>Automatic Suspend>Battery = On, 15 minutes
---
5. Use is inactive for more than 5 minutes, and less than 15. (At 15
minutes it definitely goes into suspend successfully).
6. I look up and see the GNOME lock screen with multiple yakyak
notifications, and also see a power notification (international stop
sign symbol). The power notification doesn't itself make the display
come on, it's yakyak. If I don't receive an incoming message on
yakyak, I have no idea the power notification is present. And if I
take a screenshot while the display is off, the screenshot file is all
black.
7. The instant I click on any key or the trackpad, only the power
notification vanishes. The yakyak message remain in the list, and once
I log back into my user session, the power notification is not in the
drop down list of notifications when clicking on the time. And yet all
the yakyak notifications are in the list.
8. Nothing in the journal related to power
https://paste.fedoraproject.org/paste/p1Y-B8Sq3446sM4H5FtvgQ/raw
Is there a way to make the environment spit out more verbose messages
into the journal? I don't see a debug or verbose option with
gnome-shell -h
gnome-shell-3.30.0-7.fc29.x86_64
--
Chris Murphy