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 #1627: [Dialer] The bottom bar menu show
"Mute" when incoming a call even setting slient or vibrate only
(Openmoko Public Trac)
2. Re: Openmoko Bug #1786: GtkButton inner_border theme change
(Openmoko Public Trac)
3. Re: Openmoko Bug #1786: GtkButton inner_border theme change
(Openmoko Public Trac)
4. Re: Openmoko Bug #1627: [Dialer] The bottom bar menu show
"Mute" when incoming a call even setting slient or vibrate only
(Openmoko Public Trac)
5. Re: Openmoko Bug #1983: eth0 doesn't exist / Oops during
bootup (Openmoko Public Trac)
6. Openmoko Bug #1992: Suspend/Resume plays up when initiated
manually (Openmoko Public Trac)
7. Openmoko Bug #1992: Suspend/Resume plays up when initiated
manually (Openmoko Public Trac)
8. Re: Openmoko Bug #1867: Dhclient is not working
(Openmoko Public Trac)
--- Begin Message ---
#1627: [Dialer] The bottom bar menu show "Mute" when incoming a call even
setting
slient or vibrate only
---------------------------+------------------------------------------------
Reporter: regina_kim | Owner: zecke
Type: defect | Status: reopened
Priority: normal | Milestone: Om2008.9
Component: Qtopia | Version:
Severity: major | Resolution:
Keywords: must have | Blockedby:
Reproducible: | Blocking:
---------------------------+------------------------------------------------
Comment(by charlie):
Thanks for the hint Holger.
I just had a look, ehehe in fact it is not that simple : the m_actionMute
only corresponds to the entry in the menu you get when you click the
option button. So where does the 'mute' button comes from ? Well, it is
simply the back button with the label set to 'Mute' :
QSoftMenuBar::setLabel(m_listView, Qt::Key_Back, ":icon/mute",
tr("Mute"));
Later on, when we press the mute button, the label is changed to "Reject".
How do we know we press mute or reject then ? We check if the m_actionMute
is visible.
I think the easier way to solve this without redoing everything is to
automatically trigger the mute event if the current profile volume is 0.
It is a little hack-ish, but should work.
I will try that...
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1627#comment:14>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1786: GtkButton inner_border theme change
-------------------------------------------------+--------------------------
Reporter: montgoss | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: trivial | Resolution:
Keywords: gtk,theme,inner_border, HasPatch | Blockedby:
Reproducible: | Blocking:
-------------------------------------------------+--------------------------
Comment(by erin_yueh):
please update it to moko-gtk-theme revision 4411! this theme is fine.
i would notify distro team to update moko-gtk-theme version. In our daily
images, the version of moko-gtk-theme and moko-gtk-enginer are different,
still using the old one. Your patch file is based on the old one, not new
one. Update it to the latest one, then it can solve your problem.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1786#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1786: GtkButton inner_border theme change
-------------------------------------------------+--------------------------
Reporter: montgoss | Owner: openmoko-devel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: trivial | Resolution: fixed
Keywords: gtk,theme,inner_border, HasPatch | Blockedby:
Reproducible: | Blocking:
-------------------------------------------------+--------------------------
Changes (by erin_yueh):
* status: new => closed
* resolution: => fixed
Comment:
this new version is still in testing repository, you may get opk file from
here:
http://downloads.openmoko.org/repository/testing/armv4t/moko-gtk-
theme_0.1.0+svnr4411-r0_armv4t.opk
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1786#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1627: [Dialer] The bottom bar menu show "Mute" when incoming a call even
setting
slient or vibrate only
---------------------------+------------------------------------------------
Reporter: regina_kim | Owner: zecke
Type: defect | Status: in_testing
Priority: normal | Milestone: Om2008.9
Component: Qtopia | Version:
Severity: major | Resolution:
Keywords: must have | Blockedby:
Reproducible: | Blocking:
---------------------------+------------------------------------------------
Changes (by charlie):
* status: reopened => in_testing
Comment:
Ok I committed the patch :
http://git.openmoko.org/?p=qtopia.git;a=commit;h=3b3a104f0373e975e0e5bbe4e87ba1ec1d2984b5
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1627#comment:15>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1983: eth0 doesn't exist / Oops during bootup
----------------------------+-----------------------------------------------
Reporter: Weiss | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: wifi kernel | Blockedby:
Reproducible: always | Blocking:
----------------------------+-----------------------------------------------
Comment(by Weiss):
Thanks for the reply again. I've obtained a full 'dmesg' trace (dmesg-
beforejiggling.log) which shows the timeouts from the start with nothing
else which looks relevant to me. I opened the case and checked the WLAN
module, but it seems nicely seated and is very firmly stuck in place. I
tried to wiggle it around a little but it really wasn't moving more than a
fraction of a millimetre.
After poking around, the timeouts in dmesg seemed to have gone (dmesg-
afterjiggling.log), but there was still no wifi (same 'no such device'
errors). On a subsequent bootup, the errors had returned (dmesg-
afterjiggling-withtimeouts.log). I'm afraid I couldn't swear to the
timeout messages not having been intermittent before the poking around - I
wasn't watching too closely until I began to realise that the messages
during bootup could be related to the wifi problems.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1983#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1992: Suspend/Resume plays up when initiated manually
--------------------------+-------------------------------------------------
Reporter: thepizzaking | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Keywords:
Blockedby: | Reproducible: always
Blocking: |
--------------------------+-------------------------------------------------
When I set my phone to suspend automatically after 30 seconds and then
initiate suspend manually (by pressing the power button). I then wait
more than 30 seconds and press the power button again to resume, it wakes
up and then goes straight back to sleep, probably thinking that nothing's
happened for 30 seconds so it should sleep. Pressing the power button
again makes it wake up and stay on, even if you don't press it within
another 30 seconds. Also, letting it automatically suspend after 30
seconds doesn't cause this issue on resume.
A logread after resuming is attached. Along with opkg list_installed.
This is from a rootfs from 29th August 2008 and updated until today (11th
September) on stable.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1992>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1992: Suspend/Resume plays up when initiated manually
--------------------------+-------------------------------------------------
Reporter: thepizzaking | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Keywords:
Blockedby: | Reproducible: always
Blocking: |
--------------------------+-------------------------------------------------
When I set my phone to suspend automatically after 30 seconds and then
initiate suspend manually (by pressing the power button). I then wait
more than 30 seconds and press the power button again to resume, it wakes
up and then goes straight back to sleep, probably thinking that nothing's
happened for 30 seconds so it should sleep. Pressing the power button
again makes it wake up and stay on, even if you don't press it within
another 30 seconds. Also, letting it automatically suspend after 30
seconds doesn't cause this issue on resume.
A logread after resuming is attached. Along with opkg list_installed.
This is from a rootfs from 29th August 2008 and updated until today (11th
September) on stable.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1992>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1867: Dhclient is not working
-------------------------------------+--------------------------------------
Reporter: Zoup | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: Om2008.8
Severity: normal | Resolution:
Keywords: dhclient dhcp-client | Blockedby:
Reproducible: | Blocking:
-------------------------------------+--------------------------------------
Comment(by maxious):
A possible workaround is to use udhcpc which is part of busybox.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1867#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
