installing 17.04 failed..!!

Aaron Honeycutt honeycuttaaron3 at gmail.com
Sat Dec 3 01:36:14 UTC 2016


Thanks to blaze we were able to move from PyQt4 to PyQt5. So not sure if
something else changed with PyQt that caused this.

On Dec 2, 2016 8:28 PM, "Walter Lapchynski" <wxl at ubuntu.com> wrote:

> That looks like a ubiquity problem, specific as it relates to partitioning.
>
> Looking at the code, there's a self.emit() [SIGNAL][1]. Looking at the way
> [emit][2] is supposed to work, there should be a self.connect() to the
> SIGNAL (in this case, dataChanged()). Interestingly there's no mention of
> "dataChanged" anywhere in the entirety of the code base. The current code
> there is from [2012][3] and even then it was just changed to meet with
> pep8. So I'm not sure if either I don't understand PyQt (quite possible) or
> if something went missing. I don't see anything obvious in the commit
> messages, even the [porting to PyQt5][4].
>
> Dutch, it would be interesting to see if this is reproducible. Please give
> me the exact steps. Thanks!
>
> [1]: https://bazaar.launchpad.net/~ubuntu-installer/ubiquity/
> trunk/view/head:/ubiquity/frontend/kde_components/PartitionModel.py#L67
> [2]: https://wiki.python.org/moin/PyQt/Threading%2C_Signals_and_Slots
> [3]: https://bazaar.launchpad.net/~ubuntu-installer/
> ubiquity/trunk/revision/5562
> [4]: https://bazaar.launchpad.net/~ubuntu-installer/
> ubiquity/trunk/revision/6490
>
> On Fri, Dec 2, 2016 at 4:31 PM, Valorie Zimmerman <
> valorie.zimmerman at gmail.com> wrote:
>
>> On Wed, Nov 2, 2016 at 8:50 AM, Dutch Glory <dutch.glory at yahoo.com>
>> wrote:
>> >
>> > with creating/formating partitions  ended with crash...
>> >
>> > Traceback (most recent call last):
>> >
>> > File "/usr/lib/ubiquity/ubiquity/frontend/kde_components/Partitio
>> nModel.py",
>> >
>> > line 67, in setData self.emit (AttributeError: 'PartitionModel' object
>> has no attribute 'emit'
>>
>> When I upgraded to Zesty, I already had a boot problem that Zesty
>> didn't cure. So I added back a problematic PPA and then ppa-purged it,
>> which did cure my boot problem.
>>
>> It sounds like you experienced an entirely different issue, Dutch
>> Glory. Have you solved it yet?
>>
>> Valorie
>>
>> --
>> http://about.me/valoriez
>>
>> --
>> kubuntu-devel mailing list
>> kubuntu-devel at lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> an/listinfo/kubuntu-devel
>>
>
>
>
> --
>        @wxl | polka.bike
> C563 CAC5 8BE1 2F22 A49D
> 68F6 8B57 A48B C4F2 051A
>
> --
> kubuntu-devel mailing list
> kubuntu-devel at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/kubuntu-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/kubuntu-devel/attachments/20161202/d3755623/attachment.html>


More information about the kubuntu-devel mailing list