On Mon, 3 Sep 2018, 19:57 Robert Moskowitz, <rgm(a)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
On 09/03/2018 02:51 PM, Peter Robinson wrote:
>
> Blocker field
>
> On Mon, 3 Sep 2018, 19:40 Robert Moskowitz, <rgm(a)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(a)redhat.com
>> To: rgm(a)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(a)scrye.com
>> Reporter: rgm(a)htt-consult.com
>> QA Contact: extras-qa(a)fedoraproject.org
>> CC: kevin(a)scrye.com, nonamedotc(a)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(a)lists.fedoraproject.org
>> To unsubscribe send an email to arm-leave(a)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
>>
>
>
Hi there,
While testing upstream kernel on some devices, I've recently
discovered that suspend was broken for "distro kernel" (not only
related to fedora kernel, but also ubuntu).
I order to debug this, I was advised to use a serial console and boot
with theses options:
no_console_suspend=1 initcall_debug
Then using systemctl suspend outputs this report for me:
https://bugzilla.redhat.com/show_bug.cgi?id=1619699
Basically, I'm running a tegra device, but a pxa driver (unrelated to
the device) lead to a crash preventing suspend.
I would like others on this list to try to report such use case, I
don't expect pxa_gpio to be the only driver to have issue in the
fedora config. Specially as it does not have problem at boot time or
shutdown so this problem might remains silent.
Please don't forget to block ARMTracker on bugzilla.redhat.com, and
mention it there if you uses upstream bug tracker.
Thx for any report.
--
-
Nicolas (kwizart)
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(a)redhat.com
To: rgm(a)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(a)scrye.com
Reporter: rgm(a)htt-consult.com
QA Contact: extras-qa(a)fedoraproject.org
CC: kevin(a)scrye.com, nonamedotc(a)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.