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 1202] New: Packagekit may crash while installing
([EMAIL PROTECTED])
2. [Bug 1202] Packagekit may crash while installing
([EMAIL PROTECTED])
3. [Bug 90] GSM TS07.10 multiplex missing
([EMAIL PROTECTED])
4. [Bug 1203] New: neod emits far too much debugging output
([EMAIL PROTECTED])
5. [Bug 1153] Dialer talking window isn't closed, when caller
hung up call ([EMAIL PROTECTED])
6. [Bug 1031] Add SD driver on gta02
([EMAIL PROTECTED])
7. [Bug 341] Meta: Phase 2 is not releasable
([EMAIL PROTECTED])
8. [Bug 1204] New: Mobile keypad won't go away when selecting
qwerty keyboard ([EMAIL PROTECTED])
9. [Bug 1205] New: Qwerty keyboard covers button when screen in
locked mode ([EMAIL PROTECTED])
10. [Bug 1206] New: Even when "Dim only, don't lock" slected,
screen is locked ([EMAIL PROTECTED])
11. [Bug 1116] busybox 1.2.1 is old and broken -- 1.7.2 works
fine ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1202
Summary: Packagekit may crash while installing
Product: OpenMoko
Version: current svn head
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Applications & Dependencies
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
After installing and uninstalling for many times.
The packagekitd may go away.
Maybe it is because *opkg fork failed* but I am not knowing why now.
It's seems nothing related with assassin.
----------- LOG --------------------
[EMAIL PROTECTED]:~$ assassin install 'tcl;8.4.11-r5;armv4t;'
DEBUG: (assassin.c, 53): get_properties: Type: 0 status: 0 T->package is
tcl;8.4.11-r5;armv4t;
DEBUG: (pkutil.c, 105): packagekit_thread: g_main_loop_run starts
DEBUG: (pkutil.c, 64): pkg_client_initialize: Getting new pk_connection
DEBUG: (pkutil.c, 67): pkg_client_initialize: Getting new pk_client
DEBUG: (pkutil.c, 21): check_connection: check PASS!!
DEBUG: (pkutil.c, 32): check_packagekit: Connection is fine!!
DEBUG: (confirm_command.c, 65): do_confirm:
CP.target->package=tcl;8.4.11-r5;armv4t;
DEBUG: (gears.c, 24): __autolayout_type_message: type x=12,y= 0,w=104,h=32
DEBUG: (gears.c, 31): __autolayout_button: button move to ( 0,125)
DEBUG: (gears.c, 31): __autolayout_button: button move to (240,125)
DEBUG: (assassin.c, 79): main: ecore main loop runs
DEBUG: (confirm_command.c, 18): assassin_confirm_positive: Yes selected!!
DEBUG: (confirm_command.c, 21): assassin_confirm_positive:
cp->target->package=tcl;8.4.11-r5;armv4t;
DEBUG: (actions.c, 160): action: Try to install: tcl;8.4.11-r5;armv4t;
DEBUG: (gears.c, 162): new_Progressbar: text = Downloading
DEBUG: (actions.c, 122): pk_status_change_cb: 0;daeebcde;data Status: setup 0
DEBUG: (actions.c, 135): pk_status_change_cb: target->status=1
DEBUG: (actions.c, 122): pk_status_change_cb: 0;daeebcde;data Status: install
7
DEBUG: (actions.c, 135): pk_status_change_cb: target->status=3
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=0
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 0
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 0
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 2
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 4
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=4
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 4
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 6
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 8
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 10
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 12
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 14
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 16
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 18
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=18
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 18
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 20
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 22
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 24
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 26
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 29
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 31
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 33
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=33
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 33
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 35
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 37
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 39
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 41
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 43
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 45
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 47
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=47
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 47
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 49
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 51
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 53
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 55
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 57
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 59
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 62
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 64
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=64
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 64
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 66
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 68
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 70
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 72
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 74
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 76
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 78
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=78
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 78
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 80
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 82
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 84
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 86
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 88
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 90
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 92
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 95
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 97
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=97
DEBUG: (actions.c, 51): eavs_progress_bar_cb: progress is 97
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 99
DEBUG: (actions.c, 92): pk_progress_cb: Progress Update 100
DEBUG: (actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2
progress=100
opkg: fork failed
DEBUG: (pkutil.c, 54): pk_connection_changed_cb: Connection changed event
happened!!
DEBUG: (pkutil.c, 57): pk_connection_changed_cb: The daemon went away...DEBUG:
(actions.c, 23): eavs_progress_bar_cb: Update Progess bar status=2 progress=100
------- 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=1202
------- Additional Comments From [EMAIL PROTECTED] 2008-01-29 15:28 -------
I have tried using pkcon to install and remove a package several times and I
have not managed to reproduce this error.
Today I fixed an issue with the progress bar code which may have resulted in a
crash. Could you please test again using pkcon and see if you can still
reproduce this bug with the latest code. If you can, please run packagekitd
inside gdb and attach a stack trace if it 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=90
------- Additional Comments From [EMAIL PROTECTED] 2008-01-29 16:28 -------
Writchie: ping?
------- 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=1203
Summary: neod emits far too much debugging output
Product: OpenMoko
Version: 2007.2
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P2
Component: neod
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
This is perhaps an unwarranted report (marking as minor), but neod displays an
awful lot of debugging information. Two lines of text every time I press the
touch screen is quite irritating, especially given the jitter (so often a single
press registers as several); it makes reading debugging output from other
applications more cumbersome than it need be.
Is it possible that we can have the verbosity of the debugging output from neod
turned down by default? Is it really necessary to emit debugging information
when the touch-screen is pressed? Perhaps, if we can't tone this down, can we at
least redirect neod's output to its own file by default?
------- 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=1153
------- Additional Comments From [EMAIL PROTECTED] 2008-01-29 17:32 -------
You've communicated to me that the bug you experience is that the window closes
when the call is redirected to voicemail, which doesn't match this description -
if this is indeed the case, can we leave this one closed and open a new report
please? Otherwise this may get confusing.
------- 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=1031
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2008-01-29 22:23 -------
This is resolved in current svn / git.
------- 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=341
Bug 341 depends on bug 1031, which changed state.
Bug 1031 Summary: Add SD driver on gta02
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1031
What |Old Value |New Value
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- 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=1204
Summary: Mobile keypad won't go away when selecting qwerty
keyboard
Product: OpenMoko
Version: current svn head
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Autobuilds / Snapshots
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Since the default keyboard was changed to be a mobile key-pad style keyboard, it
isn't possible to remove it, at least from the GUI that is provided.
The little keyboard-icon at the top will provide the regular qwerty-keyboard,
however not *instead* of the mobile key-pad, but together with it.
And there is way to little screen area to have both present at the same time.
Last seen at today's daily build:
http://buildhost.openmoko.org/daily/neo1973/deploy/glibc/images/neo1973/OpenMoko-openmoko-devel-image-glibc-ipk-P1-Snapshot-20080129-fic-gta01.rootfs.tar.gz
------- 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=1205
Summary: Qwerty keyboard covers button when screen in locked mode
Product: OpenMoko
Version: current svn head
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-keyboard
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Since the appearance of the mobile keypad the qwerty keyboard can be misplaced
when in use:
1.Select power savings mode to "Dim only, don't lock"
2.Go into Message screen and select to have the qwerty keyboard appear.
3.Now both keypad and keyboard are present on the screen.
4.Wait for the screen to lock (and the selection was "don't lock" in #1 above
:-)
5.Tap on the screen to have the light come on
6.Notice that the OpenMoko icon that should be dragged from the bottom to the
top lock, to unlock the screen, is now covered with the qwerty keyboard
7.It is not possible to drag the keyboard away or in some other neat way get to
the OpenMoko icon, so it seems like a dead-lock only fixable by reboot.
8.Not good
However, there is a funny work-around to rebooting:
1.Activate the AUX menu by pressing and holding the AUX button for a few seconds
2.Select screenshot
3.Select Browse
4.Notice the "X Save File" bar at the top.
5.Drag that bar downwards and the qwerty keyboard icon will appear at the top.
6.Push the qwerty keyboard icon in order to disable that selection
7.The keypad appears instead of the qwerty keyboard
8.Select Cancel and Cancel and the locked screen re-appears
9.Now you may drag the OpenMoko icon to the top, to unlock the screen
This was found on the latest build:
http://buildhost.openmoko.org/daily/neo1973/deploy/glibc/images/neo1973/OpenMoko-openmoko-devel-image-glibc-ipk-P1-Snapshot-20080129-fic-gta01.rootfs.tar.gz
------- 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=1206
Summary: Even when "Dim only, don't lock" slected, screen is
locked
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-screensaver
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
When entering the Power Menu by pushing and holding the power button for a few
seconds, Power Management has three options:
1.Dim first, then lock
2.Dim only, don't lock
3.Disabled
When selecting #2 the screen dims after 10sec and then also locks after 50sec.
which was unexpected.
#1 works the same as #2.
------- 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=1116
------- Additional Comments From [EMAIL PROTECTED] 2008-01-30 03:12 -------
The default set of utilities configured by busybox could also stand to be
updated. In both 1.2.1 and 1.7.2 (and for that matter, 1.8.2 in Poky's
repository), the provided (default) defconfig specifies:
* no 'nice' command (but 'renice' is there);
* 'xargs' doesn't support the '-0' flag (even though 'find' has '-print0');
and
* 'find' doesn't have the '-delete' expression
Other changes might also be useful, so I'd encourage a thorough re-evaluation of
all of the default options by someone who knows their stuff.
And to fix part of another bug I submitted (that would be bug #870), I
personally would set "CONFIG_INSTALL_NO_USR=y" so people can mount a memory card
partition at /usr and still allow the boot/init process to complete successfully
without it.
------- 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
