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 #1650: Mokomakefile: gtk+/gtk+-fastscaling
conflicts (Openmoko Public Trac)
2. Re: Openmoko Bug #1650: Mokomakefile: gtk+/gtk+-fastscaling
conflicts (Openmoko Public Trac)
3. Re: Openmoko Bug #1738: [Alert message in home screen]
Crashed Alert message with vibration (Openmoko Public Trac)
4. Re: Openmoko Bug #1422: Device doesn?t wake up from blank
time when incoming a call and SMS (Openmoko Public Trac)
5. Re: Openmoko Bug #1700: [Qtopia] sometimes Device does not
Ringing (Openmoko Public Trac)
6. Re: Openmoko Bug #1742: [illume] even the WiFi is off, the
icon is still there in illume bar (Openmoko Public Trac)
7. Re: Openmoko Bug #1730: SELinux Kernel Support
(Openmoko Public Trac)
8. Openmoko Bug #1746: qtmail closes connection when sending
SMTP mail with TLS (Openmoko Public Trac)
--- Begin Message ---
#1650: Mokomakefile: gtk+/gtk+-fastscaling conflicts
--------------------+-------------------------------------------------------
Reporter: gcasse | Owner: julian_chu
Type: defect | Status: closed
Priority: high | Milestone: OM-2007.2
Component: Distro | Version: GTA02v6
Severity: major | Resolution: fixed
Keywords: | Blocking:
Blockedby: |
--------------------+-------------------------------------------------------
Changes (by vortex):
* status: new => closed
* resolution: => fixed
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1650#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1650: Mokomakefile: gtk+/gtk+-fastscaling conflicts
--------------------+-------------------------------------------------------
Reporter: gcasse | Owner: julian_chu
Type: defect | Status: closed
Priority: high | Milestone: OM-2007.2
Component: Distro | Version: GTA02v6
Severity: major | Resolution: fixed
Keywords: | Blocking:
Blockedby: |
--------------------+-------------------------------------------------------
Comment(by vortex):
As of now (3/8/08) a fresk
opkg update
seems to fix this issue.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1650#comment:8>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1738: [Alert message in home screen] Crashed Alert message with vibration
------------------------+---------------------------------------------------
Reporter: regina_kim | Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: normal | Milestone: ASU
Component: Qtopia | Version: GTA02v5
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Comment(by zecke):
If that happens, please do the following immediately:
sudo ifconfig usb0 192.168.0.200 up
ssh [EMAIL PROTECTED]
logread
attach the output of this command to the bugreport.
also verify that making outgoing calls, or accepting incoming ones is not
working after pressing the ok button
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1738#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1422: Device doesn’t wake up from blank time when incoming a call and SMS
-------------------------------------+--------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED]
Type: defect | Status: assigned
Priority: high | Milestone: ASU
Component: Qtopia | Version: GTA02v5
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
-------------------------------------+--------------------------------------
Comment(by zecke):
why was that reopened? Did the device wakeup at all? did the device wake
up but didn't show any notification?
If that happens:
sudo ifconfig usb0 192.168.0.200 up
ssh [EMAIL PROTECTED]
logread
and please attach the output to this bug.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1422#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1700: [Qtopia] sometimes Device does not Ringing
------------------------+---------------------------------------------------
Reporter: regina_kim | Owner: [EMAIL PROTECTED]
Type: defect | Status: in_testing
Priority: high | Milestone: ASU
Component: Qtopia | Version:
Severity: major | Resolution:
Keywords: | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Changes (by zecke):
* status: new => in_testing
Comment:
I toyed with the "mediaserver" and the GStreamer plugin fixing some leaks.
This might or might not have had an impact. Please try it again.
It would be interesting to find out:
- If ring only works on a fresh boot and then stops working
- Or is never working even on a fresh boot
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1700#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1742: [illume] even the WiFi is off, the icon is still there in illume bar
-----------------------------+----------------------------------------------
Reporter: wendy_hung | Owner: openmoko-kernel
Type: defect | Status: assigned
Priority: high | Milestone: ASU
Component: System Software | Version:
Severity: critical | Resolution:
Keywords: | Blocking:
Blockedby: |
-----------------------------+----------------------------------------------
Changes (by raster):
* owner: raster => openmoko-kernel
* status: new => assigned
* component: E - Illume => System Software
Comment:
this is a driver/system level issue. even with eth0 down, an invalid essid
and no key (though it was connected before TO an ap with a different essid
and with a wep key), the link quality is reported as:
[EMAIL PROTECTED]:/etc/network# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:688 (688.0 B) TX bytes:688 (688.0 B)
usb0 Link encap:Ethernet HWaddr 3A:EE:24:E7:8A:0F
inet addr:192.168.0.202 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1040 errors:0 dropped:0 overruns:0 frame:0
TX packets:623 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:77061 (75.2 KiB) TX bytes:74691 (72.9 KiB)
[EMAIL PROTECTED]:/etc/network# iwconfig
lo no wireless extensions.
usb0 no wireless extensions.
eth0 AR6000 802.11g ESSID:""
Mode:Ad-Hoc Bit Rate=48 Mb/s Tx-Power=16 dBm
Sensitivity=0/3
Retry:on
Encryption key:off
Power Management:on
Link Quality:185/94 Signal level:-166 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:1
note the 185/94... there is no adhoc network here... and all networks are
encrypted.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1742#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1730: SELinux Kernel Support
-----------------------------+----------------------------------------------
Reporter: willis | Owner: openmoko-kernel
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Resolution:
Keywords: selinux, kernel | Blocking:
Blockedby: |
-----------------------------+----------------------------------------------
Comment(by willis):
Adding SELinux support to the kernel doesn't force anyone to use SELinux,
it just gives them an SELinux enabled kernel. SELinux can be kept off by
default in the rootfs. When installed, the SELinux package would then
install the policy and turn SELinux on. The trade-off with enabling it by
default is that the kernel will be larger and boot slower. But if a user
chooses to install SELinux then they will not be required to flash a new
kernel image (which they would be required to do if not supported by
default). I guess the discussion should be: would the number of users that
would potentially use SELinux on their device support the decision of
increasing kernel size/boot time? This seems like it would be dependent on
how much kernel size/boot time increases which I'm not qualified to
answer. Although if someone would be willing to do some testing on the
uImage to get empirical data =) ...
> I wonder what is the story about what we can expect from selinux support
given we did not take > care about even user / group functional separation
properly yet in our rootfs.
True, user/group defaults would go a ways towards increasing security on
the device. But I think in the meantime (or in spite of this), SELinux on
a single user device makes a lot of sense. In particular, the benefit of
SELinux is that it can prevent privilege escalation between two root
processes by sandboxing each.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1730#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1746: qtmail closes connection when sending SMTP mail with TLS
---------------------+------------------------------------------------------
Reporter: ssinger | Owner: zecke
Type: defect | Status: new
Priority: normal | Milestone: ASU
Component: Qtopia | Version: current svn head
Severity: normal | Keywords: qtmail,ssl
Blocking: | Blockedby:
---------------------+------------------------------------------------------
When I try to send email through qtmail it gives me an "unknown error".
I configure outgoing email to use SMTP with TLS
server: smtphm.sympatico.ca (This actually points to a hotmail run server)
port:25
Encryption: TLS
Authentication: Plain or Login, same results
qtmail sends the EHELO, then the STARTTLS
The email server replies with server ready and then qtmail closes the
connection and prints "unknown error"
If I start qtmail from a terminal I see
Cannot find SSL certificates "(my buildpath/mailtransport.cpp:45"
QsslSocket: cannot call unresolved function SSLv3_client_method
Also
SSL_CTX_new
ERR_get_error
are unresolved.
This was with an Aug 2 2008 asu.dev build
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1746>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
