Re: 11.3.0 release candidate 4 (build 883) released
Hi Gary, On Mon, Oct 31, 2011 at 6:41 PM, Gary Martin garycmar...@googlemail.com wrote: ... I've just been testing Telescope-12 on the XO-1.75 running the new 883 build, first the good news, the camera is showing up correctly in Record and Telescope, fab! :) Now the not so hot: - While in Telescope-12, clicking the digital zoom toolbar button completely locked up the XO-1.75 (re-testing with an XO-1 the digital zoom works ok). - After some waiting and many attempted keyboard shortcuts, I decided to power down. Clicking the power hardware button did not trigger the usual shut down screen during this particular lockup case; clicking the power button twice (assuming it might just be the gfx that had locked-up) had no effect; finally I held down the power button for some seconds until the power led flashes and then the hard powers off. - On reboot the Journal now shows 3 corrupt entries (see attached screen shot) with no name and unknown metadata. None of the three entries allow invoking the details view or raise their palette so can not be erased via the Sugar Journal UI. The three corrupt entries will be an entry for Browse where I visited ASLO to download telescope and then quit Browse; the downloaded Telescope-12 bundle; and the instance entry for the Telescope that was running when the XO locked up. Given the nature of the hard power off I understand why some data would not have been synched to disk, but just wanted to raise this case here. I guess the actionable items might be: 1) fixing Telescope-12's digital zoom not to lock up an XO-1.75 (I don't have an XO-1.5 to test but I re-checked on an XO-1 which still worked fine). 2) Seeing why the XO-1.75 hard crashed, I'm assuming something camera driver related may have borked badly (I do have a serial cable here for un-bricking an XO-1.75 but don't know my way around that side of things very well). I tried to reproduce with Telescope, and I get an oops/hang as well. The same oops is already filed as https://dev.laptop.org/ticket/11128. Using a serial console for logging may show if it is a panic/crash or a hang (like a very busy loop). If you unbricked your XO-1.75 with an other Linux system, you should be able to use minicom to capture a log in a similar way. After starting minicom, press CTRL+a,z (press CTRL+a together, release them, press 'z') to get in the minicom help/menu. Pressing 'l' will ask you for a filename, I'd use samething like xo-1.75-camera-issue.log. After pressing return, everything will be saved. Now turn on the XO and reproduce the issue. When you encounter the panic/hang again, press CTRL+l in minicom to close the logfile and exit minicom. I'll try this as well, but am still running build 882 which may be differnt than build 883 in this respect. Good luck, Niels ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 11.3.0 release candidate 4 (build 883) released
On Tue, Nov 1, 2011 at 11:24 AM, Niels de Vos de...@fedoraproject.org wrote: Hi Gary, On Mon, Oct 31, 2011 at 6:41 PM, Gary Martin garycmar...@googlemail.com wrote: ... I've just been testing Telescope-12 on the XO-1.75 running the new 883 build, first the good news, the camera is showing up correctly in Record and Telescope, fab! :) Now the not so hot: - While in Telescope-12, clicking the digital zoom toolbar button completely locked up the XO-1.75 (re-testing with an XO-1 the digital zoom works ok). - After some waiting and many attempted keyboard shortcuts, I decided to power down. Clicking the power hardware button did not trigger the usual shut down screen during this particular lockup case; clicking the power button twice (assuming it might just be the gfx that had locked-up) had no effect; finally I held down the power button for some seconds until the power led flashes and then the hard powers off. - On reboot the Journal now shows 3 corrupt entries (see attached screen shot) with no name and unknown metadata. None of the three entries allow invoking the details view or raise their palette so can not be erased via the Sugar Journal UI. The three corrupt entries will be an entry for Browse where I visited ASLO to download telescope and then quit Browse; the downloaded Telescope-12 bundle; and the instance entry for the Telescope that was running when the XO locked up. Given the nature of the hard power off I understand why some data would not have been synched to disk, but just wanted to raise this case here. I guess the actionable items might be: 1) fixing Telescope-12's digital zoom not to lock up an XO-1.75 (I don't have an XO-1.5 to test but I re-checked on an XO-1 which still worked fine). 2) Seeing why the XO-1.75 hard crashed, I'm assuming something camera driver related may have borked badly (I do have a serial cable here for un-bricking an XO-1.75 but don't know my way around that side of things very well). I tried to reproduce with Telescope, and I get an oops/hang as well. The same oops is already filed as https://dev.laptop.org/ticket/11128. Using a serial console for logging may show if it is a panic/crash or a hang (like a very busy loop). If you unbricked your XO-1.75 with an other Linux system, you should be able to use minicom to capture a log in a similar way. After starting minicom, press CTRL+a,z (press CTRL+a together, release them, press 'z') to get in the minicom help/menu. Pressing 'l' will ask you for a filename, I'd use samething like xo-1.75-camera-issue.log. After pressing return, everything will be saved. Now turn on the XO and reproduce the issue. When you encounter the panic/hang again, press CTRL+l in minicom to close the logfile and exit minicom. I'll try this as well, but am still running build 882 which may be differnt than build 883 in this respect. The result I have with build 882 and Telescope: - working nicely - click 'diigital zoom' - Telescope gets unresponsive (no picture anymore) - oops over the serial console - mouse and keyboard are still functioning - Telescope can be (forcefully) stopped - Telescope fails to sart (requires reboot) - no additional oopses recorded The oops is available in #11128. HTH Niels ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] 11.3.0 release candidate 4 (build 883) released
Excerpts from Gary Martin's message of 2011-10-31 19:41:21 +0100: - On reboot the Journal now shows 3 corrupt entries (see attached screen shot) with no name and unknown metadata. None of the three entries allow invoking the details view or raise their palette so can not be erased via the Sugar Journal UI. The three corrupt entries will be an entry for Browse where I visited ASLO to download telescope and then quit Browse; the downloaded Telescope-12 bundle; and the instance entry for the Telescope that was running when the XO locked up. Please provide copies of shell.log and datastore.log and a tarball of ~/.sugar/default/datastore. If the data store contains information you'd prefer not to make public, you can send me the tarball privately (encrypted with my PGP key) or put it on sunjammer for me to pick up. Otherwise please open a new ticket [1] and attach the files there. Sascha [1] https://bugs.sugarlabs.org/newticket?component=sugarversion=0.94.xseverity=Majordistribution=OLPC -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] 11.3.0 release candidate 4 (build 883) released
Reproduced here, datastore.log does not show anything, but shell.log show: Trying to open Detail View: Traceback (most recent call last): File /usr/lib/python2.7/site-packages/jarabe/journal/journalactivity.py, line 206, in __detail_clicked_cb self._show_secondary_view(object_id) File /usr/lib/python2.7/site-packages/jarabe/journal/journalactivity.py, line 228, in _show_secondary_view metadata = model.get(object_id) File /usr/lib/python2.7/site-packages/jarabe/journal/model.py, line 551, in get metadata = _get_datastore().get_properties(object_id, byte_arrays=True) File /usr/lib/python2.7/site-packages/dbus/proxies.py, line 140, in __call__ **keywords) File /usr/lib/python2.7/site-packages/dbus/connection.py, line 630, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Python.IOError: Traceback (most recent call last): File /usr/lib/python2.7/site-packages/dbus/service.py, line 702, in _message_cb retval = candidate_method(self, *args, **keywords) File /usr/lib/python2.7/site-packages/carquinyol/datastore.py, line 355, in get_properties metadata = self._metadata_store.retrieve(uid) File /usr/lib/python2.7/site-packages/carquinyol/metadatastore.py, line 41, in retrieve return metadatareader.retrieve(metadata_path, properties) IOError: Couldn't open metadata directory /home/olpc/.sugar/default/datastore///metadata Moving the mouse over the icon: Traceback (most recent call last): File /usr/lib/python2.7/site-packages/sugar/graphics/palettewindow.py, line 939, in __motion_notify_event_cb self.notify_mouse_enter() File /usr/lib/python2.7/site-packages/sugar/graphics/palettewindow.py, line 629, in notify_mouse_enter self._ensure_palette_exists() File /usr/lib/python2.7/site-packages/sugar/graphics/palettewindow.py, line 624, in _ensure_palette_exists palette = self.parent.create_palette() File /usr/lib/python2.7/site-packages/jarabe/journal/listview.py, line 615, in create_palette metadata = tree_model.get_metadata(self.props.palette_invoker.path) File /usr/lib/python2.7/site-packages/jarabe/journal/listmodel.py, line 103, in get_metadata return model.get(self[path][ListModel.COLUMN_UID]) File /usr/lib/python2.7/site-packages/jarabe/journal/model.py, line 551, in get metadata = _get_datastore().get_properties(object_id, byte_arrays=True) File /usr/lib/python2.7/site-packages/dbus/proxies.py, line 140, in __call__ **keywords) File /usr/lib/python2.7/site-packages/dbus/connection.py, line 630, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Python.IOError: Traceback (most recent call last): File /usr/lib/python2.7/site-packages/dbus/service.py, line 702, in _message_cb retval = candidate_method(self, *args, **keywords) File /usr/lib/python2.7/site-packages/carquinyol/datastore.py, line 355, in get_properties metadata = self._metadata_store.retrieve(uid) File /usr/lib/python2.7/site-packages/carquinyol/metadatastore.py, line 41, in retrieve return metadatareader.retrieve(metadata_path, properties) IOError: Couldn't open metadata directory /home/olpc/.sugar/default/datastore///metadata Gonzalo On Tue, Nov 1, 2011 at 9:02 AM, Sascha Silbe sascha-ml-reply-to-201...@silbe.org wrote: Excerpts from Gary Martin's message of 2011-10-31 19:41:21 +0100: - On reboot the Journal now shows 3 corrupt entries (see attached screen shot) with no name and unknown metadata. None of the three entries allow invoking the details view or raise their palette so can not be erased via the Sugar Journal UI. The three corrupt entries will be an entry for Browse where I visited ASLO to download telescope and then quit Browse; the downloaded Telescope-12 bundle; and the instance entry for the Telescope that was running when the XO locked up. Please provide copies of shell.log and datastore.log and a tarball of ~/.sugar/default/datastore. If the data store contains information you'd prefer not to make public, you can send me the tarball privately (encrypted with my PGP key) or put it on sunjammer for me to pick up. Otherwise please open a new ticket [1] and attach the files there. Sascha [1] https://bugs.sugarlabs.org/newticket?component=sugarversion=0.94.xseverity=Majordistribution=OLPC -- http://sascha.silbe.org/ http://www.infra-silbe.de/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] 11.3.0 release candidate 4 (build 883) released
New ticket #11372 was created with the content of a corrupted datastore. Gonzalo ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 11.3.0 release candidate 4 (build 883) released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, For 'digital zoom', Telescope uses the videobox gst element. Maybe that's where the problem is. Unfortunately, I don't have much time to debug it myself on a 1.75 right now. Also, from what I gather, the digital zoom does work on a xo 1.5, so the problem does seem xo1.75 specific at the moment. Hope this helps. On 11/01/2011 05:19 PM, Niels de Vos wrote: On Tue, Nov 1, 2011 at 11:24 AM, Niels de Vos de...@fedoraproject.org wrote: Hi Gary, On Mon, Oct 31, 2011 at 6:41 PM, Gary Martin garycmar...@googlemail.com wrote: ... I've just been testing Telescope-12 on the XO-1.75 running the new 883 build, first the good news, the camera is showing up correctly in Record and Telescope, fab! :) Now the not so hot: - While in Telescope-12, clicking the digital zoom toolbar button completely locked up the XO-1.75 (re-testing with an XO-1 the digital zoom works ok). - After some waiting and many attempted keyboard shortcuts, I decided to power down. Clicking the power hardware button did not trigger the usual shut down screen during this particular lockup case; clicking the power button twice (assuming it might just be the gfx that had locked-up) had no effect; finally I held down the power button for some seconds until the power led flashes and then the hard powers off. - On reboot the Journal now shows 3 corrupt entries (see attached screen shot) with no name and unknown metadata. None of the three entries allow invoking the details view or raise their palette so can not be erased via the Sugar Journal UI. The three corrupt entries will be an entry for Browse where I visited ASLO to download telescope and then quit Browse; the downloaded Telescope-12 bundle; and the instance entry for the Telescope that was running when the XO locked up. Given the nature of the hard power off I understand why some data would not have been synched to disk, but just wanted to raise this case here. I guess the actionable items might be: 1) fixing Telescope-12's digital zoom not to lock up an XO-1.75 (I don't have an XO-1.5 to test but I re-checked on an XO-1 which still worked fine). 2) Seeing why the XO-1.75 hard crashed, I'm assuming something camera driver related may have borked badly (I do have a serial cable here for un-bricking an XO-1.75 but don't know my way around that side of things very well). I tried to reproduce with Telescope, and I get an oops/hang as well. The same oops is already filed as https://dev.laptop.org/ticket/11128. Using a serial console for logging may show if it is a panic/crash or a hang (like a very busy loop). If you unbricked your XO-1.75 with an other Linux system, you should be able to use minicom to capture a log in a similar way. After starting minicom, press CTRL+a,z (press CTRL+a together, release them, press 'z') to get in the minicom help/menu. Pressing 'l' will ask you for a filename, I'd use samething like xo-1.75-camera-issue.log. After pressing return, everything will be saved. Now turn on the XO and reproduce the issue. When you encounter the panic/hang again, press CTRL+l in minicom to close the logfile and exit minicom. I'll try this as well, but am still running build 882 which may be differnt than build 883 in this respect. The result I have with build 882 and Telescope: - working nicely - click 'diigital zoom' - Telescope gets unresponsive (no picture anymore) - oops over the serial console - mouse and keyboard are still functioning - Telescope can be (forcefully) stopped - Telescope fails to sart (requires reboot) - no additional oopses recorded The oops is available in #11128. HTH Niels - -- Anish Mangal Sugar Labs -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOsMRLAAoJEBoxUdDHDZVpVxcIAJI22tl9B+E2+8L7QkWQHFsr sSqVjnQ73fX7LtRTd/MWbYLEUiEsdc9KvaNi1M0LV+y7U4/s5aBZnacJQs2qYmHu a/f/cce1cCl95hpwkPSHZ/L4fq728TwUSZYFewRMY55GELOKQMx8uACdYCfiDHHM mvhrdvp+wLXBV7NeCJZTpAQ3F0L6e7YfMs0xaromITKQmvSKjJ1yYD8d8BvJQ8n6 0doVKaUH2/9i6I8tKLYGoFzk5/Pb1KLNnRkc4evk4BKnVAL5pm1c3lNJWF3d5nCi Ww9L9K9pLCx9jGpi+SDsH+QRiuuHTGIu8dnFkTOEnFvZYJ5svSoiIQGJkqIuECA= =IgvR -END PGP SIGNATURE- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 11.3.0 release candidate 4 (build 883) released
Hi Daniel,On 29 Oct 2011, at 22:28, Daniel Drake wrote:Hi,We're pleased to announce our 4th release candidate of our new11.3.0 software release.Information and installation instructions can be found here:http://wiki.laptop.org/go/Release_notes/11.3.0Quick links for those who know which files need to be grabbed and saveto USB disks:http://download.laptop.org/xo-1/os/candidate/883/http://download.laptop.org/xo-1.5/os/candidate/883/http://download.laptop.org/xo-1.75/os/candidate/883/This is a signed release candidate that can be installed on all XOs,even those with security enabled.We're looking for testing and feedback on all aspects of the system.I've just been testing Telescope-12 on the XO-1.75 running the new 883 build, first the good news, the camera is showing up correctly in Record and Telescope, fab! :) Now the not so hot:- While in Telescope-12, clicking the digital zoom toolbar button completely locked up the XO-1.75 (re-testing with an XO-1 the digital zoom works ok).- After some waiting and many attempted keyboard shortcuts, I decided to power down. Clicking the power hardware button did not trigger the usual shut down screen during this particular lockup case; clicking the power button twice (assuming it might just be the gfx that had locked-up) had no effect; finally I held down the power button for some seconds until the power led flashes and then the hard powers off.- On reboot the Journal now shows 3 corrupt entries (see attached screen shot) with no name and unknown metadata. None of the three entries allow invoking the details view or raise their palette so can not be erased via the Sugar Journal UI.The three corrupt entries will be an entry for Browse where I visited ASLO to download telescope and then quit Browse; the downloaded Telescope-12 bundle; and the instance entry for the Telescope that was running when the XO locked up.Given the nature of the hard power off I understand why some data would not have been synched to disk, but just wanted to raise this case here. I guess the actionable items might be:1) fixing Telescope-12's digital zoom not to lock up an XO-1.75 (I don't have an XO-1.5 to test but I re-checked on an XO-1 which still worked fine).2) Seeing why the XO-1.75 hard crashed, I'm assuming something camera driver related may have borked badly (I do have a serial cable here for un-bricking an XO-1.75 but don't know my way around that side of things very well).3) Making Datastore more robust to corrupt entries; and/or perhaps just not displaying corrupt entries in the Journal UI (assuming they can be tested for reliably); and/or allowing them be erased via the Journal UI; and/or improving the way Journal displays a corrupt entry (broken document icon, fake title name).I'll hang onto this datastore as is, for a little while, in case someone wants to explore.Regards,--GaryThanks for any help you can offer, and for all the feedback that wasreceived throughout development.Our scheduled release date is November 1st.Please review the "Known problems" section of the release notes. Somedocumented issues are carried over from previous releases, but othersare new and are things that we will aim to fix in the few weeks beforerelease, including:XO-1.75 Sound does not work in many activities (ticket #11296). There is no suspend/resume support yet. There is slight mouse cursor visual corruption in Sugar, and themouse cursor in GNOME appears odd, but is otherwise functional.XO-1 users: we have identified a bug in the firmware releases shippedduring 11.3.0 development and in earlier 11.3.0 release candidatebuilds 880 and 881.Affected versions are Q2E46 and Q2E47. You can check which version youare running in the Sugar 'Settings' dialog.Unfortunately, a bug in the firmware update code means that thesefirmware versions will not automatically upgrade to newer versions. Wehave fixed this in Q2E48 (included in 11.3.0 build 882 onwards), butexisting users of Q2E46 and Q2E47 will need to update manually. Sorryabout that. The procedure is outlined here:http://dev.laptop.org/ticket/11336#comment:8Ask for help on these lists if needed.Users of 11.2.0 and previous (who will be running older firmwarereleases such as Q2E45) are not affected, and XO-1.5 and XO-1.75 usersare similarly unaffected.Changes since build 882:Camera use under Scratch on XO-1.5 no longer exhibits bad colors.Upgrades from 11.2 will now prompt the user to update activities.An XO-1.75 "third dot" boot hang is hopefully fixed.uvc USB webcam driver is now available on XO-1.75XO-1.75 kernel update includes some audio improvements - but we knowthere are still issues.XO-1 screen backlight will turn itself off upon inactivity againXO-1.5 and XO-1.75 firmware updates included.Closed tickets:#11357 Boot freezing on third clock dot#11297 Scratch: Camera quality in xo-1.5 is worst than in os874#11304 11.3.0 build 8 is not dimming, powering off the screen backlight on XO-1#11354 UVC webcam driver not available on XO-1.75#11355 No
11.3.0 release candidate 4 (build 883) released
Hi, We're pleased to announce our 4th release candidate of our new 11.3.0 software release. Information and installation instructions can be found here: http://wiki.laptop.org/go/Release_notes/11.3.0 Quick links for those who know which files need to be grabbed and save to USB disks: http://download.laptop.org/xo-1/os/candidate/883/ http://download.laptop.org/xo-1.5/os/candidate/883/ http://download.laptop.org/xo-1.75/os/candidate/883/ This is a signed release candidate that can be installed on all XOs, even those with security enabled. We're looking for testing and feedback on all aspects of the system. Thanks for any help you can offer, and for all the feedback that was received throughout development. Our scheduled release date is November 1st. Please review the Known problems section of the release notes. Some documented issues are carried over from previous releases, but others are new and are things that we will aim to fix in the few weeks before release, including: XO-1.75 Sound does not work in many activities (ticket #11296). There is no suspend/resume support yet. There is slight mouse cursor visual corruption in Sugar, and the mouse cursor in GNOME appears odd, but is otherwise functional. XO-1 users: we have identified a bug in the firmware releases shipped during 11.3.0 development and in earlier 11.3.0 release candidate builds 880 and 881. Affected versions are Q2E46 and Q2E47. You can check which version you are running in the Sugar 'Settings' dialog. Unfortunately, a bug in the firmware update code means that these firmware versions will not automatically upgrade to newer versions. We have fixed this in Q2E48 (included in 11.3.0 build 882 onwards), but existing users of Q2E46 and Q2E47 will need to update manually. Sorry about that. The procedure is outlined here: http://dev.laptop.org/ticket/11336#comment:8 Ask for help on these lists if needed. Users of 11.2.0 and previous (who will be running older firmware releases such as Q2E45) are not affected, and XO-1.5 and XO-1.75 users are similarly unaffected. Changes since build 882: Camera use under Scratch on XO-1.5 no longer exhibits bad colors. Upgrades from 11.2 will now prompt the user to update activities. An XO-1.75 third dot boot hang is hopefully fixed. uvc USB webcam driver is now available on XO-1.75 XO-1.75 kernel update includes some audio improvements - but we know there are still issues. XO-1 screen backlight will turn itself off upon inactivity again XO-1.5 and XO-1.75 firmware updates included. Closed tickets: #11357 Boot freezing on third clock dot #11297 Scratch: Camera quality in xo-1.5 is worst than in os874 #11304 11.3.0 build 8 is not dimming, powering off the screen backlight on XO-1 #11354 UVC webcam driver not available on XO-1.75 #11355 No software-update suggestion/prompt after an olpc-update #11358 New XO-1.5 firmware Q3B22 #11360 New XO-1.75 firmware Q4C02 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
