Mer/Releases/0.13testing1 - Revision history

amigadave: {{Mer}}

2010-09-22T10:00:39Z

← Older revision		Revision as of 10:00, 22 September 2010
Line 1:		Line 1:
		+	{{Mer}}
		+
	By using these testing images, you're '''morally obligated to test them''' and to edit this page and report -every single bug you find-, no matter if they're theme flaws, quirks, bugs or crashes. You can optionally also use [https://bugs.maemo.org/enter_bug.cgi?product=Mer bugzilla] , use version 0.13.		By using these testing images, you're '''morally obligated to test them''' and to edit this page and report -every single bug you find-, no matter if they're theme flaws, quirks, bugs or crashes. You can optionally also use [https://bugs.maemo.org/enter_bug.cgi?product=Mer bugzilla] , use version 0.13.

Line 44:		Line 46:
	** Icon sizes are changed in Fremantle, so a theme issue probably		** Icon sizes are changed in Fremantle, so a theme issue probably
	*** no. There are no icons on the toolbar. Screenshot: [http://www.quicksnapper.com/JMarkevich/image/toolbar-bug Toolbar Bug] (this has been a persistent bug in Maemo, though mostly for all python programs, evidently)		*** no. There are no icons on the toolbar. Screenshot: [http://www.quicksnapper.com/JMarkevich/image/toolbar-bug Toolbar Bug] (this has been a persistent bug in Maemo, though mostly for all python programs, evidently)
-
-	~~[[Category:Mer]]~~

amigadave: Category:Mer

2010-02-11T15:23:14Z

Category:Mer

← Older revision		Revision as of 15:23, 11 February 2010
Line 44:		Line 44:
	** Icon sizes are changed in Fremantle, so a theme issue probably		** Icon sizes are changed in Fremantle, so a theme issue probably
	*** no. There are no icons on the toolbar. Screenshot: [http://www.quicksnapper.com/JMarkevich/image/toolbar-bug Toolbar Bug] (this has been a persistent bug in Maemo, though mostly for all python programs, evidently)		*** no. There are no icons on the toolbar. Screenshot: [http://www.quicksnapper.com/JMarkevich/image/toolbar-bug Toolbar Bug] (this has been a persistent bug in Maemo, though mostly for all python programs, evidently)
		+
		+	[[Category:Mer]]

stskeeps: /* Bugs in testing1 */

2009-05-13T18:22:30Z

Bugs in testing1

← Older revision		Revision as of 18:22, 13 May 2009
Line 21:		Line 21:
	* Enhancement: jffs2 images, kernels, etc.		* Enhancement: jffs2 images, kernels, etc.
	** Potential fix: Edit kernel-diablo in Maemo:Mer:Devel:HW:N8x0:Devel to include a variant (like -oprofile or such) that is built to sed CONFIG_CMDLINE from 'CONFIG_CMDLINE="root=1f03 rootfstype=jffs2 ro console=tty0 console=ttyMTD5" to:'CONFIG_CMDLINE="root=1f04 rootfstype=jffs2 init=/sbin/tablet-init ro console=tty0 console=ttyMTD5"'		** Potential fix: Edit kernel-diablo in Maemo:Mer:Devel:HW:N8x0:Devel to include a variant (like -oprofile or such) that is built to sed CONFIG_CMDLINE from 'CONFIG_CMDLINE="root=1f03 rootfstype=jffs2 ro console=tty0 console=ttyMTD5" to:'CONFIG_CMDLINE="root=1f04 rootfstype=jffs2 init=/sbin/tablet-init ro console=tty0 console=ttyMTD5"'
		+	*** Added in kernel-diablo
	* Minor issues:		* Minor issues:
	** [0.12, not verified to be in 0.13testing1] /etc/init.d/powered produces a message similar to ‘[: 105: false: invalid operator’. The fix is to change ‘==’ to ‘=’ in all lines of the form ‘[ "$FOO" == "true" ]’. (Just search for ‘==’ in all init.d scripts.)		** [0.12, not verified to be in 0.13testing1] /etc/init.d/powered produces a message similar to ‘[: 105: false: invalid operator’. The fix is to change ‘==’ to ‘=’ in all lines of the form ‘[ "$FOO" == "true" ]’. (Just search for ‘==’ in all init.d scripts.)

stskeeps: /* Bugs in testing1 */

2009-05-13T07:21:07Z

Bugs in testing1

← Older revision		Revision as of 07:21, 13 May 2009
Line 23:		Line 23:
	* Minor issues:		* Minor issues:
	** [0.12, not verified to be in 0.13testing1] /etc/init.d/powered produces a message similar to ‘[: 105: false: invalid operator’. The fix is to change ‘==’ to ‘=’ in all lines of the form ‘[ "$FOO" == "true" ]’. (Just search for ‘==’ in all init.d scripts.)		** [0.12, not verified to be in 0.13testing1] /etc/init.d/powered produces a message similar to ‘[: 105: false: invalid operator’. The fix is to change ‘==’ to ‘=’ in all lines of the form ‘[ "$FOO" == "true" ]’. (Just search for ‘==’ in all init.d scripts.)
		+	*** Fixed in powerlaunch 0.9.2mer8
	** [0.12, not verified to be in 0.13testing1] Near the top of /usr/sbin/set_dim_and_blank.py is ‘if dim > blank: print "Dim must be >= blank"’; the message should say ‘<=’ rather than ‘>=’.		** [0.12, not verified to be in 0.13testing1] Near the top of /usr/sbin/set_dim_and_blank.py is ‘if dim > blank: print "Dim must be >= blank"’; the message should say ‘<=’ rather than ‘>=’.
	*** Fixed in dsme-tools 0.8		*** Fixed in dsme-tools 0.8

84.238.94.243: /* Bugs in testing1 */

2009-05-13T07:19:17Z

Bugs in testing1

← Older revision		Revision as of 07:19, 13 May 2009
Line 23:		Line 23:
	* Minor issues:		* Minor issues:
	** [0.12, not verified to be in 0.13testing1] /etc/init.d/powered produces a message similar to ‘[: 105: false: invalid operator’. The fix is to change ‘==’ to ‘=’ in all lines of the form ‘[ "$FOO" == "true" ]’. (Just search for ‘==’ in all init.d scripts.)		** [0.12, not verified to be in 0.13testing1] /etc/init.d/powered produces a message similar to ‘[: 105: false: invalid operator’. The fix is to change ‘==’ to ‘=’ in all lines of the form ‘[ "$FOO" == "true" ]’. (Just search for ‘==’ in all init.d scripts.)
-	** [0.12, not verified to be in 0.13testing1] Near the top of /usr/sbin/set_dim_and_blank.py is ‘if dim > blank: print "Dim must be >= blank"’; the message should say ‘<=’ rather than ‘>=’.	+	** [0.12, not verified to be in 0.13testing1] Near the top of /usr/sbin/set_dim_and_blank.py is ‘if dim > blank: print "Dim must be >= blank"’; the message should say ‘<=’ rather than ‘>=’.
		+	*** Fixed in dsme-tools 0.8

130.194.69.10: /* Bugs in testing1 */ clarify one of the issues i added yesterday (pjrm)

2009-05-13T06:03:46Z

Bugs in testing1: clarify one of the issues i added yesterday (pjrm)

← Older revision		Revision as of 06:03, 13 May 2009
Line 23:		Line 23:
	* Minor issues:		* Minor issues:
	** [0.12, not verified to be in 0.13testing1] /etc/init.d/powered produces a message similar to ‘[: 105: false: invalid operator’. The fix is to change ‘==’ to ‘=’ in all lines of the form ‘[ "$FOO" == "true" ]’. (Just search for ‘==’ in all init.d scripts.)		** [0.12, not verified to be in 0.13testing1] /etc/init.d/powered produces a message similar to ‘[: 105: false: invalid operator’. The fix is to change ‘==’ to ‘=’ in all lines of the form ‘[ "$FOO" == "true" ]’. (Just search for ‘==’ in all init.d scripts.)
-	** [0.12, not verified to be in 0.13testing1] At the top of /usr/sbin/set_dim_and_blank.py~~, if the requested blank time~~ is ~~less than~~ dim ~~time then a message is printed, but~~ the message ~~has the comparison wrong:~~ should ~~either swap operands or swap direction of operator. (Sorry for unclear description, I'll check this tomorrow or so~~.)	+	** [0.12, not verified to be in 0.13testing1] Near the top of /usr/sbin/set_dim_and_blank.py is ‘if dim > blank: print "Dim must be >= blank"’; the message should say ‘<=’ rather than ‘>=’.

jaem at 20:44, 12 May 2009

2009-05-12T20:44:50Z

← Older revision		Revision as of 20:44, 12 May 2009
Line 15:		Line 15:
	== Bugs in testing1 ==		== Bugs in testing1 ==

		+	* Hardware keyboard/slider events on N810 when device is in standby only turns on backlight, and doesn't unblank the screen. Touchscreen events work fine in this respect.
	* Touchscreen using xf86-input-tslib does not work (N8x0, SmartQ). Fix will be in testing2 image (redownload image and it should be fixed)		* Touchscreen using xf86-input-tslib does not work (N8x0, SmartQ). Fix will be in testing2 image (redownload image and it should be fixed)
	* Brightness applet makes hildon crash (not always) http://pastebin.ca/1418638		* Brightness applet makes hildon crash (not always) http://pastebin.ca/1418638
-	* ~~Frozing~~ at shutdown if the ~~commad~~ is given from the new gui	+	* Freezing at shutdown if the command is given from the new gui
	* Enhancement: jffs2 images, kernels, etc.		* Enhancement: jffs2 images, kernels, etc.
	** Potential fix: Edit kernel-diablo in Maemo:Mer:Devel:HW:N8x0:Devel to include a variant (like -oprofile or such) that is built to sed CONFIG_CMDLINE from 'CONFIG_CMDLINE="root=1f03 rootfstype=jffs2 ro console=tty0 console=ttyMTD5" to:'CONFIG_CMDLINE="root=1f04 rootfstype=jffs2 init=/sbin/tablet-init ro console=tty0 console=ttyMTD5"'		** Potential fix: Edit kernel-diablo in Maemo:Mer:Devel:HW:N8x0:Devel to include a variant (like -oprofile or such) that is built to sed CONFIG_CMDLINE from 'CONFIG_CMDLINE="root=1f03 rootfstype=jffs2 ro console=tty0 console=ttyMTD5" to:'CONFIG_CMDLINE="root=1f04 rootfstype=jffs2 init=/sbin/tablet-init ro console=tty0 console=ttyMTD5"'

boxofsnoo: /* x86 VMDK */

2009-05-12T17:34:50Z

x86 VMDK

← Older revision		Revision as of 17:34, 12 May 2009
Line 29:		Line 29:
	* Applications installed prompt for folder location but are always stored in Extras		* Applications installed prompt for folder location but are always stored in Extras
	** Artifact of Fremantle Application Manager i think		** Artifact of Fremantle Application Manager i think
-	*** (~~Don't care~~. It's a bug)	+	*** (Irrelevant. It's a bug)
	* Organize dialog nonresponsive to any input		* Organize dialog nonresponsive to any input
	* Locale hardcoded to en_GB.utf8 (?)		* Locale hardcoded to en_GB.utf8 (?)
Line 39:		Line 39:
	* Terminal toolbar (likely other) has significanly misaligned background image when selected.		* Terminal toolbar (likely other) has significanly misaligned background image when selected.
	** Icon sizes are changed in Fremantle, so a theme issue probably		** Icon sizes are changed in Fremantle, so a theme issue probably
-	*** no. There are no icons on the toolbar. ~~I will work up~~ a ~~screenshot~~	+	*** no. There are no icons on the toolbar. Screenshot: [http://www.quicksnapper.com/JMarkevich/image/toolbar-bug Toolbar Bug] (this has been a persistent bug in Maemo, though mostly for all python programs, evidently)

boxofsnoo: /* x86 VMDK */

2009-05-12T17:29:52Z

x86 VMDK

← Older revision		Revision as of 17:29, 12 May 2009
Line 29:		Line 29:
	* Applications installed prompt for folder location but are always stored in Extras		* Applications installed prompt for folder location but are always stored in Extras
	** Artifact of Fremantle Application Manager i think		** Artifact of Fremantle Application Manager i think
		+	*** (Don't care. It's a bug)
	* Organize dialog nonresponsive to any input		* Organize dialog nonresponsive to any input
	* Locale hardcoded to en_GB.utf8 (?)		* Locale hardcoded to en_GB.utf8 (?)
	** There is a .current-locale feature, needs control panel (+ reboot), look in /usr/bin/start-hildon		** There is a .current-locale feature, needs control panel (+ reboot), look in /usr/bin/start-hildon
		+	*** the file is ~/.osso/current-locale and it doesn't work.
	* Terminal menu text is not replaced with localized text - e.g. "webameedit - webamecopy" etc.		* Terminal menu text is not replaced with localized text - e.g. "webameedit - webamecopy" etc.
-	** Make some strings for osso-xterm, we don't have any :)
	* Terminal toolbar Ctrl button non-functional (try Ctrl + d, Ctrl + h, Ctrl + g, Ctrl + c)		* Terminal toolbar Ctrl button non-functional (try Ctrl + d, Ctrl + h, Ctrl + g, Ctrl + c)
	** Work on including patches in libvte on garage.maemo.org/projects/osso-xterm into vte - there's some not included yet.		** Work on including patches in libvte on garage.maemo.org/projects/osso-xterm into vte - there's some not included yet.
	* Terminal toolbar (likely other) has significanly misaligned background image when selected.		* Terminal toolbar (likely other) has significanly misaligned background image when selected.
	** Icon sizes are changed in Fremantle, so a theme issue probably		** Icon sizes are changed in Fremantle, so a theme issue probably
-		+	*** no. There are no icons on the toolbar. I will work up a screenshot
-	~~--[[User:boxofsnoo\|boxofsnoo]] 18:25, 10 May 2009 (UTC)~~	+

118.208.232.17: /* Bugs in testing1 */ add a couple of minor issues

2009-05-12T12:22:51Z

Bugs in testing1: add a couple of minor issues

← Older revision		Revision as of 12:22, 12 May 2009
Line 20:		Line 20:
	* Enhancement: jffs2 images, kernels, etc.		* Enhancement: jffs2 images, kernels, etc.
	** Potential fix: Edit kernel-diablo in Maemo:Mer:Devel:HW:N8x0:Devel to include a variant (like -oprofile or such) that is built to sed CONFIG_CMDLINE from 'CONFIG_CMDLINE="root=1f03 rootfstype=jffs2 ro console=tty0 console=ttyMTD5" to:'CONFIG_CMDLINE="root=1f04 rootfstype=jffs2 init=/sbin/tablet-init ro console=tty0 console=ttyMTD5"'		** Potential fix: Edit kernel-diablo in Maemo:Mer:Devel:HW:N8x0:Devel to include a variant (like -oprofile or such) that is built to sed CONFIG_CMDLINE from 'CONFIG_CMDLINE="root=1f03 rootfstype=jffs2 ro console=tty0 console=ttyMTD5" to:'CONFIG_CMDLINE="root=1f04 rootfstype=jffs2 init=/sbin/tablet-init ro console=tty0 console=ttyMTD5"'
		+	* Minor issues:
		+	** [0.12, not verified to be in 0.13testing1] /etc/init.d/powered produces a message similar to ‘[: 105: false: invalid operator’. The fix is to change ‘==’ to ‘=’ in all lines of the form ‘[ "$FOO" == "true" ]’. (Just search for ‘==’ in all init.d scripts.)
		+	** [0.12, not verified to be in 0.13testing1] At the top of /usr/sbin/set_dim_and_blank.py, if the requested blank time is less than dim time then a message is printed, but the message has the comparison wrong: should either swap operands or swap direction of operator. (Sorry for unclear description, I'll check this tomorrow or so.)