[MeeGo-dev] bluetooth service framwork
Hi all Meego current bluetooth app which I found was one simple demo based on bluez4 and do not find any bluetooth service framework but i found the qt4.4 extended have a bluetooth service framework and i know nokia now has abandoned qt4.4 extended and devleop new qt-mobility for moblie so i want to know qt-mobility have plan to devleop bluetooth service framework which based on blueZ4.x thanks ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Virtual Keyboard
Hi All, I dont see an 'Enter key' in Virtual Keyboard in meego 1.1 image. I tried SMS application and wifi application but both keypads are not having 'Enter' key. Is there a need to install some other keyboard layout. Regards, PP ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Meego Bugs Access Denied
On Nov 1, 2010, at 20:03, Ryan Ware wrote: On Mon, Nov 1, 2010 at 10:51 AM, Jeremiah Foster jeremiah.fos...@pelagicore.com wrote: ...snip... My understanding with most Open Source projects is that bugs would never be hidden - the current policy, even if it applies to just one hardware vendor, seems to be in direct contradiction to the Linux Foundation claims to openness. I'd like to point out that the Linux Foundation bylaws state; The purposes of this corporation include promoting, protecting, and standardizing Linux and open source software. Then your understanding is incorrect. Is it? Debian is one of the oldest Linux distros, the largest in terms of packages, and the most successful in terms of deployment if you count derivatives such as Ubuntu, Mint, etc. Here's their bug policy: http://www.debian.org/social_contract from which I quote; We will keep our entire bug report database open for public view at all times. Fedora is also a large, highly successful Linux Distro, here is their policy: http://fedoraproject.org/wiki/Security/TrackingBugs I'll highlight a quote: Parent bug is publicly viewable. The GNU project which comprises a significant portion of any Linux distribution, including MeeGo, also has an open bug policy. Gentoo's policy has an exception that they have a security embargo: http://www.gentoo.org/security/en/vulnerability-policy.xml Gentoo's policy is reasonable because they are aiming to protect their users from known zero day exploits which may directly affect users. It is interesting to note that other Open Source projects have also considered this policy, but rejected it as offering no real security advantage. I don't think my understanding is incorrect; Open Source projects have open bugtrackers. As I've previously explained the vast majority (if not all) highly visible open source projects keep security issues closed until they are resolved. I don't think anyone has a problem with a MeeGo Bugzilla security embargo as long as that embargo is clearly explained, and reaches a consensus in the community. My understanding was that the policy that was in place in MeeGo's bug tracker met neither of those conditions. Jeremiah That said, there is no reason I see that this particular bug should have been anything but open. Ryan ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Meego Bugs Access Denied
2010/11/2 Jeremiah Foster jeremiah.fos...@pelagicore.com: I don't think anyone has a problem with a MeeGo Bugzilla security embargo as long as that embargo is clearly explained, and reaches a consensus in the community. My understanding was that the policy that was in place in MeeGo's bug tracker met neither of those conditions. Minor detail, consensus implies democracy (at least in my interpretation), while there's people responsible and a hierarchy in MeeGo - so there's someone making the last call on these issues.. Doesn't mean the discussion shouldn't happen publically, but someone has the last word and makes the final decision. The additional problem to consider is let's say, if someone posts copyrighted material to a bugtracker or any other community service. Technically a take-down notice can be sent as we're now in the project hosting copyrighted material we don't have a license to publish. Naturally we'd have to remove that material. What I personally think should be done is simply by having a public written policy how to deal with matters like: * Security sensitive bug reports * Developers/testers/whatever contributing copyrighted information that he has no right to, either as patches, bug report information, etc. We obviously can't let the project be subject to legal action so we'll need to take our precautions when matters rise.. It doesn't change the fact that a situation like this is a PITA and since we're a young project, procedures aren't written and we're learning to deal with things. These discussions hopefully lead to a better situation. BR Carsten Munk ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] DVB support on MeeGo
On Mon, 2010-11-01 at 17:25 +, Rudolf Streif wrote: What's missing is decoding of the Service Information if required Well, GStreamer does provide a mean to get access to decoded version of some of the DVB-SI tables (PAT, PMT, NIT, SDT, EIT) that's what gnome-dvb-daemon uses for instance. and eventually the Teletext. Although DVB defines Teletext encoding as stream it is not that commonly used. Many operators are still using the VBI-encoding from the analog days and in that case the Teletext is found in the video stream. You do have a vbidec element in -bad, no idea how well it'd work though. http://cgit.freedesktop.org/gstreamer/gst-plugins-bad/tree/gst/vbidec and a teletex subtitles element, with the same comment. http://github.com/sebp/gst-teletext/tree -- Damien ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] meego account in IVI image
On Oct 31, 2010, at 19:29, Mark S. Townsley wrote: Hi I just brought up the IVI image but it seems to be different from the netbook one in that I was not given the option to create user accounts. It comes with a meego user login. Does anyone know what is the password for this meego account? As previously mentioned, the password is meego. Note that you can change this if you create your image from a kickstart file. In the kickstart file there is a field where you can specify a password. Regards, Jeremiah ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] (no subject)
Hello, Fixed a null pointer access in libmeegotouch. Please review. BR, Jukka Selesniemi From: Jukka Selesniemi ext-jukka.selesni...@nokia.com Subject: [PATCH] Fixed: BMC#9315 - Contact application crashes when tapping and holding a contact In-Reply-To: ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] [PATCH] Fixed: BMC#9315 - Contact application crashes when tapping and holding a contact
Fixed a null pointer access in libmeegotouch when creating a MOriginContainer
object in MStyleSheetPrivate::combine() method.
Signed-off-by: Jukka Selesniemi ext-jukka.selesni...@nokia.com
---
src/corelib/style/mstylesheet.cpp | 11 ++-
1 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/src/corelib/style/mstylesheet.cpp
b/src/corelib/style/mstylesheet.cpp
index b911809..0e1c0d6 100644
--- a/src/corelib/style/mstylesheet.cpp
+++ b/src/corelib/style/mstylesheet.cpp
@@ -377,12 +377,13 @@ bool MStyleSheetPrivate::combine(MStyle *style, const
CacheEntry entry, const S
if (!isHigherPriority(old, info.selector, info.classPriority,
info.parentPriority)) {
continue;
}
-}
-// override
-MOriginContainer *tempMOriginCont = new
MOriginContainer(attribute, info.selector, info.classPriority,
info.parentPriority, info.filename, old-stylesheet);
-data[attribute-name] = tempMOriginCont;
-tempMOriginContainers.append(tempMOriginCont);
+// override
+MOriginContainer *tempMOriginCont = new
MOriginContainer(attribute, info.selector, info.classPriority,
+info.parentPriority, info.filename, old-stylesheet);
+data[attribute-name] = tempMOriginCont;
+tempMOriginContainers.append(tempMOriginCont);
+}
}
}
--
1.7.0.4
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Meego Bugs Access Denied
On Nov 2, 2010, at 11:48, Jussi Kukkonen wrote: On 11/02/2010 11:43 AM, Jeremiah Foster wrote: On Nov 1, 2010, at 20:03, Ryan Ware wrote: On Mon, Nov 1, 2010 at 10:51 AM, Jeremiah Foster jeremiah.fos...@pelagicore.com wrote: My understanding with most Open Source projects is that bugs would never be hidden - the current policy, even if it applies to just one hardware vendor, seems to be in direct contradiction to the Linux Foundation claims to openness. I'd like to point out that the Linux Foundation bylaws state; The purposes of this corporation include promoting, protecting, and standardizing Linux and open source software. Then your understanding is incorrect. Is it? Debian is one of the oldest Linux distros, the largest in terms of packages, and the most successful in terms of deployment if you count derivatives such as Ubuntu, Mint, etc. Here's their bug policy: http://www.debian.org/social_contract from which I quote; We will keep our entire bug report database open for public view at all times. Fedora is also a large, highly successful Linux Distro, here is their policy: http://fedoraproject.org/wiki/Security/TrackingBugs I'll highlight a quote: Parent bug is publicly viewable. The GNU project which comprises a significant portion of any Linux distribution, including MeeGo, also has an open bug policy. Gentoo's policy has an exception that they have a security embargo: http://www.gentoo.org/security/en/vulnerability-policy.xml Gentoo's policy is reasonable because they are aiming to protect their users from known zero day exploits which may directly affect users. It is interesting to note that other Open Source projects have also considered this policy, but rejected it as offering no real security advantage. I don't think my understanding is incorrect; Open Source projects have open bugtrackers. It is incorrect, at least with regard to distros. Your statement has no basis in fact. There is not a single closed bug in Debian's BTS. Please point to a closed bug in Debian to back up your statement. There are various ways to deal with this and a very common approach is to keep selected bugs closed (this is also a requirement for access to various vulnerability information sources). If you are referring to the Vendor-sec mailing list: http://oss-security.openwall.org/wiki/mailing-lists/vendor-sec then yes that is one of the various ways to deal with security bugs. But this list is not closed; The mailing list is unmoderated, but requests for membership are manually vetted to ensure that only the target audience may join. This is done to avoid leaking the potentially sensitive discussions, as vendor-sec members often have access to information about vulnerabilities before they become public As an example, these distros embargo security information in some form: * Debian There is a security team inside Debian and the Debian Developers reference document refers to the handling of security critical bugs; http://www.debian.org/doc/developers-reference/pkgs.html#bug-security To quote from that; http://www.debian.org/doc/developers-reference/pkgs.html#bug-security If this is what you are referring to, please note this is NOT the BTS, this is the separate Security Tracker, and even here that secrecy is limited. * Gentoo I already identified Gentoo as imposing an embargo. * Fedora * Ubuntu * Mint That's five out of the five distros you mentioned. At least four last ones use a bug tracking system in the same way meego does. If a bug is open in Debian, it is most likely open in Ubuntu since Ubuntu is quite close to Debian, and Mint is based on Ubuntu (moving to Debian) so that point is moot too. Fedora's policy needs more scrutiny, I'm not convinced it is as you say it is, I think it is closer to Debian's policy. Whether MeeGo bugzilla is the right place for other limited access bugs may be debatable. Arguing that vulnerability information embargo is an uncommon policy among distros is just silly. That is not the argument. The argument was whether or not to close bugs in the bug tracking system. I argue this is the wrong thing to do. I also concede that some form of security embargo is warranted. These two positions are not mutually exclusive. Jeremiah ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Virtual Keyboard
2010/11/2 praveen pandey praveen.pan...@gmail.com: Hi All, I dont see an 'Enter key' in Virtual Keyboard in meego 1.1 image. I tried SMS application and wifi application but both keypads are not having 'Enter' key. Is there a need to install some other keyboard layout. Hi, In 1.1 the Enter key is under Space, so you need to press Shift-Space to get Enter. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Virtual Keyboard
Hi, Without actually looking at the UI, but isn't this a bit awkward ? e.g. Enter is common enough to be more apparent that that? Hopefully it'll change for 1.2 ? -Sivan On Tue, Nov 2, 2010 at 7:01 PM, Mohammad Anwari md...@di.blankon.in wrote: 2010/11/2 praveen pandey praveen.pan...@gmail.com: Hi All, I dont see an 'Enter key' in Virtual Keyboard in meego 1.1 image. I tried SMS application and wifi application but both keypads are not having 'Enter' key. Is there a need to install some other keyboard layout. Hi, In 1.1 the Enter key is under Space, so you need to press Shift-Space to get Enter. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Virtual Keyboard
2010/11/2 Sivan Greenberg si...@omniqueue.com: Hi, Without actually looking at the UI, but isn't this a bit awkward ? e.g. Enter is common enough to be more apparent that that? Hopefully it'll change for 1.2 ? Yes, it will change, you consider that as a journey of the UI of MeeGo virtual keyboard :-) ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Virtual Keyboard
On Tue, Nov 2, 2010 at 8:41 PM, Mohammad Anwari md...@di.blankon.in wrote: 2010/11/2 Sivan Greenberg si...@omniqueue.com: Hi, Without actually looking at the UI, but isn't this a bit awkward ? e.g. Enter is common enough to be more apparent that that? Hopefully it'll change for 1.2 ? Yes, it will change, you consider that as a journey of the UI of MeeGo virtual keyboard :-) Great, as per my latest involvement with Maemo and MeeGo, it is important we do not repeat previous UI mistakes or leave stuff like that unchanged, were there plans to fix that without a user noticing it and commenting on it here? :) Thanks! -Sivan ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
