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 379] trove / browsing shows no projects
([EMAIL PROTECTED])
2. [Bug 544] Link to java-pkg-devel mailing list is broken
([EMAIL PROTECTED])
3. [Bug 567] New: I/O errors on flash and frozen fs
([EMAIL PROTECTED])
4. [Bug 567] I/O errors on flash and frozen fs
([EMAIL PROTECTED])
5. [Bug 567] I/O errors on flash and frozen fs
([EMAIL PROTECTED])
6. [Bug 567] I/O errors on flash and frozen fs
([EMAIL PROTECTED])
7. [Bug 421] systray applet only shows white rectangles
([EMAIL PROTECTED])
8. [Bug 421] systray applet only shows white rectangles
([EMAIL PROTECTED])
9. [Bug 421] systray applet only shows white rectangles
([EMAIL PROTECTED])
10. [Bug 421] systray applet only shows white rectangles
([EMAIL PROTECTED])
11. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
12. [Bug 553] gta01-pm-bt.ko is missing from modules
([EMAIL PROTECTED])
13. [Bug 553] gta01-pm-bt.ko is missing from modules
([EMAIL PROTECTED])
14. [Bug 553] gta01-pm-bt.ko is missing from modules
([EMAIL PROTECTED])
15. [Bug 464] GSM modem passthrough mode in u-boot
([EMAIL PROTECTED])
16. [Bug 195] passthrough mode (Directly use GSM Modem from PC
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=379
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-05-18 16:22 -------
The gforge package maintainer forget to enable the pgsql module for php4-cli.
Enable it by editing "/etc/php4/cli/conf.d/pgsql.ini".
Then, wait for the crond to daily recalculate of the sums under the trove map or
execute yourself.
------- 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=544
------- Additional Comments From [EMAIL PROTECTED] 2007-05-18 17:36 -------
The bug is probably from mal-configuration of mailman.
So I change /etc/mailman/httpd.conf from
ScriptAlias /cgi-bin/mailman/ /usr/lib/cgi-bin/mailman/
to
ScriptAlias /mailman/ /var/lib/mailman/cgi-bin/
I think it should be identical to /etc/gforge/httpd.conf
I can't test because it seems that the more information page is generated when
the project is created.
I will verify the result when a new project is created.
------- 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=567
Summary: I/O errors on flash and frozen fs
Product: OpenMoko
Version: unspecified
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: major
Priority: P2
Component: kernel
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Hardware: GTA01Bv03 (phase 0)
Kernel: Linux version 2.6.20.2-moko8 ([EMAIL PROTECTED]) (gcc version 4.1.1) #56
PREEMPT Sun Apr 8 13:58:03 CEST 2007
u-boot: I think 1.2.0-moko7 (getting to the u-boot prompt isn't stricly easy)
The whole thing started, when I downloaded openmoko-theme-standard.ipk to tmpfs
and tried to install it using ipkg install *.ipk. I got a few Input/Output
errors on files and the ipkg command hung.
Logging in via ssh still worked. And all commands, which were still in RAM,
worked fine. But any access to jffs2 locked up that command.
I could grab dmesg output, which contains a kernel-oops. (will be attached to
this bug as write-oops.dmesg)
As /sbin/halt.sysvinit (for "halt -p -d -i -p") was not in RAM (and I copied a
fresh one via scp to tmpfs) and some other needed stuff was not available, I had
to hard power off the machine (remove battery, half minute pressing power-button
did not work).
The next day, the machine seemed to boot fine. Until the fs gave me again I/O
errors (this time I did not try to write to it explicitly). This time I have a
bigger dmesg, which goes back to the boot. (will be attached to this bug as
boot_and_jffs2notices.dmesg).
Again I had to remove the battery, as I still haven't found the node in /sys,
that will shut down the phone IMMEDIATELY when echoing something into it.
------- 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=567
------- Additional Comments From [EMAIL PROTECTED] 2007-05-18 22:53 -------
Created an attachment (id=157)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=157&action=view)
write-oops.dmesg
The first dmesg capture, after explicitly writing to jffs2.
------- 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=567
------- Additional Comments From [EMAIL PROTECTED] 2007-05-18 22:54 -------
Created an attachment (id=158)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=158&action=view)
boot_and_jffs2notices.dmesg
Second instance, this time no explicit write.
------- 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=567
------- Additional Comments From [EMAIL PROTECTED] 2007-05-19 03:00 -------
I think this might be similar to bug #245. We've had a memory initialization
bug that resulted in memory corruption as soon as the kernel used the upper 64MB
of RAM. That memory corruption can obviously result in filesystem corruption as
soon as pages get written out to disk.
I'd recommend to install a way more up-to-date u-boot, kernel and rootfs image
and test again.
------- 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=421
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
------- Additional Comments From [EMAIL PROTECTED] 2007-05-19 03:42 -------
The matchbox-panel-2 startup notifier, openmoko-panel-startup, works fine now.
It is already in svn and tested.
I already got a review from Matthew for the matchbox vanilla version. We should
be able to merge this into matchbox svn soon.
------- 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=421
------- Additional Comments From [EMAIL PROTECTED] 2007-05-19 03:44 -------
Created an attachment (id=159)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=159&action=view)
openmoko-panel-startup oe infrastructure
Mickey, please add this to svn as I don't have the permissions for the oe dir.
------- 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=421
------- Additional Comments From [EMAIL PROTECTED] 2007-05-19 03:50 -------
In terms of the input manager applet.
Matthew and Ross had worked out a gtk input method which let the keyboard popup
once a textentry field is in use.
http://svn.o-hand.com/repos/matchbox/trunk/matchbox-keyboard/gtk-im/
It is pretty new and I have not tested it yet, but I will do this next week.
The only drawback I see is that we still need somekind of proxy or other visible
thing to switch between the different input methods. This brings me to the
question if we will stay with three different input methods: matchbox-keyboard,
openmoko-keyboard and stroke recognition
------- 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=421
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #159 is|0 |1
obsolete| |
------- Additional Comments From [EMAIL PROTECTED] 2007-05-19 04:14 -------
Created an attachment (id=160)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=160&action=view)
Fixed patch. This one inlcudes the needed bitbake recipe
------- 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 ---
[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=69
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=70
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=137
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=412
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=422
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=448
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=470
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=471
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=536
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=540
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=541
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=555
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=553
------- Additional Comments From [EMAIL PROTECTED] 2007-05-19 05:19 -------
even after
modprobe hci_usb
and
echo 1>/sys/bus/platform/devices/gta01-pm-bt.0/power_on
the bluetooth adapter does not appear using hciconfig -a
I've tried this on the latest dev image and on an image I built using
mokomakefile. Same result.
------- 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=553
------- Additional Comments From [EMAIL PROTECTED] 2007-05-19 06:05 -------
What hardware revision do you have? "P1 device" doesn't really make too much
sense, since P1 still has not started yet.
------- 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=553
------- Additional Comments From [EMAIL PROTECTED] 2007-05-19 07:58 -------
ok sorry I just assumed it was a p1 since it arrived very recently...
hardware gta01
revision 0240
------- 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=464
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
------- Additional Comments From [EMAIL PROTECTED] 2007-05-19 08:00 -------
*** This bug has been marked as a duplicate of 195 ***
------- 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=195
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
------- Additional Comments From [EMAIL PROTECTED] 2007-05-19 08:00 -------
*** Bug 464 has been marked as a duplicate of this bug. ***
------- 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
