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 477] MokoTreeView is Redundant
([EMAIL PROTECTED])
2. [Bug 453] Use gconf bridge to achieve stateful applications
([EMAIL PROTECTED])
3. [Bug 445] MokoPanedWindow: rename upper/lower to
navigation/details ([EMAIL PROTECTED])
4. [Bug 446] Add MokoNavigationWindow containing a fullscreen
button ([EMAIL PROTECTED])
5. [Bug 506] New: Add qemu component in the Openmoko bugzilla
([EMAIL PROTECTED])
6. [Bug 507] New: make qemu failing
([EMAIL PROTECTED])
7. [Bug 508] New: Icon theme is not being applied properly
([EMAIL PROTECTED])
8. [Bug 509] New: Font size in year view should be decreased
([EMAIL PROTECTED])
9. [Bug 446] Add MokoNavigationWindow containing a fullscreen
button ([EMAIL PROTECTED])
10. [Bug 509] Font size in year view should be decreased
([EMAIL PROTECTED])
11. [Bug 507] make qemu failing
([EMAIL PROTECTED])
12. [Bug 421] systray applet only shows white rectangles
([EMAIL PROTECTED])
13. [Bug 393] We need a notification API
([EMAIL PROTECTED])
14. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=477
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From [EMAIL PROTECTED] 2007-04-23 13:02 -------
That may seem to be the case for _now_, yes. However, the mid term plan is to
add more common functionality to MokoTreeView and I rather not have all
applications having to switch to it later.
------- 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=453
------- Additional Comments From [EMAIL PROTECTED] 2007-04-23 13:05 -------
For a start: View Mode, Split Percentage for Splitter, Filter Menu Selection
------- 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=445
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
------- Additional Comments From [EMAIL PROTECTED] 2007-04-23 13:43 -------
I'll do it tomorrow and will catch up w/ all applications in our SVN. Please
adjust contacts as well.
------- 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=446
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
Status|NEW |ASSIGNED
------- Additional Comments From [EMAIL PROTECTED] 2007-04-23 13:45 -------
Question is whether we just add a MokoNavigationWindow (somewhat duplicating the
functionality of MokoDetailsWindow) or combine these two features into one
seperate class derived from GtkScrolledWindow.
What do you think?
------- 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=506
Summary: Add qemu component in the Openmoko bugzilla
Product: Site Infrastructure
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Bugzilla
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Hey guys..I had a bug in the qemu that comes with a toolchain and was completely
at a loss regarding what component i should file the bug under..Requesting to
add qemu component so that bugs relating to it would be filed there..
Thank you,
Sudharshan S
------- 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=507
Summary: make qemu failing
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: major
Priority: P3
Component: Applications & Dependencies
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
I am not sure if this is the right category..so apologies in advance.
While doing a make qemu I am getting the following error in the current SVN
head.
[EMAIL PROTECTED] ~/Projects/openmoko $ cat log
[ -e build/qemu ] || \
( cd build ; mkdir -p qemu )
[ -e build/qemu/Makefile ] || \
( . ./setup-env ; cd build/qemu ; \
${OMDIR}/openmoko/trunk/src/host/qemu-neo1973/configure \
--target-list=arm-softmmu )
[ -e build/qemu/openmoko ] || \
( . ./setup-env ; cd build/qemu ; mkdir openmoko ; \
for f in ${OMDIR}/openmoko/trunk/src/host/qemu-neo1973/openmoko/* ;
do \
ln -s $f openmoko/`basename $f` ; \
done )
[ -d stamps ] || mkdir stamps
touch stamps/qemu
( cd build/qemu ; make )
make[1]: Entering directory `/home/sudharsh/Projects/openmoko/build/qemu'
make -C arm-softmmu all
make[2]: Entering directory
`/home/sudharsh/Projects/openmoko/build/qemu/arm-softmmu'
gcc32 -Wall -O2 -g -fno-strict-aliasing -mpreferred-stack-boundary=2
-fomit-frame-pointer -falign-functions=0 -fno-gcse -fno-reorder-blocks
-fno-optimize-sibling-calls -I. -I..
-I/home/sudharsh/Projects/openmoko/openmoko/trunk/src/host/qemu-neo1973/target-arm
-I/home/sudharsh/Projects/openmoko/openmoko/trunk/src/host/qemu-neo1973
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-I/home/sudharsh/Projects/openmoko/openmoko/trunk/src/host/qemu-neo1973/fpu
-DHAS_AUDIO -DHIGH_LATENCY
-I/home/sudharsh/Projects/openmoko/openmoko/trunk/src/host/qemu-neo1973/slirp -c
-o op.o
/home/sudharsh/Projects/openmoko/openmoko/trunk/src/host/qemu-neo1973/target-arm/op.c
make[2]: Leaving directory
`/home/sudharsh/Projects/openmoko/build/qemu/arm-softmmu'
make[1]: Leaving directory `/home/sudharsh/Projects/openmoko/build/qemu'
/home/sudharsh/Projects/openmoko/openmoko/trunk/src/host/qemu-neo1973/target-arm/op.c:
In function 'op_iwmmxt_movq_wRn_M0':
/home/sudharsh/Projects/openmoko/openmoko/trunk/src/host/qemu-neo1973/target-arm/op.c:1374:
error: unable to find a register to spill in class 'GENERAL_REGS'
/home/sudharsh/Projects/openmoko/openmoko/trunk/src/host/qemu-neo1973/target-arm/op.c:1374:
error: this is the insn:
(insn:HI 11 22 12 0
/home/sudharsh/Projects/openmoko/openmoko/trunk/src/host/qemu-neo1973/target-arm/op.c:1373
(set (mem/s/j:DI (plus:SI (plus:SI (mult:SI (reg/f:SI 58 [ __op_param1.884 ])
(const_int 8 [0x8]))
(reg/f:SI 59 [ env.883 ]))
(const_int 848 [0x350])) [0 <variable>.iwmmxt.regs S8 A32])
(reg:DI 60 [ <variable>.iwmmxt.val ])) 56 {*movdi_2}
(insn_list:REG_DEP_TRUE 9 (insn_list:REG_DEP_TRUE 10 (nil)))
(expr_list:REG_DEAD (reg:DI 60 [ <variable>.iwmmxt.val ])
(expr_list:REG_DEAD (reg/f:SI 58 [ __op_param1.884 ])
(expr_list:REG_DEAD (reg/f:SI 59 [ env.883 ])
(nil)))))
/home/sudharsh/Projects/openmoko/openmoko/trunk/src/host/qemu-neo1973/target-arm/op.c:1374:
confused by earlier errors, bailing out
make[2]: *** [op.o] Error 1
make[1]: *** [subdir-arm-softmmu] Error 2
make: *** [build-qemu] Error 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=508
Summary: Icon theme is not being applied properly
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Theming
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Icon theme is not being applied properly, and therefore some icons do not appear
in the OpenMoko style.
------- 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=509
Summary: Font size in year view should be decreased
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-dates
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
As reported by Mickey:
"Font size in year view should be decreased"
------- 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=446
------- Additional Comments From [EMAIL PROTECTED] 2007-04-23 16:18 -------
Just to be clear, the only feature that MokoDetailsWindow adds to
GtkScrolledWindow is to add the maximise button? If this is the same for both
the Details and Navigation areas, then it would be good if they could both use
the same widget.
------- 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=509
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
------- Additional Comments From [EMAIL PROTECTED] 2007-04-23 16:19 -------
Rob, could you take a look at what is needed to do this?
------- 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=507
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From [EMAIL PROTECTED] 2007-04-23 17:49 -------
well..I didnt notice that i dont have gcc3 required to build the image
correctly...Sorry for the idiocy..
------- 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
----------------------------------------------------------------------------
AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED]
Status|ASSIGNED |NEW
------- Additional Comments From [EMAIL PROTECTED] 2007-04-24 00:03 -------
Short status update:
I'm working the startup-notifier applet migration right now. Input manager
follow afterwards.
------- 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=393
------- Additional Comments From [EMAIL PROTECTED] 2007-04-24 01:13 -------
notification-daemon really seems to be what we want to use here, but
it is missing some functionality:
We want the notifications to have an icon present in the panel as long
as the notification is active (even when the actual notification popup
has expired.
i.e. a message arrives: A message icon should appear in the panel and a
notification popup informing us about the Sender and providing buttons
for specific actions ("Read now", "Read later", "Delete"). After 10 seconds
the nofification popup should disappear, leaving the message icon in the
panel. If I click on the message icon the notification should pop up again.
If I read the message through the regular application the icon will disappear.
These are the unobtrusive notifications. We also want to have notifications
that the user *has* to react to.
This would be suitable for most users in case of an incoming call.
Which type of notification is used needs to be configurable by notification
metadata (category, urgency, appname).
------- 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=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=204
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=298
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=379
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=408
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=469
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=470
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=471
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
