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