Re: 13.10 daily image - Unity not launching after upgrade
Thanks, Nicholas and Phil. I am not using virtualbox. I have two test environments - one is saucy-daily-guest image in kvm. Other is a bare metal installation running alongside my 12.10 main desktop on a different partition. I was getting these errors when trying to refresh daily build using apt-get update and apt-get upgrade. Yesterday I was able to download latest good zsync (i think it is friday's image) from a location with faster connection, burned and reinstalled on my test partition. So I am good to continue my tests for now. It will be a problem if I get the same error after the next apt-get upgrade. Another question in this regard - does the display engine switch over to mir automatically after an apt-get upgrade? Or is it a user initiated task? Is there any command to show which graphics engine is currently running? Thanks Vasudevan Kottilil On Mon, Jul 15, 2013 at 9:51 AM, Phill Whiteside wrote: > Following on from what Nicholas said, when upgrading a test ISO, please be > aware of possibility of the upgrade not being fully sync'd and asking to > remove things, more details can be found at > http://ubuntuforums.org/showthread.php?t=1343434 > > Regards, > > Phill. > > > On 15 July 2013 16:40, Nicholas Skaggs wrote: > >> Vasudevan, this is in a virtualbox image right? And your using the >> 64-bit daily saucy image? Can you give us anymore details about your setup >> that might help? If your encountering issues, you can workaround them a >> couple ways. >> >> 1) Use a non-unity desktop enviroment. If something in unity is broken, >> use lxde, xfce, or something else in the interim. >> 2) Stay on an older image and don't upgrade until your bug is fixed. Make >> sure you file it, but if your using a vm, you should be able to clone it so >> you have a working machine that you can use and a spare test version to >> check and track progress on the bug preventing you from upgrading. >> >> Nicholas >> >> >> On 07/12/2013 06:10 PM, Vasudevan Kottilil wrote: >> >> Thanks, Phil; Tried update/upgrade again today and still can not boot/log >> into 13.10 after upgrade. During upgrade, saw a bunch of errors like these >> "(gtk-update-icon-cache-3.0:5767): GdkPixbuf-WARNING **: Cannot open >> pixbuf loader module file >> '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such >> file or directory >> This likely means that your installation is broken." >> Than I reinstalled the older image from dvd and did an >> update/upgrade;got the same errors. >> Vasudevan Kottilil >> On Fri, Jul 12, 2013 at 9:18 AM, Phill Whiteside wrote: >> >>> Hi, >>> >>> update & upgrade will indeed up date an installed system, if you want >>> to refresh your ISO for installation then use zsync [1]. >>> >>> Regards, >>> >>> Phill. >>> 1. >>> https://wiki.ubuntu.com/Testing/Activities/Classroom/Saucy#Introduction_to_QA_.2BAC8_Testing >>> >>> On 12 July 2013 17:15, Vasudevan Kottilil wrote: >>> >>>> As a follow up, do we have to download new iso and re install to >>>> reflect the change over from unity to mir? Usually I apt-get upgrade to >>>> refresh the daily image. >>>> Thanks, >>>> Vasudevan Kottilil >>>> >>>> >>>> On Tue, Jul 9, 2013 at 4:08 PM, Vasudevan Kottilil < >>>> vasudeva...@gmail.com> wrote: >>>> >>>>> Unity shell is not launching after login screen. >>>>> Tried these steps and still not working - >>>>> unity --reset-icons -> got a message saying that another widow manager >>>>> is already running on screen 0 and froze afterwards. >>>>> Tried to enable using ccsm and does not work. >>>>> >>>>> Anyone else seeing similar issues? >>>>> >>>>> Thanks, >>>>> Vasudevan Kottilil >>>>> >>>> >>>> >>>> -- >>>> Ubuntu-quality mailing list >>>> Ubuntu-quality@lists.ubuntu.com >>>> Modify settings or unsubscribe at: >>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality >>>> >>>> -- >>>> <https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality> >>>> https://wiki.ubuntu.com/phillw >>> >>> >> >> >> >> > > > -- > https://wiki.ubuntu.com/phillw > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: 13.10 daily image - Unity not launching after upgrade
Thanks, Phil; Tried update/upgrade again today and still can not boot/log into 13.10 after upgrade. During upgrade, saw a bunch of errors like these "(gtk-update-icon-cache-3.0:5767): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken." Than I reinstalled the older image from dvd and did an update/upgrade;got the same errors. Vasudevan Kottilil On Fri, Jul 12, 2013 at 9:18 AM, Phill Whiteside wrote: > Hi, > > update & upgrade will indeed up date an installed system, if you want to > refresh your ISO for installation then use zsync [1]. > > Regards, > > Phill. > 1. > https://wiki.ubuntu.com/Testing/Activities/Classroom/Saucy#Introduction_to_QA_.2BAC8_Testing > > On 12 July 2013 17:15, Vasudevan Kottilil wrote: > >> As a follow up, do we have to download new iso and re install to reflect >> the change over from unity to mir? Usually I apt-get upgrade to refresh the >> daily image. >> Thanks, >> Vasudevan Kottilil >> >> >> On Tue, Jul 9, 2013 at 4:08 PM, Vasudevan Kottilil > > wrote: >> >>> Unity shell is not launching after login screen. >>> Tried these steps and still not working - >>> unity --reset-icons -> got a message saying that another widow manager >>> is already running on screen 0 and froze afterwards. >>> Tried to enable using ccsm and does not work. >>> >>> Anyone else seeing similar issues? >>> >>> Thanks, >>> Vasudevan Kottilil >>> >> >> >> -- >> Ubuntu-quality mailing list >> Ubuntu-quality@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality >> >> -- >> <https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality> >> https://wiki.ubuntu.com/phillw > > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: 13.10 daily image - Unity not launching after upgrade
As a follow up, do we have to download new iso and re install to reflect the change over from unity to mir? Usually I apt-get upgrade to refresh the daily image. Thanks, Vasudevan Kottilil On Tue, Jul 9, 2013 at 4:08 PM, Vasudevan Kottilil wrote: > Unity shell is not launching after login screen. > Tried these steps and still not working - > unity --reset-icons -> got a message saying that another widow manager is > already running on screen 0 and froze afterwards. > Tried to enable using ccsm and does not work. > > Anyone else seeing similar issues? > > Thanks, > Vasudevan Kottilil > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
13.10 daily image - Unity not launching after upgrade
Unity shell is not launching after login screen. Tried these steps and still not working - unity --reset-icons -> got a message saying that another widow manager is already running on screen 0 and froze afterwards. Tried to enable using ccsm and does not work. Anyone else seeing similar issues? Thanks, Vasudevan Kottilil -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Autopilot GTK Fixes!
Thanks Martin and thank you Nicholas for sharing the good news. Will start running the existing scripts and also add new ones for this cycle. So all we need to do is just update and upgrade the daily image along with autopilot coming from ppa:autopilot/ppa? Vasudevan Kottilil On Tue, Jun 25, 2013 at 10:09 AM, Nicholas Skaggs < nicholas.ska...@canonical.com> wrote: > Martin Pitt (pitti) has been fixing up the autopilot-gtk module by > allowing more objects to be introspected, enhancing the testsuite for > autopilot-gtk and fixing up longstanding bugs. This should make it easier > to write autopilot tests for gtk apps like our work in the > ubuntu-autopilot-tests project. > > In other words, Martin wants to make it easier for us to write autopilot > tests for gtk applications without the bugs and heartache we've sometimes > suffered! > > Martin is asking us for bugs, so let's make sure our current issues are > documented! Dan, Carla, Vasudevan, et la -- I know we've filed bugs in the > past. Let's make sure any specific issues we found/know about are filed > specifically against the autopilot-gtk module. > > https://bugs.launchpad.net/**autopilot-gtk<https://bugs.launchpad.net/autopilot-gtk> > > This includes the issue with shotwell, the introspection troubles with > nautilus, the issues with selecting a directory in archive manager, etc, > etc. Anything else you can think of or have found :-) > > Let's get'em filed and have Martin fix them. A huge thank you to Martin > for helping out. This should allow us to take the tests to the next level > so to speak :-) > > Cheers! > > Nicholas > > -- > Ubuntu-quality mailing list > Ubuntu-quality@lists.ubuntu.**com > Modify settings or unsubscribe at: https://lists.ubuntu.com/** > mailman/listinfo/ubuntu-**quality<https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality> > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Update on porting autopilot tests to 1.3
For introspection what is the best way to figure out which id/name
corresponds to which button/icon/child window? for example - using
autopilot vis how to determine the id/name for the right side panel where
you right click inside the nautilus app to create new folder/doc etc?
Thanks.
Vasudevan Kottilil
On Fri, Jun 7, 2013 at 5:29 PM, Vasudevan Kottilil wrote:
> Thanks Nicholas. Understood. Initially I assumed that proxy object itself
> would be a handle to the main/top level window for the app that is launched.
> Vasu
>
>
> On Fri, Jun 7, 2013 at 3:11 PM, Nicholas Skaggs <
> nicholas.ska...@canonical.com> wrote:
>
>> Vasudeven, self.app is not an object. Have a look at some of the other
>> tests in the tree to see some examples of things. You use select_single and
>> select_multiple to grab dbus objects. Those can be moved to, clicked, etc.
>> Make sense?
>>
>> Nicholas
>>
>>
>> On 06/06/2013 10:01 PM, Vasudevan Kottilil wrote:
>>
>> Tried the changes and still seeing errors?
>> self.app is proxy returned from launch_test_application.
>> self.mouse.move_to_object(self.app)
>> ValueError: Object '> 0x1a24b50>' does not have any recognised position attributes
>>
>> On Thu, Jun 6, 2013 at 2:21 PM, Vasudevan Kottilil > > wrote:
>>
>>> Thanks Nicholas, I can see NautilusDesktopWindow with GtkGrid, GtkPaned
>>> and NautilusToolbar objects under that. Let me give it a try and get back
>>> to you. Testcase for connecting to server will be challenging...
>>> Vasu
>>>
>>> Vasudevan Kottilil
>>>
>>> On Thu, Jun 6, 2013 at 2:04 PM, Nicholas Skaggs <
>>> nicholas.ska...@canonical.com> wrote:
>>>
>>>> Vasudevan, the autopilot folks have a solution for us. Check this out:
>>>>
>>>> http://pastebin.ubuntu.com/5740039/
>>>>
>>>> Basically if we close down nautilus using the "nautilus -q" command
>>>> first, we can introspect nautilus. So this works for example:
>>>>
>>>> nautilus -q
>>>> autopilot launch nautilus
>>>> autopilot vis
>>>>
>>>> See the paste for incorporating the idea into the test. Good luck!
>>>>
>>>> Nicholas
>>>>
>>>>
>>>> On 05/31/2013 03:54 AM, Vasudevan Kottilil wrote:
>>>>
>>>> Hi Nicholas,
>>>> Thanks - still getting errors within my dev env. Based on brief
>>>> conversation earlier on irc, I installed autopilot on vm from
>>>> ppa:autopilot/ppa. Is this the correct version for 1.3?
>>>> Got the latest version of test_nautilus from trunk and tried to run it
>>>> 'as is'. This is what I am getting now
>>>>
>>>> Loading tests from: /home/test/autopilot
>>>>
>>>> Tests running...
>>>> ==
>>>> ERROR: tests.test_nautilus.NautilusTests.test_create_a_folder
>>>> --
>>>> _StringException: traceback-1: {{{
>>>> Traceback (most recent call last):
>>>> File "/home/test/autopilot/tests/test_nautilus.py", line 32, in
>>>> test_create_a_folder
>>>> self.keyboard.press_and_release("Ctrl+l")
>>>> File "/usr/lib/python2.7/dist-packages/autopilot/testcase.py", line
>>>> 158, in keyboard
>>>> self.addCleanup(self._kb.cleanup)
>>>> AttributeError: 'Keyboard' object has no attribute 'cleanup'
>>>> }}}
>>>>
>>>> Traceback (most recent call last):
>>>> File "/usr/lib/python2.7/dist-packages/autopilot/utilities.py", line
>>>> 242, in action_on_test_start
>>>> obj.on_test_start(test_instance)
>>>> File "/usr/lib/python2.7/dist-packages/autopilot/globals.py", line
>>>> 108, in on_test_start
>>>> if _video_logger._enable_recording:
>>>> AttributeError: '_VideoLogger' object has no attribute
>>>> '_enable_recording'
>>>>
>>>> Ran 1 test in 1.284s
>>>> FAILED (failures=1)
>>>>
>>>> I still have issues with terminal display inside the vm and it is not
>>>> displaying cursor and commands typed with in it. Was able to work around
>>>> that by using a uxterm. Since some of you are able to execute these
>>>> scripts
Re: Update on porting autopilot tests to 1.3
Porting information is available here :
http://unity.ubuntu.com/autopilot/index.html
On Fri, Jun 7, 2013 at 5:30 PM, Samuel Gabbay wrote:
> I dont get this porting buissness
>
> Envoyé de mon iPod
>
> Le 2013-06-07 à 08:29 PM, "Vasudevan Kottilil" a
> écrit :
>
> Thanks Nicholas. Understood. Initially I assumed that proxy object itself
> would be a handle to the main/top level window for the app that is launched.
> Vasu
>
> On Fri, Jun 7, 2013 at 3:11 PM, Nicholas Skaggs <
> nicholas.ska...@canonical.com> wrote:
>
>> Vasudeven, self.app is not an object. Have a look at some of the other
>> tests in the tree to see some examples of things. You use select_single and
>> select_multiple to grab dbus objects. Those can be moved to, clicked, etc.
>> Make sense?
>>
>> Nicholas
>>
>>
>> On 06/06/2013 10:01 PM, Vasudevan Kottilil wrote:
>>
>> Tried the changes and still seeing errors?
>> self.app is proxy returned from launch_test_application.
>> self.mouse.move_to_object(self.app)
>> ValueError: Object '> 0x1a24b50>' does not have any recognised position attributes
>>
>> On Thu, Jun 6, 2013 at 2:21 PM, Vasudevan Kottilil > > wrote:
>>
>>> Thanks Nicholas, I can see NautilusDesktopWindow with GtkGrid, GtkPaned
>>> and NautilusToolbar objects under that. Let me give it a try and get back
>>> to you. Testcase for connecting to server will be challenging...
>>> Vasu
>>>
>>> Vasudevan Kottilil
>>>
>>> On Thu, Jun 6, 2013 at 2:04 PM, Nicholas Skaggs <
>>> nicholas.ska...@canonical.com> wrote:
>>>
>>>> Vasudevan, the autopilot folks have a solution for us. Check this out:
>>>>
>>>> http://pastebin.ubuntu.com/5740039/
>>>>
>>>> Basically if we close down nautilus using the "nautilus -q" command
>>>> first, we can introspect nautilus. So this works for example:
>>>>
>>>> nautilus -q
>>>> autopilot launch nautilus
>>>> autopilot vis
>>>>
>>>> See the paste for incorporating the idea into the test. Good luck!
>>>>
>>>> Nicholas
>>>>
>>>>
>>>> On 05/31/2013 03:54 AM, Vasudevan Kottilil wrote:
>>>>
>>>> Hi Nicholas,
>>>> Thanks - still getting errors within my dev env. Based on brief
>>>> conversation earlier on irc, I installed autopilot on vm from
>>>> ppa:autopilot/ppa. Is this the correct version for 1.3?
>>>> Got the latest version of test_nautilus from trunk and tried to run it
>>>> 'as is'. This is what I am getting now
>>>>
>>>> Loading tests from: /home/test/autopilot
>>>>
>>>> Tests running...
>>>> ==
>>>> ERROR: tests.test_nautilus.NautilusTests.test_create_a_folder
>>>> --
>>>> _StringException: traceback-1: {{{
>>>> Traceback (most recent call last):
>>>> File "/home/test/autopilot/tests/test_nautilus.py", line 32, in
>>>> test_create_a_folder
>>>> self.keyboard.press_and_release("Ctrl+l")
>>>> File "/usr/lib/python2.7/dist-packages/autopilot/testcase.py", line
>>>> 158, in keyboard
>>>> self.addCleanup(self._kb.cleanup)
>>>> AttributeError: 'Keyboard' object has no attribute 'cleanup'
>>>> }}}
>>>>
>>>> Traceback (most recent call last):
>>>> File "/usr/lib/python2.7/dist-packages/autopilot/utilities.py", line
>>>> 242, in action_on_test_start
>>>> obj.on_test_start(test_instance)
>>>> File "/usr/lib/python2.7/dist-packages/autopilot/globals.py", line
>>>> 108, in on_test_start
>>>> if _video_logger._enable_recording:
>>>> AttributeError: '_VideoLogger' object has no attribute
>>>> '_enable_recording'
>>>>
>>>> Ran 1 test in 1.284s
>>>> FAILED (failures=1)
>>>>
>>>> I still have issues with terminal display inside the vm and it is not
>>>> displaying cursor and commands typed with in it. Was able to work around
>>>> that by using a uxterm. Since some of you are able to execute these
>>>> scripts with 1.3, it looks like some environment issues at my end...
>>
Re: Update on porting autopilot tests to 1.3
Thanks Nicholas. Understood. Initially I assumed that proxy object itself
would be a handle to the main/top level window for the app that is launched.
Vasu
On Fri, Jun 7, 2013 at 3:11 PM, Nicholas Skaggs <
nicholas.ska...@canonical.com> wrote:
> Vasudeven, self.app is not an object. Have a look at some of the other
> tests in the tree to see some examples of things. You use select_single and
> select_multiple to grab dbus objects. Those can be moved to, clicked, etc.
> Make sense?
>
> Nicholas
>
>
> On 06/06/2013 10:01 PM, Vasudevan Kottilil wrote:
>
> Tried the changes and still seeing errors?
> self.app is proxy returned from launch_test_application.
> self.mouse.move_to_object(self.app)
> ValueError: Object ' 0x1a24b50>' does not have any recognised position attributes
>
> On Thu, Jun 6, 2013 at 2:21 PM, Vasudevan Kottilil
> wrote:
>
>> Thanks Nicholas, I can see NautilusDesktopWindow with GtkGrid, GtkPaned
>> and NautilusToolbar objects under that. Let me give it a try and get back
>> to you. Testcase for connecting to server will be challenging...
>> Vasu
>>
>> Vasudevan Kottilil
>>
>> On Thu, Jun 6, 2013 at 2:04 PM, Nicholas Skaggs <
>> nicholas.ska...@canonical.com> wrote:
>>
>>> Vasudevan, the autopilot folks have a solution for us. Check this out:
>>>
>>> http://pastebin.ubuntu.com/5740039/
>>>
>>> Basically if we close down nautilus using the "nautilus -q" command
>>> first, we can introspect nautilus. So this works for example:
>>>
>>> nautilus -q
>>> autopilot launch nautilus
>>> autopilot vis
>>>
>>> See the paste for incorporating the idea into the test. Good luck!
>>>
>>> Nicholas
>>>
>>>
>>> On 05/31/2013 03:54 AM, Vasudevan Kottilil wrote:
>>>
>>> Hi Nicholas,
>>> Thanks - still getting errors within my dev env. Based on brief
>>> conversation earlier on irc, I installed autopilot on vm from
>>> ppa:autopilot/ppa. Is this the correct version for 1.3?
>>> Got the latest version of test_nautilus from trunk and tried to run it
>>> 'as is'. This is what I am getting now
>>>
>>> Loading tests from: /home/test/autopilot
>>>
>>> Tests running...
>>> ==
>>> ERROR: tests.test_nautilus.NautilusTests.test_create_a_folder
>>> --
>>> _StringException: traceback-1: {{{
>>> Traceback (most recent call last):
>>> File "/home/test/autopilot/tests/test_nautilus.py", line 32, in
>>> test_create_a_folder
>>> self.keyboard.press_and_release("Ctrl+l")
>>> File "/usr/lib/python2.7/dist-packages/autopilot/testcase.py", line
>>> 158, in keyboard
>>> self.addCleanup(self._kb.cleanup)
>>> AttributeError: 'Keyboard' object has no attribute 'cleanup'
>>> }}}
>>>
>>> Traceback (most recent call last):
>>> File "/usr/lib/python2.7/dist-packages/autopilot/utilities.py", line
>>> 242, in action_on_test_start
>>> obj.on_test_start(test_instance)
>>> File "/usr/lib/python2.7/dist-packages/autopilot/globals.py", line
>>> 108, in on_test_start
>>> if _video_logger._enable_recording:
>>> AttributeError: '_VideoLogger' object has no attribute
>>> '_enable_recording'
>>>
>>> Ran 1 test in 1.284s
>>> FAILED (failures=1)
>>>
>>> I still have issues with terminal display inside the vm and it is not
>>> displaying cursor and commands typed with in it. Was able to work around
>>> that by using a uxterm. Since some of you are able to execute these
>>> scripts with 1.3, it looks like some environment issues at my end...
>>> Vasudevan
>>>
>>>
>>> On Thu, May 30, 2013 at 7:51 AM, Nicholas Skaggs <
>>> nicholas.ska...@canonical.com> wrote:
>>>
>>>> Vasudevan, there is a basic nautilus testcase (very basic!) that is
>>>> now in the production branch. Can't wait to see you expand it to test more
>>>> :-)
>>>>
>>>> Vasudevan, sounds like you want to use a tool called testdrive:
>>>>
>>>> https://wiki.ubuntu.com/UsingDevelopmentReleases
>>>> http://www.youtube.com/watch?v=JGZF6UHhl4I
>>>>
>>>> Your workflow is exactly what happe
Re: Update on porting autopilot tests to 1.3
Tried the changes and still seeing errors?
self.app is proxy returned from launch_test_application.
self.mouse.move_to_object(self.app)
ValueError: Object '' does not have any recognised position attributes
On Thu, Jun 6, 2013 at 2:21 PM, Vasudevan Kottilil wrote:
> Thanks Nicholas, I can see NautilusDesktopWindow with GtkGrid, GtkPaned
> and NautilusToolbar objects under that. Let me give it a try and get back
> to you. Testcase for connecting to server will be challenging...
> Vasu
>
> Vasudevan Kottilil
>
> On Thu, Jun 6, 2013 at 2:04 PM, Nicholas Skaggs <
> nicholas.ska...@canonical.com> wrote:
>
>> Vasudevan, the autopilot folks have a solution for us. Check this out:
>>
>> http://pastebin.ubuntu.com/5740039/
>>
>> Basically if we close down nautilus using the "nautilus -q" command
>> first, we can introspect nautilus. So this works for example:
>>
>> nautilus -q
>> autopilot launch nautilus
>> autopilot vis
>>
>> See the paste for incorporating the idea into the test. Good luck!
>>
>> Nicholas
>>
>>
>> On 05/31/2013 03:54 AM, Vasudevan Kottilil wrote:
>>
>> Hi Nicholas,
>> Thanks - still getting errors within my dev env. Based on brief
>> conversation earlier on irc, I installed autopilot on vm from
>> ppa:autopilot/ppa. Is this the correct version for 1.3?
>> Got the latest version of test_nautilus from trunk and tried to run it
>> 'as is'. This is what I am getting now
>>
>> Loading tests from: /home/test/autopilot
>>
>> Tests running...
>> ==
>> ERROR: tests.test_nautilus.NautilusTests.test_create_a_folder
>> --
>> _StringException: traceback-1: {{{
>> Traceback (most recent call last):
>> File "/home/test/autopilot/tests/test_nautilus.py", line 32, in
>> test_create_a_folder
>> self.keyboard.press_and_release("Ctrl+l")
>> File "/usr/lib/python2.7/dist-packages/autopilot/testcase.py", line
>> 158, in keyboard
>> self.addCleanup(self._kb.cleanup)
>> AttributeError: 'Keyboard' object has no attribute 'cleanup'
>> }}}
>>
>> Traceback (most recent call last):
>> File "/usr/lib/python2.7/dist-packages/autopilot/utilities.py", line
>> 242, in action_on_test_start
>> obj.on_test_start(test_instance)
>> File "/usr/lib/python2.7/dist-packages/autopilot/globals.py", line 108,
>> in on_test_start
>> if _video_logger._enable_recording:
>> AttributeError: '_VideoLogger' object has no attribute '_enable_recording'
>>
>> Ran 1 test in 1.284s
>> FAILED (failures=1)
>>
>> I still have issues with terminal display inside the vm and it is not
>> displaying cursor and commands typed with in it. Was able to work around
>> that by using a uxterm. Since some of you are able to execute these
>> scripts with 1.3, it looks like some environment issues at my end...
>> Vasudevan
>>
>>
>> On Thu, May 30, 2013 at 7:51 AM, Nicholas Skaggs <
>> nicholas.ska...@canonical.com> wrote:
>>
>>> Vasudevan, there is a basic nautilus testcase (very basic!) that is
>>> now in the production branch. Can't wait to see you expand it to test more
>>> :-)
>>>
>>> Vasudevan, sounds like you want to use a tool called testdrive:
>>>
>>> https://wiki.ubuntu.com/UsingDevelopmentReleases
>>> http://www.youtube.com/watch?v=JGZF6UHhl4I
>>>
>>> Your workflow is exactly what happens in the canonical QA lab everyday.
>>> The autopilot tests we're writing will be a part of that. So for your
>>> testing however, you don't need to install from an image everyday (unless
>>> you want to test installation, in which case use testdrive above to help!).
>>> So setup your vm and simply update on a regular basis, just like your
>>> stable version of ubuntu. Your installation will track the development
>>> release. You can then use it to develop autopilot testcases or do manual
>>> testing.
>>>
>>> Does that help / make sense?
>>>
>>> Nicholas
>>>
>>>
>>> On 05/29/2013 06:55 PM, Vasudevan Kottilil wrote:
>>>
>>> Hi Nicholas, Dan,
>>> I am working on the nautilus script and was hoping to make some progress
>>> by now but running into many issues(sorry, could not work during the long
>>> weekend).
&
Re: Update on porting autopilot tests to 1.3
Thanks Nicholas, I can see NautilusDesktopWindow with GtkGrid, GtkPaned and
NautilusToolbar objects under that. Let me give it a try and get back to
you. Testcase for connecting to server will be challenging...
Vasu
Vasudevan Kottilil
On Thu, Jun 6, 2013 at 2:04 PM, Nicholas Skaggs <
nicholas.ska...@canonical.com> wrote:
> Vasudevan, the autopilot folks have a solution for us. Check this out:
>
> http://pastebin.ubuntu.com/5740039/
>
> Basically if we close down nautilus using the "nautilus -q" command first,
> we can introspect nautilus. So this works for example:
>
> nautilus -q
> autopilot launch nautilus
> autopilot vis
>
> See the paste for incorporating the idea into the test. Good luck!
>
> Nicholas
>
>
> On 05/31/2013 03:54 AM, Vasudevan Kottilil wrote:
>
> Hi Nicholas,
> Thanks - still getting errors within my dev env. Based on brief
> conversation earlier on irc, I installed autopilot on vm from
> ppa:autopilot/ppa. Is this the correct version for 1.3?
> Got the latest version of test_nautilus from trunk and tried to run it 'as
> is'. This is what I am getting now
>
> Loading tests from: /home/test/autopilot
>
> Tests running...
> ==
> ERROR: tests.test_nautilus.NautilusTests.test_create_a_folder
> --
> _StringException: traceback-1: {{{
> Traceback (most recent call last):
> File "/home/test/autopilot/tests/test_nautilus.py", line 32, in
> test_create_a_folder
> self.keyboard.press_and_release("Ctrl+l")
> File "/usr/lib/python2.7/dist-packages/autopilot/testcase.py", line 158,
> in keyboard
> self.addCleanup(self._kb.cleanup)
> AttributeError: 'Keyboard' object has no attribute 'cleanup'
> }}}
>
> Traceback (most recent call last):
> File "/usr/lib/python2.7/dist-packages/autopilot/utilities.py", line
> 242, in action_on_test_start
> obj.on_test_start(test_instance)
> File "/usr/lib/python2.7/dist-packages/autopilot/globals.py", line 108,
> in on_test_start
> if _video_logger._enable_recording:
> AttributeError: '_VideoLogger' object has no attribute '_enable_recording'
>
> Ran 1 test in 1.284s
> FAILED (failures=1)
>
> I still have issues with terminal display inside the vm and it is not
> displaying cursor and commands typed with in it. Was able to work around
> that by using a uxterm. Since some of you are able to execute these
> scripts with 1.3, it looks like some environment issues at my end...
> Vasudevan
>
>
> On Thu, May 30, 2013 at 7:51 AM, Nicholas Skaggs <
> nicholas.ska...@canonical.com> wrote:
>
>> Vasudevan, there is a basic nautilus testcase (very basic!) that is now
>> in the production branch. Can't wait to see you expand it to test more :-)
>>
>> Vasudevan, sounds like you want to use a tool called testdrive:
>>
>> https://wiki.ubuntu.com/UsingDevelopmentReleases
>> http://www.youtube.com/watch?v=JGZF6UHhl4I
>>
>> Your workflow is exactly what happens in the canonical QA lab everyday.
>> The autopilot tests we're writing will be a part of that. So for your
>> testing however, you don't need to install from an image everyday (unless
>> you want to test installation, in which case use testdrive above to help!).
>> So setup your vm and simply update on a regular basis, just like your
>> stable version of ubuntu. Your installation will track the development
>> release. You can then use it to develop autopilot testcases or do manual
>> testing.
>>
>> Does that help / make sense?
>>
>> Nicholas
>>
>>
>> On 05/29/2013 06:55 PM, Vasudevan Kottilil wrote:
>>
>> Hi Nicholas, Dan,
>> I am working on the nautilus script and was hoping to make some progress
>> by now but running into many issues(sorry, could not work during the long
>> weekend).
>> I had downloaded a daily build image for saucy-desktop-amd64.iso on 05/23
>> and tried to create a guest image using the following command: (host is
>> running 12.10 desktop)
>>
>> virt-install --connect qemu:///system --virt-type kvm --name
>> saucy-alpha-vm --ram 4096 --disk
>> path=/var/lib/libvirt/images/saucy-desktop-vm,size=30 --graphics vnc
>> --location /home/vkottilil/Downloads/saucy-desktop-amd64.iso and it throws
>> an error
>> Starting install...
>> ERRORCould not find an installable distribution at
>> '/home/vkottilil/Downloads/saucy-desktop-amd64.iso'
>> The location must be the roo
Re: This week in QA -- June 4th Hackfest, Classroom Sessions and Cadence Testing
Hi,
Here are some updates - still working on nautilus test case. It looks as if
there are several changes between nautilus in 12.10 and later versions.
Running into issues when trying to move mouse cursor to execute right
clicks with in the child window. Tried using both move_to_object and
geometry and got these errors.
Please let me know if I am missing some steps here or possible workarounds.
Basic scenario to create empty doc in saucy:
launch app
browse to /tmp
generate a tmp file name
move cursor to center of window
right click, select New Document/Empty Document
Loading tests from: /home/test/autopilot
Tests running...
==
ERROR: tests.test_nautilus.NautilusTests.test_create_empty_doc
--
_StringException: Traceback (most recent call last):
File "/home/test/autopilot/tests/test_nautilus.py", line 72, in
test_create_empty_doc
self.mouse.move_to_object(self.app)
File "/usr/lib/python2.7/dist-packages/autopilot/input/_X11.py", line
398, in move_to_object
raise ValueError("Object '%r' does not have any recognised position
attributes" % object_proxy)
ValueError: Object '' does not have any
recognised position attributes
Ran 1 test in 3.601s
FAILED (failures=1)
Loading tests from: /home/test/autopilot
Tests running...
==
ERROR: tests.test_nautilus.NautilusTests.test_create_empty_doc
--
_StringException: Traceback (most recent call last):
File "/home/test/autopilot/tests/test_nautilus.py", line 73, in
test_create_empty_doc
self.wc = self.app.geometry
File "/usr/lib/python2.7/dist-packages/autopilot/process/_bamf.py", line
464, in geometry
origin = GdkX11.X11Window.foreign_new_for_display(get_display(),
self._xid).get_origin()
File "/usr/lib/python2.7/dist-packages/gi/types.py", line 137, in
constructor
return info.invoke(cls, *args, **kwargs)
TypeError: argument display: Expected Gdk.Display, but got
Xlib.display.instance
Ran 1 test in 3.688s
FAILED (failures=1)
Thanks,
Vasudevan Kottilil
On Mon, Jun 3, 2013 at 8:07 AM, Nicholas Skaggs <
nicholas.ska...@canonical.com> wrote:
> I wanted to remind everyone we have another hackfest scheduled for
> tomorrow:
>
> https://wiki.ubuntu.com/QATeam/Hackfest/20130604
>
> We will continue the migration to autopilot 1.3 (very close to completion)
> as well as hack on some manual testcases too. In addition, we'll be
> attempting to hack on ubiquity using autopilot to perform automated
> installer tests. If you can't join us specifically during the hackfest,
> that's ok! There is another one scheduled for June 13th. And of course,
> ccontributions to the manual or automated test repositories are welcome
> anytime, and there's documentation to help you get started:
>
> https://wiki.ubuntu.com/QATeam/ContributingTestcases
>
> In addition I'd like to remind everyone June is our month for classroom
> sessions. For those who signed up to host a class, now is the time to slot
> in a date a time for your session;
> https://wiki.ubuntu.com/Testing/Activities/Classroom/Saucy/. Ideally we
> will have held all sessions before the end of June to middle of July :-).
>
> Finally, our remember our cadence testing is set to begin in just a couple
> weeks on June 15th. This will mark the first week for us actively testing
> saucy and it's development. To help you prepare, ensure you have a computer
> (or virtual machine) setup and running saucy to help test during the
> cadence week. If you wish, you can plan to do some image testing and then
> utilize the installation for the cadence testing as well :-). See this
> tutorial for more information:
>
> https://wiki.ubuntu.com/Testing/Cadence/Walkthrough
>
> Remember now is the time for hacking on testcases, working through new
> ideas and learning new things. As the cycle continues, more and more
> testing will be required. Take the time now to make sure our testing
> experience this cycle will be better than the last.
>
> Happy Testing!
>
> Nicholas
>
> --
> Ubuntu-quality mailing list
> Ubuntu-quality@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
>
>
--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Update on porting autopilot tests to 1.3
Hi Nicholas,
Thanks - still getting errors within my dev env. Based on brief
conversation earlier on irc, I installed autopilot on vm from
ppa:autopilot/ppa. Is this the correct version for 1.3?
Got the latest version of test_nautilus from trunk and tried to run it 'as
is'. This is what I am getting now
Loading tests from: /home/test/autopilot
Tests running...
==
ERROR: tests.test_nautilus.NautilusTests.test_create_a_folder
--
_StringException: traceback-1: {{{
Traceback (most recent call last):
File "/home/test/autopilot/tests/test_nautilus.py", line 32, in
test_create_a_folder
self.keyboard.press_and_release("Ctrl+l")
File "/usr/lib/python2.7/dist-packages/autopilot/testcase.py", line 158,
in keyboard
self.addCleanup(self._kb.cleanup)
AttributeError: 'Keyboard' object has no attribute 'cleanup'
}}}
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/autopilot/utilities.py", line 242,
in action_on_test_start
obj.on_test_start(test_instance)
File "/usr/lib/python2.7/dist-packages/autopilot/globals.py", line 108,
in on_test_start
if _video_logger._enable_recording:
AttributeError: '_VideoLogger' object has no attribute '_enable_recording'
Ran 1 test in 1.284s
FAILED (failures=1)
I still have issues with terminal display inside the vm and it is not
displaying cursor and commands typed with in it. Was able to work around
that by using a uxterm. Since some of you are able to execute these
scripts with 1.3, it looks like some environment issues at my end...
Vasudevan
On Thu, May 30, 2013 at 7:51 AM, Nicholas Skaggs <
nicholas.ska...@canonical.com> wrote:
> Vasudevan, there is a basic nautilus testcase (very basic!) that is now
> in the production branch. Can't wait to see you expand it to test more :-)
>
> Vasudevan, sounds like you want to use a tool called testdrive:
>
> https://wiki.ubuntu.com/UsingDevelopmentReleases
> http://www.youtube.com/watch?v=JGZF6UHhl4I
>
> Your workflow is exactly what happens in the canonical QA lab everyday.
> The autopilot tests we're writing will be a part of that. So for your
> testing however, you don't need to install from an image everyday (unless
> you want to test installation, in which case use testdrive above to help!).
> So setup your vm and simply update on a regular basis, just like your
> stable version of ubuntu. Your installation will track the development
> release. You can then use it to develop autopilot testcases or do manual
> testing.
>
> Does that help / make sense?
>
> Nicholas
>
>
> On 05/29/2013 06:55 PM, Vasudevan Kottilil wrote:
>
> Hi Nicholas, Dan,
> I am working on the nautilus script and was hoping to make some progress
> by now but running into many issues(sorry, could not work during the long
> weekend).
> I had downloaded a daily build image for saucy-desktop-amd64.iso on 05/23
> and tried to create a guest image using the following command: (host is
> running 12.10 desktop)
>
> virt-install --connect qemu:///system --virt-type kvm --name
> saucy-alpha-vm --ram 4096 --disk
> path=/var/lib/libvirt/images/saucy-desktop-vm,size=30 --graphics vnc
> --location /home/vkottilil/Downloads/saucy-desktop-amd64.iso and it throws
> an error
> Starting install...
> ERRORCould not find an installable distribution at
> '/home/vkottilil/Downloads/saucy-desktop-amd64.iso'
> The location must be the root directory of an install tree.
> Domain installation does not appear to have been successful.
> If it was, you can restart your domain by running:
> virsh --connect qemu:///system start saucy-alpha-vm
> otherwise, please restart your installation.
>
> What causes this error?
>
> After this, I burned the iso to dvd and from that location it was able to
> create a vm using the same tool with option --cdrom /dev/sr0 instead of
> --location.
> After launching guest, I am unable to see anything typed out in the vm's
> terminal - tried changing the profile settings with different color etc and
> still does not work.
> I can ssh from the host to the vm. Is it possible to run autopliot on the
> vm from ssh terminal - are there any x server/display options?
>
> I have heard of a totally different workflow this team is using to test
> the daily image using testdrive - any pointers to that would be great.
> Ideally it would be great if we can run a predictable set of steps similar
> to
> wget latestgood
> create vm
> spin it up
> install autopilot
> copy test scripts
> run tests
> tear down
>
> Thanks,
> Vasudevan Kottilil
>
>
Re: Update on porting autopilot tests to 1.3
Hi Nicholas, Dan, I am working on the nautilus script and was hoping to make some progress by now but running into many issues(sorry, could not work during the long weekend). I had downloaded a daily build image for saucy-desktop-amd64.iso on 05/23 and tried to create a guest image using the following command: (host is running 12.10 desktop) virt-install --connect qemu:///system --virt-type kvm --name saucy-alpha-vm --ram 4096 --disk path=/var/lib/libvirt/images/saucy-desktop-vm,size=30 --graphics vnc --location /home/vkottilil/Downloads/saucy-desktop-amd64.iso and it throws an error Starting install... ERRORCould not find an installable distribution at '/home/vkottilil/Downloads/saucy-desktop-amd64.iso' The location must be the root directory of an install tree. Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start saucy-alpha-vm otherwise, please restart your installation. What causes this error? After this, I burned the iso to dvd and from that location it was able to create a vm using the same tool with option --cdrom /dev/sr0 instead of --location. After launching guest, I am unable to see anything typed out in the vm's terminal - tried changing the profile settings with different color etc and still does not work. I can ssh from the host to the vm. Is it possible to run autopliot on the vm from ssh terminal - are there any x server/display options? I have heard of a totally different workflow this team is using to test the daily image using testdrive - any pointers to that would be great. Ideally it would be great if we can run a predictable set of steps similar to wget latestgood create vm spin it up install autopilot copy test scripts run tests tear down Thanks, Vasudevan Kottilil On Tue, May 28, 2013 at 8:21 AM, Dan Chapman wrote: > Hi everyone, > > just thought i would give a quick update on the status of porting the > autopilot test cases since the last hackfest (check out the notes > http://pad.ubuntu.com/CFXkuLR7Lb) and what is working/needs reviewing and > testing. > > *Firefox: *nskaggs completed this and is now merged to the production > branch. The test was converted to using the ProcessManager class as > introspecting firefox was not possible. > * > Evince: *has been ported to 1.3 using introspection, the test is working > good and has been proposed for merge. Currently it could still do with the > open and print dialogs being introspected, as it is still currently using > keyboard shortcuts to navigate. Also i think this test case could be > further expanded as it still misses some features that can be introspected > Currently it tests > > >- Display pdf >- Enter & Exit fullscreen >- Show & Hide sidebar >- Rotate document > > Maybe we could add tests for zoom, bookmark and presentation features? > Whats your thoughts? > > *File-Roller: *ported to 1.3 using introspection and has been proposed > for merge. It is currently using the archive created in the first test > across all the tests. So the tests are unable to be called and run > independently from each other. Could do with modifying to make each test > self contained. > > I could not find a sane way to select/choose an archive format so > currently it works with whatever your default archive is and collects the > name of the archive from the window title so can be deleted successfully. > Anyone have any ideas on accessing the items in a GtkComboBoxText control > and getting the selected item? > > *Gedit: *Letozaf has been working on this and has proposed a merge. > > *Nautilus: *Has been ported to 1.3 but unable to introspect due to > autopilot module not loading, So currently using the ProcessManager. This > test is still very basic in that it just creates and deletes a directory. > As this is probably the most used application on ubuntu it should probably > have an extensive test to match the current manual-test-case as much as > possible. > > *Shotwell: *Still to be ported to autopilot 1.3 > > *Totem: *nskaggs is working on this I think?? > > *Screenshot:* when running autopilot launch gnome-screenshot it > automatically takes a screenshot of the whole screen and loads on to the > save screenshot window. This is the same when just running gnome-screenshot > in the terminal. Is this a bug i couldnt find a bug like this. Or is this > the default behaviour when launching it from terminal? > > Also the same when lauching the application with launch_test_application() > > screenshot can be introspected but cannot get into the main window to test > taking different shots. This needs looking into further. > > *Terminal:* ported to 1.3 using ProcessManager, it would be great to be > able t
Re: Hackathon Tomorrow (May 23rd) 1200 UTC to 2000 UTC in #ubuntu-quality
Hi Nicholas,
I tried testing all the existing autopilot scripts from trunk on my dev box
running quantal 12.10 updated today morning after I pinged on the irc.
autopliot 1.3 was built after disabling lttng option. Based on initial
experience I guess I may have to create a guest image for latest build and
try again. This is what I got on my dev env.
both these appeared to go through
-test_firefox
-test_evince
tests that failed - RuntimeError:Unable to find Autopilot interface
-test_gedit
-test_nautilus
-test_shotwell
-test_totem
all these launched the respective apps and no further interactions.
Did not run test_fileroller - the app is not working (after system update);
can not create new archive of any type on my computer - this has nothing to
do with autopilot . I have a screen shot of error, can post it if required.
These are the lingering questions that I have for tomorrow's meeting:
In setUp which should be used to launch target app? What is the criteria ?
The scripts currently use one of the three:
self.launch_test_application("appname")
or
self.start_app_window("appName")
or
self.mgr = ProcessManager.create("BAMF"),
self.mgr.start_app_window("appname")
>From where or how can we get the IDs of child windows/icons/buttons/labels
etc? (in select_single etc)
These are used to select/click/enter text on target windows in several test
cases after getting a proxy object.
Thanks,
Vasudevan
Vasudevan Kottilil
On Wed, May 22, 2013 at 8:45 AM, Nicholas Skaggs <
nicholas.ska...@canonical.com> wrote:
> Ok, so it sounded like most people are going to be able to make the
> quickly scheduled Hackathon. So, without further ado, tomorrow in
> #ubuntu-quality from 1200 UTC to 2000 UTC we'll be hacking on testcases.
> Hurray!
>
> https://wiki.ubuntu.com/QATeam/Hackfest/20130523
>
> Our goals are:
>
> Re-organize the ubuntu-autopilot-tests trunk so known good tests are
> separated from those that are a work in progress
> Complete review of the manual testcases and bugs in ubuntu-manual-tests
> Migrate all the ubuntu-autopilot-tests testcases to autopilot 1.3
> Clean up the old autopilot documentation and resource links from autopilot
> 1.2 to autopilot 1.3
>
> See everyone tomorrow!
>
> Nicholas
>
> --
> Ubuntu-quality mailing list
> Ubuntu-quality@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
>
>
--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: [Autopilot-users] Update: big changes in 1.3
Is there some more documentation for starting with this tool - http://unity.ubuntu.com/autopilot/tutorial/getting_started.html appears to be a placeholder. On Thu, May 16, 2013 at 10:13 AM, Nicholas Skaggs < nicholas.ska...@canonical.com> wrote: > FYI --- > > > Original Message Subject: [Autopilot-users] Update: > big changes in 1.3 Date: Fri, 17 May 2013 05:02:16 +1200 From: Thomi > RichardsTo: > autopilot-us...@lists.launchpad.net > > Hi everyone, > > > Wow - a second email to the autopilot-users mailing list! What could > necessitate such a momentous occasion!? Only the 1.3 release of > autopilot! Read on for the details... > > > Big changes in 1.3 > === > > Autopilot 1.3 was required to make autopilot run seamlessly across all > the platforms we care about - from phones, to tablets, to desktops. This > was a reasonably large amount of work, and we're still fine tuning > things. There are two areas of changes you need to be aware of: > > First, there are API breakages between autopilot 1.2 and 1.3. This means > you will need to port your autopilot tests to autopilot 1.3 before you > can use the new autopilot goodness. Thankfully, the porting is super > easy. There's a document describing exactly what needs to be > done:http://unity.ubuntu.com/autopilot/porting/porting.html > > Second, there's been packaging changes. The python-autopilot package > still provides the core autopilot tools (both the 'autopilot' module and > the 'autopilot' test runner), but several things have been split into > separate modules: > * The 'vis' tool has been split into the python-autopilot-vis package. > The 'vis' command will not show up unless this package is installed. > * The tests for autopilot itself has been moved to the > 'python-autopilot-tests' package. Unless you want to hack on autopilot, > you probably will never need this. > > Additionally, there are now some new binary packages: > * The python-autopilot-trace package provides support for LTTNG > (https://lttng.org/). Autopilot will now emit tracepoints at the start > and end of every test, which is useful to correlate other lttng > tracepoint data with autopilot tests. > * The autopilot-touch metapackage pulls in everything you need to run > autopilot tests on the phone. > * The autopilot-desktop metapackage pulls in everything you need to run > autopilot tests on the desktop. > > Autopilot 1.3 is being released into the saucy distribution, and into > the ppa:autopilot/ppa PPA for saucy and raring. Users of older Ubuntu > releases will need to upgrade, or build their own packages from source. > > Getting Help > > > As well as this mailing list, all the autopilot developers have started > hanging out in the #ubuntu-autopilot IRC channel on freenode. If you > need timely help, that's the place to ask. Additionally, the > documentation in 1.3 is significantly better than it was in 1.2, and is > being updated daily. Check out the documentation > here:http://unity.ubuntu.com/autopilot/ > > Contributing > > > There's plenty of work left to do in autopilot 1.3, for all skill > levels. If you're keen to hack on a project that's being used across > several platforms, teams, and products, drop us a line in > #ubuntu-autopilot and we'll help you get on the right track. > > > Cheers, > > -- > Thomi Richards > > > > > > > > -- > Ubuntu-quality mailing list > Ubuntu-quality@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality > > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Server Test Results needed!
Ok. I tried the following for wlan0 edit /etc/network/interfaces - add wpa_supplicant.conf with ssid/password restart network - did not get ip Tried to connect a cable; eth0 is shown as p3p1 edit /etc/udev/rules.d/70-persistent-net.rules and add a line for p3p1 restart network - did not get an ip ethtool shows link down Any doc url for troubleshooting this? Thanks. On Wed, Apr 24, 2013 at 9:32 PM, Nicholas Skaggs < nicholas.ska...@canonical.com> wrote: > :-( Sorry to hear! It is possible, but I don't think the the alternate > installer handles this all that well. I think you have to drop to the shell > and manually start it up -- someone else surely can inform you better on > this, I trust . . . > > Nicholas > > > On 04/24/2013 11:31 PM, Vasudevan Kottilil wrote: > > Is it possible to test server image on a wireless laptop? Tried to install > and not getting an ip; tried ifup wlan0 after logging in and does not > appear to be getting it. > > On Wed, Apr 24, 2013 at 10:26 AM, Nicholas Skaggs < > nicholas.ska...@canonical.com> wrote: > >> The final day for testing is well underway. I thought I would send out >> a call for anyone who hasn't yet submitted results for image testing. If >> not, get your name in there! Download an iso and add a result! We need >> more results! I know your out there! >> >> http://iso.qa.ubuntu.com/qatracker/milestones/269/builds >> >> Specifically there is a need for people to try and run the server images >> and associated testcases. If anyone is able to test MAAS, iSCSI, or just a >> plain mailserver (the testcases cover these :-) ) please do so and add your >> result. >> >> http://iso.qa.ubuntu.com/qatracker/milestones/269/builds/42960/testcases >> >> To everyone who has tested thus far, a big thank you! We've found a few >> bugs severe enough to cause respins, so I know you've been looking hard :-) >> Please keep up the good work and continue testing as we come down to the >> wire. >> >> Nicholas >> >> P.S. If you need it, as always the wiki is your friend and guide to >> understanding the tracker; >> https://wiki.ubuntu.com/Testing/ISO/Walkthrough >> https://wiki.ubuntu.com/Testing/QATracker >> >> -- >> Ubuntu-quality mailing list >> Ubuntu-quality@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality >> >> > > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Server Test Results needed!
Is it possible to test server image on a wireless laptop? Tried to install and not getting an ip; tried ifup wlan0 after logging in and does not appear to be getting it. On Wed, Apr 24, 2013 at 10:26 AM, Nicholas Skaggs < nicholas.ska...@canonical.com> wrote: > The final day for testing is well underway. I thought I would send out a > call for anyone who hasn't yet submitted results for image testing. If not, > get your name in there! Download an iso and add a result! We need more > results! I know your out there! > > http://iso.qa.ubuntu.com/qatracker/milestones/269/builds > > Specifically there is a need for people to try and run the server images > and associated testcases. If anyone is able to test MAAS, iSCSI, or just a > plain mailserver (the testcases cover these :-) ) please do so and add your > result. > > http://iso.qa.ubuntu.com/qatracker/milestones/269/builds/42960/testcases > > To everyone who has tested thus far, a big thank you! We've found a few > bugs severe enough to cause respins, so I know you've been looking hard :-) > Please keep up the good work and continue testing as we come down to the > wire. > > Nicholas > > P.S. If you need it, as always the wiki is your friend and guide to > understanding the tracker; > https://wiki.ubuntu.com/Testing/ISO/Walkthrough > https://wiki.ubuntu.com/Testing/QATracker > > -- > Ubuntu-quality mailing list > Ubuntu-quality@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality > > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
raring - rc download url
Is there a .torrent file for final rc iso image/daily builds? Thanks much. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: raring iso beta2 - files - internal error
Ok, thanks; will try to do it manually. On Thu, Apr 18, 2013 at 3:44 PM, Brian Murray wrote: > On Thu, Apr 18, 2013 at 03:27:33PM -0700, Vasudevan Kottilil wrote: > > Did not seem to work.. It exited out of apport-cli immediately. > > > > apport-cli -c /var/crash/_usr_bin_compiz.1000.crash > > What would you like to do? Your options are: > > S: Send report (6.9 MB) > > V: View report > > K: Keep report file for sending later or copying to somewhere else > > I: Cancel and ignore future crashes of this program version > > C: Cancel > > Please choose (S/V/K/I/C): S > > Apport is no longer sending crash reports to Launchpad. > > apport (2.9.2-0ubuntu6) raring; urgency=low > > * etc/apport/crashdb.conf: Disable Launchpad crash/kernel reports for > * the > raring release. Only report to http://errors.ubuntu.com from now on. > > This normally happens shortly after Beta 2. > > -- > Brian Murray > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: raring iso beta2 - files - internal error
Did not seem to work.. It exited out of apport-cli immediately. apport-cli -c /var/crash/_usr_bin_compiz.1000.crash What would you like to do? Your options are: S: Send report (6.9 MB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): S On Thu, Apr 18, 2013 at 2:58 PM, Nicholas Skaggs < nicholas.ska...@canonical.com> wrote: > Yes it should. However you can manually trigger this again using apport > on the cli. You'll find the .crash file in your /var/crash folder. > > Nicholas > > > On 04/18/2013 05:56 PM, Vasudevan Kottilil wrote: > > Hi Nicholas, > Got the compiz crash again after clicking Files icon. I tried to send the > bug report using the automatic window that popped up and clicked 'send'. > After that nothing happened. > Is it supposed to open a launchpad instance to complete the filing? > /etc/default/apport, enabled=1 > Vasudevan > On Mon, Apr 15, 2013 at 9:25 AM, Vasudevan Kottilil > wrote: > >> Sure - I tried to send it using the automatic reporting feature - will >> try again. >> >> >> On Mon, Apr 15, 2013 at 8:25 AM, Nicholas Skaggs < >> nicholas.ska...@canonical.com> wrote: >> >>> Vaudevan, the compiz crash is something you should report. Use apport >>> and get a bug in for it. Check for duplicates while filing! :-) >>> >>> Thanks, >>> Nicholas >>> >>> >>> On 04/15/2013 11:23 AM, Vasudevan Kottilil wrote: >>> >>>> After installation, after clicking files icon, this error shows up. >>>> Ubuntu 13.04 - internal error >>>> compiz crashed with SIGSEGV in sigc::internal::slot_call0 ...etc >>>> >>>> >>>> >>> >> > > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: raring iso beta2 - files - internal error
Hi Nicholas, Got the compiz crash again after clicking Files icon. I tried to send the bug report using the automatic window that popped up and clicked 'send'. After that nothing happened. Is it supposed to open a launchpad instance to complete the filing? /etc/default/apport, enabled=1 Vasudevan On Mon, Apr 15, 2013 at 9:25 AM, Vasudevan Kottilil wrote: > Sure - I tried to send it using the automatic reporting feature - will try > again. > > > On Mon, Apr 15, 2013 at 8:25 AM, Nicholas Skaggs < > nicholas.ska...@canonical.com> wrote: > >> Vaudevan, the compiz crash is something you should report. Use apport and >> get a bug in for it. Check for duplicates while filing! :-) >> >> Thanks, >> Nicholas >> >> >> On 04/15/2013 11:23 AM, Vasudevan Kottilil wrote: >> >>> After installation, after clicking files icon, this error shows up. >>> Ubuntu 13.04 - internal error >>> compiz crashed with SIGSEGV in sigc::internal::slot_call0 ...etc >>> >>> >>> >> > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: raring iso beta2 - incomplete language support
Hi Nicholas, This is the info that I have: Some translations or writing aids available for your chosen languages are not installed yet - Details hyphen-en-us thunderbird-locale-en contents for one of the preseed files from 1304 iso cat /mnt/preseed/cli.seed # Only install the standard system and language packs. taskseltasksel/firstmultiselect d-ipkgsel/language-pack-patternsstring # No language support packages. d-ipkgsel/install-language-supportboolean false Vasudevan On Mon, Apr 15, 2013 at 9:27 AM, Vasudevan Kottilil wrote: > Yes - installed it with out internet access. > After installation, ran apt-get update and still got it. > Will try to see what all language packs got installed. > > > On Mon, Apr 15, 2013 at 8:27 AM, Nicholas Skaggs < > nicholas.ska...@canonical.com> wrote: > >> Take a look at what it is wanting to install -- what packages? Odds are >> the following happened: >> >> You installed without internet access >> The language packs it wants to install for US English aren't on the cd >> >> Now, if you figure out what language packs didn't install, we can narrow >> if they are on the image or not. If they are, it's most certainly a bug. If >> they aren't we'll have to confer with the release team about whether or not >> they should be included. I hope that makes sense! Let us know! >> >> Nicholas >> >> >> On 04/15/2013 11:20 AM, Vasudevan Kottilil wrote: >> >>> After installation, this window pops up. >>> "The language support for your selected language seems to be incomplete >>> ... etc." >>> Installation options were default - language - US English >>> Not sure if this is expected behavior or not. >>> >>> >>> >> > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: raring iso beta2 - incomplete language support
Yes - installed it with out internet access. After installation, ran apt-get update and still got it. Will try to see what all language packs got installed. On Mon, Apr 15, 2013 at 8:27 AM, Nicholas Skaggs < nicholas.ska...@canonical.com> wrote: > Take a look at what it is wanting to install -- what packages? Odds are > the following happened: > > You installed without internet access > The language packs it wants to install for US English aren't on the cd > > Now, if you figure out what language packs didn't install, we can narrow > if they are on the image or not. If they are, it's most certainly a bug. If > they aren't we'll have to confer with the release team about whether or not > they should be included. I hope that makes sense! Let us know! > > Nicholas > > > On 04/15/2013 11:20 AM, Vasudevan Kottilil wrote: > >> After installation, this window pops up. >> "The language support for your selected language seems to be incomplete >> ... etc." >> Installation options were default - language - US English >> Not sure if this is expected behavior or not. >> >> >> > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: raring iso beta2 - files - internal error
Sure - I tried to send it using the automatic reporting feature - will try again. On Mon, Apr 15, 2013 at 8:25 AM, Nicholas Skaggs < nicholas.ska...@canonical.com> wrote: > Vaudevan, the compiz crash is something you should report. Use apport and > get a bug in for it. Check for duplicates while filing! :-) > > Thanks, > Nicholas > > > On 04/15/2013 11:23 AM, Vasudevan Kottilil wrote: > >> After installation, after clicking files icon, this error shows up. >> Ubuntu 13.04 - internal error >> compiz crashed with SIGSEGV in sigc::internal::slot_call0 ...etc >> >> >> > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
ATA Disk: vendor - Seagate, out of range smart data
'SMART' data from 'Disks' app shows lot of out of range values - quantal and raring beta2 read error rate - 101,746,920 (normalized 116, threshold 6, worst 100) start/stop count - 474 (normalized 100, threshold 20, worst 100) seek error rate - 2,500,638 (normalized 63, threshold 30, worst 60) power on hours - 14 days and 3 hours ( I rebooted 2 hours ago) airflow/temperature 49 C/120 F (normalized 51, threshold 45, worst 44) - Assessment - 'Failed in the past' Does these indicate h/w problems (brand new hardware - only a few weeks old) or tool reporting issues? Thanks much. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
SODIMM DDR3 Synchronous 1600 MHz (0.6 ns) - vendor: 8502 - *BAD*gran_size,
Seeing this on both quantal and raring beta2 on a brand new laptop from system76 (gazelle pro) after my previous desktop died mysteriously. While booting it reports these messages [0.00] *BAD*gran_size: 64K chunk_size: 16M num_reg: 10 lose cover RAM: -8M [0.00] *BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -8M [0.00] *BAD*gran_size: 64K chunk_size: 64M num_reg: 10 lose cover RAM: -8M [0.00] gran_size: 64K chunk_size: 128M num_reg: 10 lose cover RAM: 0G [0.00] gran_size: 64K chunk_size: 256M num_reg: 10 lose cover RAM: 0G [0.00] gran_size: 64K chunk_size: 512M num_reg: 10 lose cover RAM: 0G [0.00] gran_size: 64K chunk_size: 1G num_reg: 10 lose cover RAM: 0G [0.00] *BAD*gran_size: 64K chunk_size: 2G num_reg: 10 lose cover RAM: -1G [0.00] Do these indicate a h/w defect? Before installing raring beta2, memtest reported lot of errors and I killed it after the count went past a million After installing raring iso, memtest ran over night with out errors (shows 'pass'). Does installing new version of iso upgrade the memtest version also? Vasudevan Kottilil -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
raring iso beta2 - files - internal error
After installation, after clicking files icon, this error shows up. Ubuntu 13.04 - internal error compiz crashed with SIGSEGV in sigc::internal::slot_call0 ...etc -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
raring iso beta2 - incomplete language support
After installation, this window pops up. "The language support for your selected language seems to be incomplete ... etc." Installation options were default - language - US English Not sure if this is expected behavior or not. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
