Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. [Bug 706] libgsm does not build as timestamped filenames
change ([EMAIL PROTECTED])
2. [Bug 937] Qemu doens't want to flash images
([EMAIL PROTECTED])
3. [Bug 998] New: Keyboard autorepeat is too twitchy
([EMAIL PROTECTED])
4. [Bug 999] New: On-screen keyboard font has no arrows
([EMAIL PROTECTED])
5. [Bug 1000] New: Terminal starts in root, regardless of
([EMAIL PROTECTED])
6. [Bug 1000] Terminal starts in root, regardless of
([EMAIL PROTECTED])
7. [Bug 808] Nonexistent $HOME breaks stuff
([EMAIL PROTECTED])
8. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
9. [Bug 937] Qemu doens't want to flash images
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=706
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
------- Additional Comments From [EMAIL PROTECTED] 2007-11-07 18:47 -------
closing here, since this is an OE problem.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=937
------- Additional Comments From [EMAIL PROTECTED] 2007-11-07 19:54 -------
on Debian Lenny, running on an 1.9GHz Intel Pentium IV with 1GB of RAM, I
observe the following behaviour:
On a fresh install of the MokoMakefile, invoking "make qemu" hangs at the
following location:
neo_vib_switch: Buzz, buzz.
neo_vib_switch: Vibrator stopped.
neo_bl_switch: LCD Backlight now on.
GTA01Bv4 #
GTA01Bv4 # openmoko/flash.sh: line 88: 29829 Terminated $qemu
-mtdblock "$script_dir/$flash_base" -kernel "$script_dir/$1" -serial stdio
-nographic -usb -monitor null 0<&0
U-boot failed to finish writing in 300 seconds, giving up.
make: *** [flash-qemu-official] Error 255
If I subsequently invoke "make qemu" again, it gets to the more-widely-reported
hanging place:
Creating BBT. Please wait ...Bad block table not found for chip 0
Bad block table not found for chip 0
Bad block table written to 0x03ffc000, version 0x01
Bad block table written to 0x03ff8000, version 0x01
GTA01Bv4 # setenv bootcmd 'openmoko/flash.sh: line 88: 30176 Terminated
$qemu -mtdblock "$script_dir/$flash_base" -kernel "$script_dir/$1" -serial
stdio -nographic -usb -monitor null 0<&0
U-boot failed to finish writing in 300 seconds, giving up.
make: *** [flash-qemu-official] Error 255
I am happy to run any tests which anyone thinks would be helpful.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=998
Summary: Keyboard autorepeat is too twitchy
Product: OpenMoko
Version: 2007.2
Platform: Neo1973
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-keyboard
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
The onscreen keyboard has an autorepeat, so if you hold your stylus down, it
will start to repeat after a short delay. This is great for editing long
command lines, for example.
But it stops autorepeating if stylus movement is detected, and the threshold is
very, very low. So I can hold on an arrow key and the result is a bit
unpredictable:
* I might get no autorepeat at all, because of some minor jitter from the
touchscreen;
* I might get autorepeat as long as I want, which is rare; or
* I might get a few characters' worth of autorepeat, then it stops.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=999
Summary: On-screen keyboard font has no arrows
Product: OpenMoko
Version: 2007.2
Platform: Neo1973
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-keyboard
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
The font used on the onscreen keyboard doesn't have arrow characters, so
indistinguishable boxes are used on the four arrow keys.
This is probably a well-known issue, but I don't see it documented in bugzilla,
so here it is for tracking purposes.
In any event, ultimately, having arrows will be better than the "^ V <- ->" or
whatever was there previously.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1000
Summary: Terminal starts in root, regardless of
Product: OpenMoko
Version: 2007.2
Platform: Neo1973
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-terminal
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1000
------- Additional Comments From [EMAIL PROTECTED] 2007-11-07 23:45 -------
Oops, my pinky finger pressed ENTER accidentally too early. Summary should be:
Terminal starts in root, regardless of $HOME setting
I don't see where to change this behavior -- the old terminal mrxvt had an
.mrxvtrc file in which to change settings, but where go settings in the new one?
Regardless of where settings are put, the default behavior should be for it to
start in the user's home directory, currently /home/root. But right now it
starts at /
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=808
------- Additional Comments From [EMAIL PROTECTED] 2007-11-07 23:51 -------
I just checked on a brand new from-scratch image I built (2007-11-06), and $HOME
still isn't set correctly unless I set it myself in (e.g.)
/etc/profile.d/userprofile.sh
Contrary to my initial post, I don't think this has anything to do with when
mounted partitions are brought up.
On a freshly flashed, freshly booted Neo, I open the terminal, type 'env', and
see that HOME=/
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
[This e-mail has been automatically generated.]
You have one or more bugs assigned to you in the Bugzilla
bugsystem (http://bugzilla.openmoko.org/cgi-bin/bugzilla/) that require
attention.
All of these bugs are in the NEW state, and have not been touched
in 7 days or more. You need to take a look at them, and
decide on an initial action.
Generally, this means one of three things:
(1) You decide this bug is really quick to deal with (like, it's INVALID),
and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to someone
else. (Hint: if you don't know who to reassign it to, make sure that
the Component field seems reasonable, and then use the "Reassign bug to
owner of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
Just use the "Accept bug" command.
To get a list of all NEW bugs, you can use this URL (bookmark it if you like!):
http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?bug_status=NEW&[EMAIL
PROTECTED]
Or, you can use the general query page, at
http://bugzilla.openmoko.org/cgi-bin/bugzilla/query.cgi.
Appended below are the individual URLs to get to all of your NEW bugs that
haven't been touched for a week or more.
You will get this message once a day until you've dealt with these bugs!
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=41
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=69
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=112
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=114
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=141
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=181
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=301
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=340
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=448
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=466
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=555
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=572
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=624
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=630
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=661
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=675
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=696
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=714
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=727
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=847
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=864
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=870
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=881
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=882
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=888
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=908
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=934
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=935
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=961
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=937
------- Additional Comments From [EMAIL PROTECTED] 2007-11-08 10:38 -------
I tried it again by deleting everything and starting with a fresh build using
'make qemu'. I got the bug again, but then after a few tries, it miraculously
worked! I know this isn't great for a bug report, so if you need to know
anything else, please ask. This is on a fresh install of gutsy with all updates
applied.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
