Graphical nstallation of Beta TC4 Fedora-Workstation-netinst-x86_64-22_Beta_TC4.iso fails in VirtualBox
3:30 a.m.
For testing Fedora-Workstation-netinst-x86_64-22_Beta_TC4 I set up a
virtual machine in VirtualBox with a virtual 32MB video card. After the
installer has started and set up the X, rather early it hangs up.
Inspecting the logs I saw a hint: please install F22 in *textmode*.
Trying that will install completely.
After installation, the F22 VM runs flawlessly in a X11 environment.
Question: is this a bug or a feature?
Kind regards
Joachim Backes
--
Fedora release 22 (Twenty Two)
Kernel-4.0.0-0.rc4.git2.1.fc22.x86_64
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
https://www-user.rhrk.uni-kl.de/~backes
10:44 a.m.
On Sun, 2015-03-22 at 09:30 +0100, Joachim Backes wrote:
For testing Fedora-Workstation-netinst-x86_64-22_Beta_TC4 I set up a
virtual machine in VirtualBox with a virtual 32MB video card. After
the installer has started and set up the X, rather early it hangs
up. Inspecting the logs I saw a hint: please install F22 in
*textmode*. Trying that will install completely.
After installation, the F22 VM runs flawlessly in a X11 environment.
Question: is this a bug or a feature?
A bug, but bugs that are VBox-specific don't necessarily rate a super
high priority. What exactly is this message you're seeing in the logs?
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
11:14 a.m.
On Sun, 2015-03-22 at 08:44 -0700, Adam Williamson wrote:
On Sun, 2015-03-22 at 09:30 +0100, Joachim Backes wrote:
> For testing Fedora-Workstation-netinst-x86_64-22_Beta_TC4 I set up
> a virtual machine in VirtualBox with a virtual 32MB video card.
> After the installer has started and set up the X, rather early
> it hangs up. Inspecting the logs I saw a hint: please install
> F22 in
> *textmode*. Trying that will install completely.
>
> After installation, the F22 VM runs flawlessly in a X11
> environment.
>
> Question: is this a bug or a feature?
A bug, but bugs that are VBox-specific don't necessarily rate a
super high priority. What exactly is this message you're seeing in
the logs?
Interestingly, I see the same bug in my openQA tests:
https://openqa.happyassassin.net/tests/2782
screen goes black shortly after reaching the hub. I don't see this
message about text mode, though.
I'm wondering if it's something to do with this time jump:
15:42:59,993 DEBUG anaconda: spoke is ready:
<pyanaconda.ui.gui.spokes.storage.StorageSpoke object at 0x7ff3615dea50>
09:55:00,003 INFO anaconda: System time set to Sun Mar 22 16:55:00 2015 UTC
09:55:00,000 INFO anaconda: System time set to Sun Mar 22 16:55:00 2015 UTC
09:55:00,000 INFO anaconda: System time set to Sun Mar 22 16:55:00 2015 UTC
09:55:00,000 INFO anaconda: Thread Done: AnaDateTimeThread (140683642418944)
09:55:00,006 DEBUG anaconda: spoke is ready:
<pyanaconda.ui.gui.spokes.datetime_spoke.DatetimeSpoke object at 0x7ff361670a10>
in my openQA jobs the screen seems to blank right around the time that
happens (though with the accelerated videos it's hard to be sure).
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
11:37 a.m.
On Sun, 2015-03-22 at 09:14 -0700, Adam Williamson wrote:
On Sun, 2015-03-22 at 08:44 -0700, Adam Williamson wrote:
> On Sun, 2015-03-22 at 09:30 +0100, Joachim Backes wrote:
> > For testing Fedora-Workstation-netinst-x86_64-22_Beta_TC4 I set
> > up a virtual machine in VirtualBox with a virtual 32MB video
> > card. After the installer has started and set up the X,
> > rather early it hangs up. Inspecting the logs I saw a hint:
> > please install F22 in
> > *textmode*. Trying that will install completely.
> >
> > After installation, the F22 VM runs flawlessly in a X11
> > environment.
> >
> > Question: is this a bug or a feature?
>
> A bug, but bugs that are VBox-specific don't necessarily rate a
> super high priority. What exactly is this message you're seeing
> in the logs?
Interestingly, I see the same bug in my openQA tests:
https://openqa.happyassassin.net/tests/2782
screen goes black shortly after reaching the hub. I don't see this
message about text mode, though.
I'm wondering if it's something to do with this time jump:
15:42:59,993 DEBUG anaconda: spoke is ready:
<pyanaconda.ui.gui.spokes.storage.StorageSpoke object at
0x7ff3615dea50>
09:55:00,003 INFO anaconda: System time set to Sun Mar 22 16:55:00
2015 UTC
09:55:00,000 INFO anaconda: System time set to Sun Mar 22 16:55:00
2015 UTC
09:55:00,000 INFO anaconda: System time set to Sun Mar 22 16:55:00
2015 UTC
09:55:00,000 INFO anaconda: Thread Done: AnaDateTimeThread
(140683642418944)
09:55:00,006 DEBUG anaconda: spoke is ready:
<pyanaconda.ui.gui.spokes.datetime_spoke.DatetimeSpoke object at
0x7ff361670a10>
in my openQA jobs the screen seems to blank right around the time
that happens (though with the accelerated videos it's hard to be
sure).
Nope, in a manual test, the blank happens about 25 seconds after the
time jump. (The manual test VM has Spice/QXL, while my openQA uses
VNC/vga, so this doesn't seem tied to a specific video adapter or to
VNC...)
In journalctl -b I see a couple of interesting messages right around
the blank:
Mar 22 17:41:33 localhost org.a11y.Bus[1477]:
g_dbus_connection_real_closed: Remote peer vanished with error:
Underlying GIOStream returned 0 bytes on an async read (g-io-error-
quark, 0). Exiting.
Mar 22 17:41:33 localhost org.a11y.atspi.Registry[1483]:
g_dbus_connection_real_closed: Remote peer vanished with error:
Underlying GIOStream returned 0 bytes on an async read (g-io-error-
quark, 0). Exiting.
but haven't been able to figure much out beyond that yet...
TC4 and TC2 (which definitely doesn't have this bug for me) have the
same Xorg versions, but TC4 has kernel rc3.git0.1.fc22 while TC2 has
kernel rc1.git0.1.fc22.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
1:01 p.m.
On Sun, 2015-03-22 at 09:37 -0700, Adam Williamson wrote:
Nope, in a manual test, the blank happens about 25 seconds after the
time jump. (The manual test VM has Spice/QXL, while my openQA uses
VNC/vga, so this doesn't seem tied to a specific video adapter or to
VNC...)
In journalctl -b I see a couple of interesting messages right around
the blank:
Mar 22 17:41:33 localhost org.a11y.Bus[1477]:
g_dbus_connection_real_closed: Remote peer vanished with error:
Underlying GIOStream returned 0 bytes on an async read (g-io-error-
quark, 0). Exiting.
Mar 22 17:41:33 localhost org.a11y.atspi.Registry[1483]:
g_dbus_connection_real_closed: Remote peer vanished with error:
Underlying GIOStream returned 0 bytes on an async read (g-io-error-
quark, 0). Exiting.
but haven't been able to figure much out beyond that yet...
TC4 and TC2 (which definitely doesn't have this bug for me) have the
same Xorg versions, but TC4 has kernel rc3.git0.1.fc22 while TC2 has
kernel rc1.git0.1.fc22.
Ah, I see something now, on anaconda's pane (ctrl-alt-f1) there's a
traceback indicating anaconda crashed. Aha - this is the 'hawkey
crash' bcl was talking about on IRC, which we couldn't figure out
whether it was related to the fix for the networking problem or not.
The bug report is https://bugzilla.redhat.com/show_bug.cgi?id=1201897 .
Can other folks seeing the 'black screen' check through ttys and
confirm that they see a traceback referring to libhawkey and libedit
somewhere? Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
12:31 p.m.
On 03/22/2015 04:44 PM, Adam Williamson wrote:
On Sun, 2015-03-22 at 09:30 +0100, Joachim Backes wrote:
> For testing Fedora-Workstation-netinst-x86_64-22_Beta_TC4 I set up a
> virtual machine in VirtualBox with a virtual 32MB video card. After
> the installer has started and set up the X, rather early it hangs
> up. Inspecting the logs I saw a hint: please install F22 in
> *textmode*. Trying that will install completely.
>
> After installation, the F22 VM runs flawlessly in a X11 environment.
>
> Question: is this a bug or a feature?
A bug, but bugs that are VBox-specific don't necessarily rate a super
high priority. What exactly is this message you're seeing in the logs?
Hi Adam,
this happens some seconds after I activated the spoke "select
installation source". Because nothing happened, I selected anaconda
console 4 (or 3, I don't remeber), and there I see: "Pane is dead".
So going to anaconda console 1, there I saw the message:
"if the graphical installation interface fails to start, try again with
the inst.text bootoption to start text installation" . Pls. see attachments.
Using this advice was very helpful (see my previous email).
Kind regards
Joachim Backes
--
Fedora release 22 (Twenty Two)
Kernel-4.0.0-0.rc4.git2.1.fc22.x86_64
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
https://www-user.rhrk.uni-kl.de/~backes
12:55 p.m.
I'm experiencing the same problem with netinst, whereas live works OK.
I can't tell from any of the logs what the source of the problem is,
the screen just goes black shortly after choosing a partition scheme
in Manual Partitioning.
Chris Murphy
1:03 p.m.
I see this backtrace on tty1, but there's no -tb file in /tmp, and
none of the backtrace info on tty1 is found in any of the logs in /tmp
or in journalctl. I think a bug will need the screen shot.
Chris Murphy
1:05 p.m.
On Sun, 2015-03-22 at 12:03 -0600, Chris Murphy wrote:
I see this backtrace on tty1, but there's no -tb file in /tmp,
and
none of the backtrace info on tty1 is found in any of the logs in
/tmp or in journalctl. I think a bug will need the screen shot.
The bug report already has a full backtrace and coredump attached,
which dshea managed to get.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
12:58 p.m.
On Sun, 2015-03-22 at 18:31 +0100, Joachim Backes wrote:
On 03/22/2015 04:44 PM, Adam Williamson wrote:
> On Sun, 2015-03-22 at 09:30 +0100, Joachim Backes wrote:
> > For testing Fedora-Workstation-netinst-x86_64-22_Beta_TC4 I set
> > up a virtual machine in VirtualBox with a virtual 32MB video
> > card. After the installer has started and set up the X, rather
> > early it hangs up. Inspecting the logs I saw a hint: please
> > install F22 in
> > *textmode*. Trying that will install completely.
> >
> > After installation, the F22 VM runs flawlessly in a X11
> > environment.
> >
> > Question: is this a bug or a feature?
>
> A bug, but bugs that are VBox-specific don't necessarily rate a
> super high priority. What exactly is this message you're seeing in
> the logs?
>
Hi Adam,
this happens some seconds after I activated the spoke "select
installation source". Because nothing happened, I selected anaconda
console 4 (or 3, I don't remeber), and there I see: "Pane is dead".
'pane is dead' is an interesting one, indicates anaconda actually died
somehow, but I don't see any indication of that in my case...I'll have
to look again.
So going to anaconda console 1, there I saw the message:
"if the graphical installation interface fails to start, try again
with the inst.text bootoption to start text installation" . Pls.
see attachments.
That's just a standard message, in fact, nothing specific to your
case. I think it's *always* printed.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
1:17 p.m.
On 03/22/2015 06:58 PM, Adam Williamson wrote:
On Sun, 2015-03-22 at 18:31 +0100, Joachim Backes wrote:
> On 03/22/2015 04:44 PM, Adam Williamson wrote:
>> On Sun, 2015-03-22 at 09:30 +0100, Joachim Backes wrote:
>>> For testing Fedora-Workstation-netinst-x86_64-22_Beta_TC4 I set
>>> up a virtual machine in VirtualBox with a virtual 32MB video
>>> card. After the installer has started and set up the X, rather
>>> early it hangs up. Inspecting the logs I saw a hint: please
>>> install F22 in
>>> *textmode*. Trying that will install completely.
>>>
>>> After installation, the F22 VM runs flawlessly in a X11
>>> environment.
>>>
>>> Question: is this a bug or a feature?
>>
>> A bug, but bugs that are VBox-specific don't necessarily rate a
>> super high priority. What exactly is this message you're seeing in
>> the logs?
>>
>
> Hi Adam,
>
> this happens some seconds after I activated the spoke "select
> installation source". Because nothing happened, I selected anaconda
> console 4 (or 3, I don't remeber), and there I see: "Pane is dead".
'pane is dead' is an interesting one, indicates anaconda actually died
somehow, but I don't see any indication of that in my case...I'll have
to look again.
> So going to anaconda console 1, there I saw the message:
> "if the graphical installation interface fails to start, try again
> with the inst.text bootoption to start text installation" . Pls.
> see attachments.
That's just a standard message, in fact, nothing specific to your
case. I think it's *always* printed.
For logs see: http://paste.fedoraproject.org/201182/04812314
--
Fedora release 22 (Twenty Two)
Kernel-4.0.0-0.rc4.git2.1.fc22.x86_64
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
https://www-user.rhrk.uni-kl.de/~backes
1:20 p.m.
On 03/22/2015 07:17 PM, Joachim Backes wrote:
On 03/22/2015 06:58 PM, Adam Williamson wrote:
> On Sun, 2015-03-22 at 18:31 +0100, Joachim Backes wrote:
>> On 03/22/2015 04:44 PM, Adam Williamson wrote:
>>> On Sun, 2015-03-22 at 09:30 +0100, Joachim Backes wrote:
>>>> For testing Fedora-Workstation-netinst-x86_64-22_Beta_TC4 I set
>>>> up a virtual machine in VirtualBox with a virtual 32MB video
>>>> card. After the installer has started and set up the X, rather
>>>> early it hangs up. Inspecting the logs I saw a hint: please
>>>> install F22 in
>>>> *textmode*. Trying that will install completely.
>>>>
>>>> After installation, the F22 VM runs flawlessly in a X11
>>>> environment.
>>>>
>>>> Question: is this a bug or a feature?
>>>
>>> A bug, but bugs that are VBox-specific don't necessarily rate a
>>> super high priority. What exactly is this message you're seeing in
>>> the logs?
>>>
>>
>> Hi Adam,
>>
>> this happens some seconds after I activated the spoke "select
>> installation source". Because nothing happened, I selected anaconda
>> console 4 (or 3, I don't remeber), and there I see: "Pane is
dead".
>
>
> 'pane is dead' is an interesting one, indicates anaconda actually died
> somehow, but I don't see any indication of that in my case...I'll have
> to look again.
>
>> So going to anaconda console 1, there I saw the message:
>> "if the graphical installation interface fails to start, try again
>> with the inst.text bootoption to start text installation" . Pls.
>> see attachments.
>
> That's just a standard message, in fact, nothing specific to your
> case. I think it's *always* printed.
>
For logs see: http://paste.fedoraproject.org/201182/04812314
The link represents a file: logs.tar.gz
--
Fedora release 22 (Twenty Two)
Kernel-4.0.0-0.rc4.git2.1.fc22.x86_64
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
https://www-user.rhrk.uni-kl.de/~backes
3329
days inactive
3329
days old
11 comments
3 participants
participants (3)
-
Adam Williamson -
Chris Murphy -
Joachim Backes