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 264] package libelf-0.8.6-r0: task do_populate_staging:
failed ([EMAIL PROTECTED])
2. [Bug 264] package libelf-0.8.6-r0: task do_populate_staging:
failed ([EMAIL PROTECTED])
3. [Bug 215] fingerwheel crashes mainmenu when touching the
black part ([EMAIL PROTECTED])
4. [Bug 215] fingerwheel crashes mainmenu when touching the
black part ([EMAIL PROTECTED])
5. [Bug 215] fingerwheel crashes mainmenu when touching the
black part ([EMAIL PROTECTED])
6. [Bug 287] New: Charging Voltage not correctly exposed
([EMAIL PROTECTED])
7. [Bug 287] New: Charging Voltage not correctly exposed
([EMAIL PROTECTED])
8. [Bug 262] Indicate different charging mode in battery applet
([EMAIL PROTECTED])
9. [Bug 262] Indicate different charging mode in battery applet
([EMAIL PROTECTED])
10. [Bug 287] Charging Voltage not correctly exposed
([EMAIL PROTECTED])
11. [Bug 287] Charging Voltage not correctly exposed
([EMAIL PROTECTED])
12. [Bug 256] GSM Modem doesn't seem to work on some devices
([EMAIL PROTECTED])
13. [Bug 256] GSM Modem doesn't seem to work on some devices
([EMAIL PROTECTED])
14. [Bug 281] implicit declaration of function `strdup'
([EMAIL PROTECTED])
15. [Bug 281] implicit declaration of function `strdup'
([EMAIL PROTECTED])
16. [Bug 270] does our xserver need security updates?
([EMAIL PROTECTED])
17. [Bug 270] does our xserver need security updates?
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=264
------- Additional Comments From [EMAIL PROTECTED] 2007-03-19 13:21 -------
I ran into the same problem and fixed it by manually running "./configure
--enable-shared" in the libelf
dir, followed by a make. Then the shared lib was ready for installation so the
MokoMakefile continued
without problems.
Platform: Gentoo 32bit x86
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=264
------- Additional Comments From [EMAIL PROTECTED] 2007-03-19 13:21 -------
I ran into the same problem and fixed it by manually running "./configure
--enable-shared" in the libelf
dir, followed by a make. Then the shared lib was ready for installation so the
MokoMakefile continued
without problems.
Platform: Gentoo 32bit x86
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=215
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
------- Additional Comments From [EMAIL PROTECTED] 2007-03-19 18:11 -------
Mainmenu still crashes!
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=215
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
------- Additional Comments From [EMAIL PROTECTED] 2007-03-19 18:11 -------
Mainmenu still crashes!
------- 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=215
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
------- Additional Comments From [EMAIL PROTECTED] 2007-03-19 18:11 -------
Mainmenu still crashes!
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=287
Summary: Charging Voltage not correctly exposed
Product: Neo1973 Hardware
Version: unspecified
Platform: Neo1973
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: PMU (Power Management Unit)
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
[EMAIL PROTECTED]:~$ cat /sys/bus/i2c/devices/0-0008/chgcur
0
The "0" stays there, no matter whether anything (pc, wallplug charger) is
connected or not.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=287
Summary: Charging Voltage not correctly exposed
Product: Neo1973 Hardware
Version: unspecified
Platform: Neo1973
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: PMU (Power Management Unit)
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
[EMAIL PROTECTED]:~$ cat /sys/bus/i2c/devices/0-0008/chgcur
0
The "0" stays there, no matter whether anything (pc, wallplug charger) is
connected or not.
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=262
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
BugsThisDependsOn| |287
Status|NEW |ASSIGNED
------- Additional Comments From [EMAIL PROTECTED] 2007-03-20 01:19 -------
I will do this once sysfs reports anything else than "0".
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=262
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
BugsThisDependsOn| |287
Status|NEW |ASSIGNED
------- Additional Comments From [EMAIL PROTECTED] 2007-03-20 01:19 -------
I will do this once sysfs reports anything else than "0".
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=287
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
OtherBugsDependingO| |262
nThis| |
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=287
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
OtherBugsDependingO| |262
nThis| |
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=256
------- Additional Comments From [EMAIL PROTECTED] 2007-03-20 01:21 -------
I can reliably resolve this issue on a bv3 device with:
[EMAIL PROTECTED]:~$ echo 1 > /sys/devices/platform/gta01-pm-gsm.0/power_on
[EMAIL PROTECTED]:~$ cu -l /dev/ttySAC0
And then on a different console issue:
[EMAIL PROTECTED]:~$ stty -F /dev/ttySAC0 crtscts
The order is important for me because cu seems to disable hardware flow control.
Also gsmd never had problems for me, so everyone who suspects hardware problems
might want to try
[EMAIL PROTECTED]:~$ gsmd -F -s 115200 -p /dev/ttySAC0
and see if that returns any OK messages for the AT commands issued
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=256
------- Additional Comments From [EMAIL PROTECTED] 2007-03-20 01:21 -------
I can reliably resolve this issue on a bv3 device with:
[EMAIL PROTECTED]:~$ echo 1 > /sys/devices/platform/gta01-pm-gsm.0/power_on
[EMAIL PROTECTED]:~$ cu -l /dev/ttySAC0
And then on a different console issue:
[EMAIL PROTECTED]:~$ stty -F /dev/ttySAC0 crtscts
The order is important for me because cu seems to disable hardware flow control.
Also gsmd never had problems for me, so everyone who suspects hardware problems
might want to try
[EMAIL PROTECTED]:~$ gsmd -F -s 115200 -p /dev/ttySAC0
and see if that returns any OK messages for the AT commands issued
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=281
------- Additional Comments From [EMAIL PROTECTED] 2007-03-20 01:46 -------
the include string.h has the following definition:
#if defined __USE_SVID || defined __USE_BSD || defined __USE_XOPEN_EXTENDED
/* Duplicate S, returning an identical malloc'd string. */
extern char *strdup (__const char *__s)
__THROW __attribute_malloc__ __nonnull ((1));
#endif
For some reason none of those defines is used, AFAIK __USE_XOPEN_EXTENDED should
be. Maybe someone can clear up that issue for us?
So if you do the following instead of just including <string.h> it works:
#define __USE_XOPEN_EXTENDED
#include <string.h>
Anyway IMHO that is a temporary workaround.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=281
------- Additional Comments From [EMAIL PROTECTED] 2007-03-20 01:46 -------
the include string.h has the following definition:
#if defined __USE_SVID || defined __USE_BSD || defined __USE_XOPEN_EXTENDED
/* Duplicate S, returning an identical malloc'd string. */
extern char *strdup (__const char *__s)
__THROW __attribute_malloc__ __nonnull ((1));
#endif
For some reason none of those defines is used, AFAIK __USE_XOPEN_EXTENDED should
be. Maybe someone can clear up that issue for us?
So if you do the following instead of just including <string.h> it works:
#define __USE_XOPEN_EXTENDED
#include <string.h>
Anyway IMHO that is a temporary workaround.
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=270
------- Additional Comments From [EMAIL PROTECTED] 2007-03-20 01:52 -------
Make sure it is started with the -nolisten tcp option. That alone already
removes a host of possible security issues. And indeed the security issues you
highlight are highly unlikely to apply to the xserver on OpenMoko.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=270
------- Additional Comments From [EMAIL PROTECTED] 2007-03-20 01:52 -------
Make sure it is started with the -nolisten tcp option. That alone already
removes a host of possible security issues. And indeed the security issues you
highlight are highly unlikely to apply to the xserver on OpenMoko.
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
