Peter, thanks for taking a hand in this.
On 09/04/2018 07:02 PM, Peter Robinson wrote:
> On Tue, Sep 4, 2018 at 11:47 PM Robert Moskowitz <rgm@htt-consult.com> wrote:
>>
>>
>> On 09/04/2018 06:42 PM, Peter Robinson wrote:
>>> On Tue, Sep 4, 2018 at 11:27 PM Robert Moskowitz <rgm@htt-consult.com> wrote:
>>>> BTW,
>>>>
>>>> It seems the problem is with lightdm. It is fixed with the version in
>>>> the testing-update, but not in the base image. So I am in wait mode
>>>> until this goes through whatever it needs to go through...
>>> dnf upgrade should be enough to install it, and then reboot?
>> Yes. That is what I did. The system was really slow with all the
>> lightdm crashes, and dnf update took really long, but that may been for
>> all the other updates and dnf update to SD card in general.
> "systemctl stop lightdm" would have disabled the service.
But it is necessary to know about lightdm. It was only through working
through reporting the bug that I stumbled on lightdm being a problem.
Perhaps next time I will try stopping something that I see keeps looping
starting and crashing...
>
>> Once updated and rebooted, the GUI started up and I was able to run
>> through setup. Please see my last note in the bug report.
>>
>> I want to see an image with this version of lightdm and see it properly
>> go directly into the GUI setup.
> Sure, we're in freeze for beta ATM so _EVERY_ single change has to go
> through an approval process so it takes time.... oh and I want a pony!
I had wanted to attend the meeting today, but I forgot all about it when
finally working more on this bug. Would have been interesting to join
in for the first time. But more valuable that I identified something
wrong and what fixes it.
And no pony for me. Never did like Ford cars! :)
(my automotive days I worked at AMC then Chrysler)
Thanks for pushing this bug fix through. I will test an image once I
see the new version in the repo.
>
>>>> On 09/03/2018 04:22 PM, Dan Horák wrote:
>>>>> On Mon, 3 Sep 2018 16:13:37 -0400
>>>>> Robert Moskowitz <rgm@htt-consult.com> wrote:
>>>>>
>>>>>> On 09/03/2018 04:09 PM, Peter Robinson wrote:
>>>>>>> On Mon, Sep 3, 2018 at 9:06 PM Robert Moskowitz
>>>>>>> <rgm@htt-consult.com <mailto:rgm@htt-consult.com>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 09/03/2018 03:58 PM, Peter Robinson wrote:
>>>>>>>> On Mon, 3 Sep 2018, 19:57 Robert Moskowitz,
>>>>>>>> <rgm@htt-consult.com <mailto:rgm@htt-consult.com>> wrote:
>>>>>>>>
>>>>>>>> OK. I see after I created the bug, there was a field
>>>>>>>> called 'Blocks' which I entered ARMTracker into. I did not see
>>>>>>>> this when I was entering the bug.
>>>>>>>>
>>>>>>>>
>>>>>>>> It's mostly definitely there in the new bug page
>>>>>>> I just went to start a new bug:
>>>>>>>
>>>>>>> https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora
>>>>>>>
>>>>>>> And I don't see a blocker field. external Bug, yes, but I don't
>>>>>>> see how to use this (did try) for entering ARMTracker.
>>>>>>>
>>>>>>>
>>>>>>> Blocks: the last text field towards the bottom not far above the
>>>>>>> submit button
>>>>>> No Blocks: on my screen. See attached. I had tried Bug ID, but that
>>>>>> was not it.
>>>>> ah, you need to switch to the "advanced" form. There should be a link
>>>>> or button on the top.
>>>>>
>>>>>
>>>>> Dan
>>>>>
>>>>>>> Well hopefully this is the only bug I will ever need to
>>>>>>> report. ;)'
>>>>>>>
>>>>>>>> On 09/03/2018 02:51 PM, Peter Robinson wrote:
>>>>>>>>> Blocker field
>>>>>>>>>
>>>>>>>>> On Mon, 3 Sep 2018, 19:40 Robert Moskowitz,
>>>>>>>>> <rgm@htt-consult.com <mailto:rgm@htt-consult.com>> wrote:
>>>>>>>>>
>>>>>>>>> I don't see how to link this to ARMTracker...
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -------- Forwarded Message --------
>>>>>>>>> Subject: [Bug 1624972] New: No GUI desktop
>>>>>>>>> Date: Mon, 03 Sep 2018 18:36:45 +0000
>>>>>>>>> From: bugzilla@redhat.com
>>>>>>>>> <mailto:bugzilla@redhat.com> To: rgm@htt-consult.com
>>>>>>>>> <mailto:rgm@htt-consult.com>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1624972
>>>>>>>>>
>>>>>>>>> Bug ID: 1624972
>>>>>>>>> Summary: No GUI desktop
>>>>>>>>> Product: Fedora
>>>>>>>>> Version: 29
>>>>>>>>> Component: xfce4-session
>>>>>>>>> Severity: high
>>>>>>>>> Assignee:kevin@scrye.com
>>>>>>>>> <mailto:kevin@scrye.com> Reporter:rgm@htt-consult.com
>>>>>>>>> <mailto:rgm@htt-consult.com> QA
>>>>>>>>> Contact:extras-qa@fedoraproject.org
>>>>>>>>> <mailto:extras-qa@fedoraproject.org> CC:kevin@scrye.com
>>>>>>>>> <mailto:kevin@scrye.com>,nonamedotc@gmail.com
>>>>>>>>> <mailto:nonamedotc@gmail.com>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Description of problem:
>>>>>>>>>
>>>>>>>>> The Xfce desktop never starts. Lighted screen only
>>>>>>>>>
>>>>>>>>> Version-Release number of selected component (if
>>>>>>>>> applicable):
>>>>>>>>>
>>>>>>>>> Fedora-Xfce-armhfp-29-20180903.n.0-sda on Cubieboard2
>>>>>>>>>
>>>>>>>>> How reproducible:
>>>>>>>>>
>>>>>>>>> Been this way since I started testing F29-Xfce
>>>>>>>>>
>>>>>>>>> Steps to Reproduce:
>>>>>>>>> 1. Copy image to uSD card, specifying for a
>>>>>>>>> Cubieboard2
>>>>>>>>> 2. Connect Cubie to HDMI monitor, Kybd, Mouse,
>>>>>>>>> console TTY
>>>>>>>>> 3. Run screen on console to capture console log and
>>>>>>>>> login to console
>>>>>>>>> 4. Power up Cubie
>>>>>>>>> 5. "Started GSSAPI Proxy Daemon" is the last message
>>>>>>>>> on console and monitor before attempt to switch to GUI mode
>>>>>>>>>
>>>>>>>>> Actual results:
>>>>>>>>>
>>>>>>>>> Lighted screen with no response to kybd or mouse
>>>>>>>>> See:
>>>>>>>>>
>>>>>>>>> [ 148.658848] alloc_contig_range: [74200, 749f8)
>>>>>>>>> PFNs busy [ 165.979868] bridge: filtering via arp/ip/ip6tables
>>>>>>>>> is no longer available by [ 173.413278] alloc_contig_range:
>>>>>>>>> [74200, 74af8) PFNs busy [ 430.058044] alloc_contig_range:
>>>>>>>>> [74200, 74500) PFNs busy
>>>>>>>>>
>>>>>>>>> messages on console. Console is very slow to respond.
>>>>>>>>>
>>>>>>>>> Expected results:
>>>>>>>>>
>>>>>>>>> GUI starts up and whatever system initiation process
>>>>>>>>> runs on the Desktop. I do not know what that will be, as I have
>>>>>>>>> yet to get a F29 initial desktop.
>>>>>>>>>
>>>>>>>>> Additional info:
>>>>>>>>>
>>>>>>>>> The same setup with Centos Gnome:
>>>>>>>>>
>>>>>>>>> CentOS-Userland-7-armv7hl-generic-GNOME-1804-sda
>>>>>>>>>
>>>>>>>>> Brings up the Gnome desktop. I have not tried any
>>>>>>>>> other F29 desktop.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> You are receiving this mail because:
>>>>>>>>> You reported the bug.
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> arm mailing list -- arm@lists.fedoraproject.org
>>>>>>>>> <mailto:arm@lists.fedoraproject.org>
>>>>>>>>> To unsubscribe send an email to
>>>>>>>>> arm-leave@lists.fedoraproject.org
>>>>>>>>> <mailto:arm-leave@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/arm@lists.fedoraproject.org
>>>>>>>>>
>>>>> _______________________________________________
>>>>> arm mailing list -- arm@lists.fedoraproject.org
>>>>> To unsubscribe send an email to arm-leave@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/arm@lists.fedoraproject.org
>>>> _______________________________________________
>>>> arm mailing list -- arm@lists.fedoraproject.org
>>>> To unsubscribe send an email to arm-leave@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/arm@lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@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/arm@lists.fedoraproject.org
No comments:
Post a Comment