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 937] Qemu doesn't want to flash images
([EMAIL PROTECTED])
2. [Bug 894] gsmd locks-up if libgsmd-tool disconnects too
quickly ([EMAIL PROTECTED])
3. [Bug 1000] Terminal starts in root, regardless of $HOME
setting ([EMAIL PROTECTED])
4. [Bug 1000] Terminal starts in root, regardless of $HOME
setting ([EMAIL PROTECTED])
5. [Bug 1000] Terminal starts in root, regardless of $HOME
setting ([EMAIL PROTECTED])
6. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
7. [Bug 1003] GSM modem is not powered down when Linux is shut
down ([EMAIL PROTECTED])
8. [Bug 1003] GSM modem is not powered down when Linux is shut
down ([EMAIL PROTECTED])
9. [Bug 1003] GSM modem is not powered down when Linux is shut
down ([EMAIL PROTECTED])
10. [Bug 1005] U-boot passthrough does not work for current gsmd
([EMAIL PROTECTED])
11. [Bug 1003] GSM modem is not powered down when Linux is shut
down ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=937
------- Additional Comments From [EMAIL PROTECTED] 2007-11-17 23:09 -------
I'm still getting a similar error with the code I checked out this afternoon.
Please wait, programming the NAND flash...
Available alarm timers, in order of precedence:
unix
openmoko/flash.sh: line 88: 11928 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 120 seconds, giving up.
I'm running Ubuntu 7.10, kernel 2.6.22-14-generic.
------- 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=894
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
------- Additional Comments From [EMAIL PROTECTED] 2007-11-18 02:45 -------
Sorry, but what does the sleep command have to do with this bug? Imho it's
completely irrelevant. Basically, you made a change in libgsmd-tool and you're
saying that a bug that's in gsmd (not libgsmd-tool) is now fixed. How can it
possibly be fixed? This *is* a gsmd bug, not a libgsmd-tool bug.
Apart from that, S= command is flawed, you can't predict how long a command will
take and it definitely shouldn't be used in scripts. It's a hack and, even if
it may be useful for developers to test, the -w switch should be used instead.
Also please learn to use the "Resolution: FIXED" and "Resolution: WONTFIX"
bugzilla options. In some bugs you say that they will not be fixed and then you
mark it as "FIXED", it's illogical.
I can't understand why when you have a proper fix at hand, submitted on
bugzilla, you insist on wasting your time rewriting the code (and introducing
new bugs, changing function names to illogical ones, and replacing tabs by
spaces everywhere). If you see an error in some of the submitted patches, point
it out, discuss, and ask the submitter to resubmit. Ignoring is extremely rude
and it is currently destroying the gsmd project. The code quality has dropped
very badly since laf0rge left it and now the gsmd code looks like a "hello
world" made by a first-time C learner.
------- 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
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
------- Additional Comments From [EMAIL PROTECTED] 2007-11-18 02:54 -------
Mickey, I missed your comment before I came up with a patch (I will submit it
shortly), which does two things:
- startup in $HOME
- hardcode a set of colors in which alsamixer can be used successfully (too
dim before)
This program probably needs a .openmoko-terminalrc file to read, or perhaps some
gconf entries, in which colors, font, etc. can be customized, but for the time
being, I think the patch helps usability. I'll code that up (.rc/gconf) if
you're otherwise too busy.
As to your 2007-11-14 comment, remote shells all seem to start in "~", in my
experience at least, so I have enforced the same behavior here via getenv(HOME)
and passing it to the terminal widget.
Attachments will be the patch plus the updated bitbake file, which can be
ignored if you make the patch in SVN.
------- 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-18 02:57 -------
Created an attachment (id=381)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=381&action=view)
Patch for openmoko-terminal2 start directory and colors
------- 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-18 02:58 -------
Created an attachment (id=382)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=382&action=view)
Revised bitbake recipe to bring in new patch.
------- 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=129
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=276
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=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=808
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=835
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=933
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=945
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=961
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=978
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=995
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1003
------- Additional Comments From [EMAIL PROTECTED] 2007-11-18 08:03 -------
Created an attachment (id=383)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=383&action=view)
Adding api for powe on/off GSM modem
------- 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=1003
------- Additional Comments From [EMAIL PROTECTED] 2007-11-18 08:13 -------
Created an attachment (id=384)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=384&action=view)
/etc/rc0.d/K34modem
------- 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=1003
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-11-18 08:17 -------
Adding new api for power on/off modem in gsmd. With this patch and the script
when system is shut down, GSM modem off too. For NEO, you need to confirm that
if the firmware support [EMAIL PROTECTED] or not first.
------- 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=1005
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED]
Status|ASSIGNED |NEW
------- 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=1003
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
------- Additional Comments From [EMAIL PROTECTED] 2007-11-18 08:55 -------
The API for power on/off the GSM modem using gsmd is a necessary feature, but it
does not really resolve the issue reported by this bug. Specifically, the patch
and the K34modem script will *ONLY* accomplish the desired end effect *IFF* gsmd
is running.
The principle of least surprise requires that the system make every effort to
power off the GSM modem at shutdown, especially when that shutdown is due to the
failure or abnormal behavior of the software on the device. It is quite
reasonable and rational for a user to assume that if they were able to initiate
a power-off, and that the screen went blank, that the phone is truly *OFF*. By
making the power-off dependent upon gsmd, we really haven't solved this problem
for any of the cases where gsmd has failed, or if gsmd has lost communications
with the modem, or any of a huge number of failure modes.
I applaud the addition of the power-off ability to gsmd, but I think gsmd cannot
be trusted in the event that the user powers off the phone because of some sort
of problem with the phone's behavior.
I remain firmly convinced that at shutdown, we must:
A) Reset the modem
B) issue the [EMAIL PROTECTED] command
and do so with as little reliance on external processes, libraries, and
especially daemons as is possible, as we simply cannot assume that those things
are available or functional at shutdown.
------- 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
