Fedora 16 Beta VNC install works, Fedora 17 does not (IBM Power 285)

[Timo Schoeler]

On 07/02/2012 03:35 PM, thus Dan Horák spake:
> Dan Horák píše v Po 02. 07. 2012 v 15:18 +0200:
>> Karsten Hopp píše v Po 02. 07. 2012 v 15:10 +0200:
>>> Am 02.07.2012 09:46, schrieb Timo Schoeler:
>>>> Hi,
>>>>
>>>> I just double verified following issue:
>>>>
>>>> * Installing Fedora 16 ppc64 on my Power 285 (connected via
>>>> serial, then booting 'linux vnc') using VNC runs smoothly
>>>>
>>>> * Trying the same using Fedora 17 ISO fails
>>>>
>>>> It seems as if the Network Manager fails on Fedora 17 and
>>>> causes anaconda's vncS.startServer() to bark.
>>>>
>>>> Is that a known issue? Should I file a bug record for this?
>>>>
>>>> Cheers,
>>>>
>>>> Timo
>>>>
>>>> .......
>>>>
>>>> 07:52:41 Starting VNC... Traceback (most recent call last):
>>>> File "/usr/sbin/anaconda", line 804, in<module>
>>>> setupDisplay(anaconda, opts) File "/usr/sbin/anaconda", line
>>>> 587, in setupDisplay runVNC(vncS) File "/usr/sbin/anaconda",
>>>> line 331, in runVNC vncS.startServer() File
>>>> "/usr/lib64/python2.7/site-packages/pyanaconda/vnc.py", line
>>>> 190, in startServer self.initialize() File
>>>> "/usr/lib64/python2.7/site-packages/pyanaconda/vnc.py", line
>>>> 113, in initialize if self.ip.find(':') != -1: AttributeError:
>>>> 'NoneType' object has no attribute 'find'
>>>> EPOW<0x64400400000006c 0x0 0x0> ____
>>>
>>>
>>> Yes, please file a bugzilla against anaconda
>>
>> I remember seeing this on s390x (there should be already a bugzilla
>> for it) and quick search discovered also
>> https://bugzilla.redhat.com/show_bug.cgi?id=832510
>
> and https://bugzilla.redhat.com/show_bug.cgi?id=809109 is the s390x
> bug

Hi,

sorry for the noise; I didn't think of a regression like thing to happen
here and thus didn't search bugzilla for this issue. Thanks for
enlightening me.

> Dan

Timo