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. Re: Openmoko Bug #2211: Windows instant reboot while
connecting Freerunner on USB (Openmoko Public Trac)
2. Re: Openmoko Bug #1744: Bluetooth don't power up after
suspend (Openmoko Public Trac)
3. Re: Openmoko Bug #1744: Bluetooth don't power up after
suspend (Openmoko Public Trac)
4. Openmoko Bug #2242: [Xglamo] crash with xcompmgr
(Openmoko Public Trac)
5. Openmoko Bug #2243: [Xglamo] some motion events are thrashed
(Openmoko Public Trac)
6. Re: Openmoko Bug #2242: [Xglamo] crash with xcompmgr
(Openmoko Public Trac)
7. Re: Openmoko Bug #2235: Monochrome display on resume
(Openmoko Public Trac)
8. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
9. Re: Openmoko Bug #2235: Monochrome display on resume
(Openmoko Public Trac)
--- Begin Message ---
#2211: Windows instant reboot while connecting Freerunner on USB
-----------------------------+----------------------------------------------
Reporter: psonek | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
No it's a different problem, the reboot thing is fixed some weeks ago but
it's still broken for actual RNDIS action so we leave the bug open for
now.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2211#comment:9>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1744: Bluetooth don't power up after suspend
-----------------------------+----------------------------------------------
Reporter: VDVsx | Owner: openmoko-kernel
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: System Software | Version: GTA02v6
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by TimoJyrinki):
(also andy-tracking as of today, 86247495c3d585)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1744#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1744: Bluetooth don't power up after suspend
-----------------------------+----------------------------------------------
Reporter: VDVsx | Owner: openmoko-kernel
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: System Software | Version: GTA02v6
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by balajirrao):
I see this. When the phone suspends with bluetooth on, it comes up
properly. But when suspended with bluetooth off, it can't be powered up.
Will look into it now.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1744#comment:8>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2242: [Xglamo] crash with xcompmgr
------------------------------+---------------------------------------------
Reporter: Richard.Kralovic | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: FSO-MS2
Severity: normal | Keywords: Xglamo, composite, crash
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
------------------------------+---------------------------------------------
I was playing a bit with the composite extension and xcompmgr (FSO
milestone 5, kernel 2.6.28, xserver-kdrive-
glamo-1_1.3.0.0+gitr9b28d998424c77fbc057dd3a022ccbb122793a52-r3). It works
quite ok, but Xglamo crashes occasionaly. It is quite easily reporducible
- just run xcompmgr and open a lot of applications. I was able to get the
following backtrace in gdb:
#0 0x000577f4 in KdOffscreenAlloc ()
#1 0x00050888 in kaaMoveInPixmap ()
#2 0x000509f4 in kaaPixmapUseScreen ()
#3 0x00050ba8 in kaaCopyNtoN ()
#4 0x000696ac in fbCopyRegion ()
#5 0x00069cbc in fbDoCopy ()
#6 0x0004fd28 in kaaCopyArea ()
#7 0x000ed180 in cwCopyArea ()
#8 0x000e8de4 in damageCopyArea ()
#9 0x000ed180 in cwCopyArea ()
#10 0x000e8de4 in damageCopyArea ()
#11 0x000398d0 in ProcCopyArea ()
#12 0x000b3b1c in XaceCatchDispatchProc ()
#13 0x0003b4c8 in Dispatch ()
#14 0x0002376c in main ()
You can see the full core dump at
http://kedrigern.dcs.fmph.uniba.sk/~riso/xglamo.dump
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2242>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2243: [Xglamo] some motion events are thrashed
------------------------------+---------------------------------------------
Reporter: Richard.Kralovic | Owner: openmoko-devel
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: unknown | Version: FSO-MS2
Severity: normal | Keywords: Xglamo
Haspatch: 1 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
------------------------------+---------------------------------------------
When the xserver is busy, it tries to "optimize" consecutive movement
events. In particular, it throws away some events that has not been
processed. This is very unpleasant behaviour when input method based on
gesture recognition (e.g., qwo) is used. In this case, quality of the
recognition is severly degraded.
As a workaround, it is sufficient to comment out lines 100-106 in
mi/mieq.c, as indicated by the attached patch (tested on xserver-kdrive-
glamo-1_1.3.0.0+gitr9b28d998424c77fbc057dd3a022ccbb122793a52-r3, FSO
milestone 5).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2243>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2242: [Xglamo] crash with xcompmgr
------------------------------+---------------------------------------------
Reporter: Richard.Kralovic | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: FSO-MS2
Severity: normal | Keywords: Xglamo, composite, crash
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
------------------------------+---------------------------------------------
Comment(by Richard.Kralovic):
I have found some bugs in koffscreen.c. Xglamo is more stable now,
although I haven't tested it very much yet. Patch to
hw/kdrive/src/koffscreen.c is attached.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2242#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2235: Monochrome display on resume
-----------------------------+----------------------------------------------
Reporter: zeroedout | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords: display, resume
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by nicolas.dufresne):
Fixed by the following patch: http://lists.openmoko.org/pipermail
/openmoko-kernel/2009-February/009115.html
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2235#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1841: white screen of death (WSOD) after resume
-----------------------+----------------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: GTA02v5
Severity: critical | Keywords: wsod,resume
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------+----------------------------------------------------
Comment(by nicolas.dufresne):
I'm surprise this one is still open bug. I guess some people may be
interested in the following patch: http://lists.openmoko.org/pipermail
/openmoko-kernel/2009-February/009115.html
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:121>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2235: Monochrome display on resume
-----------------------------+----------------------------------------------
Reporter: zeroedout | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords: display, resume
Haspatch: 1 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Changes (by Nytowl):
* haspatch: 0 => 1
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2235#comment:8>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
