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 747] uicmoc4-native_4.3.1.bb
([EMAIL PROTECTED])
2. [Bug 741] Image of Neo hardware shows debug board
([EMAIL PROTECTED])
3. [Bug 831] moko_gsmd_connection_init should check for multiple
instances ([EMAIL PROTECTED])
4. [Bug 788] Starting or stopping gsmd completely locks up the
Neo ([EMAIL PROTECTED])
5. [Bug 873] New: Openmoko-Today app is in tiny window of about
200px by 100px on latest images
([EMAIL PROTECTED])
6. [Bug 873] Openmoko-Today app is in tiny window of about 200px
by 100px on latest images ([EMAIL PROTECTED])
7. [Bug 873] Openmoko-Today app is in tiny window of about 200px
by 100px on latest images ([EMAIL PROTECTED])
8. [Bug 873] Openmoko-Today app is in tiny window of about 200px
by 100px on latest images ([EMAIL PROTECTED])
9. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
10. [Bug 873] Openmoko-Today app is in tiny window of about 200px
by 100px on latest images ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=747
------- Additional Comments From [EMAIL PROTECTED] 2007-09-16 13:24 -------
hi,
the patch to add QT+= network in uic3.pro (attachment id 310), solves the
problems. Confirmed on gentoo with gcc 4.2.0 and 4.1.2
------- 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=741
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |REMIND
------- Additional Comments From [EMAIL PROTECTED] 2007-09-16 15:05 -------
Errr.. I think this bug should go to Tony. The last image of debug board
showed on the wiki was shot by Tony. I don't have a debug board on hand, nor
do I know how would you like it to be shot. Unless you are talking about
bring it to the photographer for a picture taking? -Liane
------- 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=831
------- Additional Comments From [EMAIL PROTECTED] 2007-09-16 22:27 -------
The issue here and with bug #385 is identical to that of starting X and its
first clients on any distro. It would be enough for the init scripts to make
sure that gsmd is ready to accept clients before starting the GSM applet and the
dialer, for example by making gsmd fork only after making the socket available,
or by making gsmd execute appropriate session scripts. Similarly rerunning gsmd
on a crash can happen in the init scripts like restarting xinit by the gdm.
------- 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=788
------- Additional Comments From [EMAIL PROTECTED] 2007-09-16 23:11 -------
The kernel should not allow user space to lock-up the system by enabling or
disabling hardware flow control (by mistake or not). This wouldn't happen if the
UART txrdy polling was in a separate kernel thread, but it would still be wrong.
The situation here is that hardware flow control should never be enabled - in
fact the entire tty should not be present (as if UART0 wasn't listed in
gta01_uartcfgs[] in arch/arm/mach-s3c2410/mach-gta01.c) whenevet there is
nothing connected to UART0, i.e. the modem is off and no debug board is
connected. I'm not sure if this could be achieved by calling
platform_device_unregister(&s3c24xx_uart_src[0]) when the modem is being
disabled, and at the same time enabling the clear-to-send pin as an IRQ source.
When the IRQ is asserted it would re-register UART0 by calling
platform_device_register(&s3c24xx_uart_src[0]).
------- 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=873
Summary: Openmoko-Today app is in tiny window of about 200px by
100px on latest images
Product: OpenMoko
Version: current svn head
Platform: Neo1973
URL: http://scap.linuxtogo.org/files/d6494eede61014ac3001e5b1
217c5cfd.png
OS/Version: Linux
Status: NEW
Severity: critical
Priority: P4
Component: openmoko-today
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
I'm running the current images Snapshot 20070916 rootfs with 20070916 kernel
fic-gta01 2.6.22.5-moko11+svnr2937-r0 and u-boot from
http://buildhost.openmoko.org/snapshots/2007.08/images/u-boot-gta01bv4-1.2.0+git8993e54b6f397973794f3d6f47d3b3c0c98dd4f6+svn20070819-r0.bin
(known to work) http://buildhost.openmoko.org/snapshots/2007.08/images/
And, I have removed "console=ttySAC0,115200" from bootargs_base
After booting, i get the screenshot at the URL attached to this with what looks
like the openmoko-today app thinking the window is small.
If I change to the dialer, then its gets a bit bigger, and also the screenshot
window appears centered in the X window...so, must not be an X issue. See the
dialer:
http://scap.linuxtogo.org/files/82cfb5c0b8893d4c937bcbb0609149ed.png
I'm trying to track this down...I'm attaching the log when I run
/etc/init.d/xserver-nodm to reboot X11
------- 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=873
------- Additional Comments From [EMAIL PROTECTED] 2007-09-16 23:42 -------
Created an attachment (id=311)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=311&action=view)
This is the log of debug messages upon running xserver-nodm
T
------- 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=873
------- Additional Comments From [EMAIL PROTECTED] 2007-09-17 00:53 -------
I would guess that matchbox-window-manager has not started, for whatever reason.
Please try `ps | grep matchbox` to determine if matchbox-window-manager is
running after X starts.
------- 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=873
------- Additional Comments From [EMAIL PROTECTED] 2007-09-17 03:17 -------
Ok, I did this and you are right, matchbox-window-manager is not running, so I
tried to start and got this:
[EMAIL PROTECTED]:~$
(process:1188): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to execute dbus-launch to autolaunch D-Bus session
GConf Error: No D-BUS daemon running
xpm file invalid*** glibc detected *** matchbox-window-manager: double free or
corruption (top): 0x0004b3c0 ***
[1] + Aborted matchbox-window-manager -display :0
So, its either the dbus connection problem or the glibc corruption...is there a
fix?
Here is a backtrace, but appears that matchbox-window-manager is not in debug
mode. Is there a way to get that and/or run in debug mode.
(gdb) run -display :0
Starting program: /usr/bin/matchbox-window-manager -display :0
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(process:1514): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to execute dbus-launch to autolaunch D-Bus session
GConf Error: No D-BUS daemon running
xpm file invalid*** glibc detected *** /usr/bin/matchbox-window-manager: double
free or corruption (top): 0x0004b3c0 ***
Program received signal SIGABRT, Aborted.
0x40331d6c in raise () from /lib/libc.so.6
(gdb) bt
#0 0x40331d6c in raise () from /lib/libc.so.6
#1 0x40333194 in abort () from /lib/libc.so.6
Backtrace stopped: frame did not save the PC
------- 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=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=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=589
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=742
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=800
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=873
------- Additional Comments From [EMAIL PROTECTED] 2007-09-17 10:21 -------
The d-bus environment variables need to be set in order for a program to connect
to d-bus. The easiest way to do this is to use `dbus-launch <application>`.
You need to install debug packages to enable debug information. These packages
are the same name as their normal package counterpart, but with a -dbg suffix.
e.g. you may want to install matchbox-wm-dbg.
------- 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
