[MeeGo-dev] [Qt] When the patch for QML_ID will be available?
Hello All, The merge request #2592https://qt.gitorious.org/qt/qt/merge_requests/2592 https://qt.gitorious.org/qt/qt/merge_requests/2592 has been committed for a while on Qt, and isn't merged yet. And we also voted for it on Nokia's forum. This patch is very important to our team for automatically testing QML GUI application. I wonder if anyone knows when it will be accepted? Or if it has been rejected, please inform me. Thanks Best Regards Shao-Feng ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Fwd: Re: MeeGo Community device program update
Hi, Am Dienstag 05 April 2011 schrieb Randall Arnold: - I was just down in Austin for the Texas Linux fest this last Saturday [4] and got to talk with Jayabharath Goluguri from TI about Pandaboards there. �TI is eager to get some into the hands of MeeGo members with big ideas! �So pending the introduction of our online solution, email myself, Any news on this? The beagleboard setup now seems to be pretty solid and panda should imho be next to get stable. TI should really get the pandas out as this will help getting a second stable diy plattform. Also please try to present those community projects a little better in sfa than last time in dublin. There were several commercial setups based on community efforts like meego on beagle, but there wasn't a single sign that these were actually originating from community efforts nor were there any live community presentations at the summit itself (there were some at the early bird events, but these only reach those that already know about them). I had all my beagle gear with me dublin, but the summit itself didn't have a space to present them. This should really change this time! Till -- Dr. Till Harbaum t...@harbaum.org ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] MIC2 users survey
Hi, all the mic2 users Thank your support and help for mic2, we're planning to refactor mic2 in order to improve user experience, enhance error handling, make developers easier to get involved, this is an very important chance to hear voices from users and do users-oriented development, so we're very eager every mic2 user can speak out all the issues you met during installation and usage and tell us your expectations for mic2, you can do this by directly replying or filing a bug on http://bugs.meego.com/enter_bug.cgi?product=Development%20Toolscomponent=MIC%20(Image%20Creator) , we'll take your relpies or bugs seriously and try our best to implement them one by one in the future releases. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [Qt] When the patch for QML_ID will be available?
On Wed, 2011-04-27 at 14:47 +0800, Tang, Shaofeng wrote: Hello All, The merge request #2592 https://qt.gitorious.org/qt/qt/merge_requests/2592 has been committed for a while on Qt, and isn’t merged yet. And we also voted for it on Nokia’s forum. This patch is very important to our team for automatically testing QML GUI application. File a bug to qt in qt's bugzilla? That's a matter of upstream. The problem won't stop you because you can file a bug in bugs.meego.com and add you solution there. Add add this patch to meego OBS devel:qml. I wonder if anyone knows when it will be accepted? Or if it has been rejected, please inform me. Thanks Best Regards Shao-Feng -- *^_^* Many thanks Best Regards SSD-OTC Meego Middleware TV Team Zhao Juan ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] meego-app-video to play live stream
live streams work fine with gstreamer. My question is not codec related (I have installed the proper codecs). My question is can I launch a play back in the Meego tablet video player from command line and how. I try this: Meego-qml-launcher --opengl --cmd playVideo --cdata URL file or stream --fullscreen --app meego-app-video The meego-app-video launches but I do not get the playback to start. It always brings me to the list of local available videos local on the system. Is there anything I am not doing right ? Regards, Philippe -Original Message- From: Ji, Jessica Sent: mercredi 27 avril 2011 02:51 To: Brendan Le Foll; Michelon, Philippe Cc: meego-dev@meego.com Subject: RE: [MeeGo-dev] meego-app-video to play live stream Yes, live stream work well now. maybe missing codec plug-in. Best Regards Jessica. Intel Asia-Pacific RD Ltd.[INET] 8821-6598 -Original Message- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Brendan Le Foll Sent: 2011年4月27日 4:03 To: Michelon, Philippe Cc: meego-dev@meego.com Subject: Re: [MeeGo-dev] meego-app-video to play live stream On 26 April 2011 21:04, Niels Mayer nielsma...@gmail.com wrote: On Tue, Apr 26, 2011 at 10:11 AM, Michelon, Philippe philippe.miche...@intel.com wrote: Can I launch the qml application meego-app-video to playback a live stream (rtsp) and how ? Hi Philippe, Should be no problem if it's based on playbin2, just give it the full URI. If you have the correct plugins it will work correctly. At any rate, the dbus based madeo-uplayer in devel:tv is able to play back rtsp streams from youtube as below just fine. For youtube streams as below you need both an Mpeg4 decoder and AAC decoder GStreamer plugin. I tried it on my MeeGo 1.1 netbook and madeo-uplayer and it worked just fine. A more general programming question is how can one get QtMobility video players to work with live (RTSP/3GP) streams? For example, given a link like rtsp://v5.cache3.c.youtube.com/CjYLENy73wIaLQkNvt4Qjs09qBMYJCAkFEIJbXYtZ29vZ2xlSARSBXdhdGNoYPjLnbXFuOLPTQw=/0/0/0/video.3gp from http://m.youtube.com/ how would one be able to send that link to meego-app-video (or banshee, or whatever player is setup forMeeGo)? Doesn't work Works fine for me. It's just not working for you because you don't have the right codecs. And we all know why we can't ship them ;-) And fedora aren't shipping them either! Can we please stop telling people to install rpms from not just other distros but unofficial repos for other distros? While this might be useful to some I don't believe it has any place on the official MeeGo wiki, this is hardly supported behaviour! -- Brendan Le Foll http://www.madeo.co.uk ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines - Intel Corporation SAS (French simplified joint stock company) Registered headquarters: Les Montalets- 2, rue de Paris, 92196 Meudon Cedex, France Registration Number: 302 456 199 R.C.S. NANTERRE Capital: 4,572,000 Euros This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [Qt] When the patch for QML_ID will be available?
Hi Juan, Thanks to your suggestion. BR, Shao-Feng -Original Message- From: Zhao, Juan J Sent: Wednesday, April 27, 2011 3:31 PM To: Tang, Shaofeng Cc: meego-dev@meego.com; meego...@lists.meego.com Subject: Re: [MeeGo-dev] [Qt] When the patch for QML_ID will be available? On Wed, 2011-04-27 at 14:47 +0800, Tang, Shaofeng wrote: Hello All, The merge request #2592 https://qt.gitorious.org/qt/qt/merge_requests/2592 has been committed for a while on Qt, and isn’t merged yet. And we also voted for it on Nokia’s forum. This patch is very important to our team for automatically testing QML GUI application. File a bug to qt in qt's bugzilla? That's a matter of upstream. The problem won't stop you because you can file a bug in bugs.meego.com and add you solution there. Add add this patch to meego OBS devel:qml. I wonder if anyone knows when it will be accepted? Or if it has been rejected, please inform me. Thanks Best Regards Shao-Feng -- *^_^* Many thanks Best Regards SSD-OTC Meego Middleware TV Team Zhao Juan ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] [PATCH 1/1] Fixed ACL in libsignon-qt-tests.
---
tests/libsignon-qt-tests/ssotestclient.cpp | 24 +---
1 files changed, 13 insertions(+), 11 deletions(-)
diff --git a/tests/libsignon-qt-tests/ssotestclient.cpp
b/tests/libsignon-qt-tests/ssotestclient.cpp
index 99d4499..f1a1cd7 100644
--- a/tests/libsignon-qt-tests/ssotestclient.cpp
+++ b/tests/libsignon-qt-tests/ssotestclient.cpp
@@ -97,6 +97,8 @@ int finishedClients = 0;
#define AEGIS_TOKEN_4 token_4
#define AEGIS_TOKEN_5
AID::com.nokia.maemo.libsignon-qt-tests.libsignon-qt-tests-id
+#define TEST_AEGIS_TOKEN libsignon-qt-tests::libsignon-qt-tests
+
void SsoTestClient::initTestCase()
{
clearDB();
@@ -192,7 +194,7 @@ void SsoTestClient::queryAvailableMetods()
TEST_USERNAME_1,
methods);
info.setSecret(TEST_PASSWORD_1);
-info.setAccessControlList(QStringList() test_token);
+info.setAccessControlList(QStringList() TEST_AEGIS_TOKEN);
if(!storeCredentialsPrivate(info))
QFAIL(Failed to initialize test for querying available methods.);
@@ -304,7 +306,7 @@ void SsoTestClient::remove()
TEST_USERNAME_1,
methods);
info.setSecret(TEST_PASSWORD_1);
-info.setAccessControlList(QStringList() test_token);
+info.setAccessControlList(QStringList() TEST_AEGIS_TOKEN);
if(!storeCredentialsPrivate(info))
QFAIL(Failed to initialize test for removing identity.);
@@ -403,7 +405,7 @@ void SsoTestClient::removeStoreRemove()
TEST_USERNAME_1,
methods);
info.setSecret(TEST_PASSWORD_1);
-info.setAccessControlList(QStringList() test_token);
+info.setAccessControlList(QStringList() TEST_AEGIS_TOKEN);
if(!storeCredentialsPrivate(info))
QFAIL(Failed to initialize test for removing identity.);
@@ -451,7 +453,7 @@ void SsoTestClient::removeStoreRemove()
TEST_USERNAME_10,
methods);
updateInfo.setSecret(TEST_PASSWORD_10);
-updateInfo.setAccessControlList(QStringList() test_token_1);
+updateInfo.setAccessControlList(QStringList() TEST_AEGIS_TOKEN);
m_identityResult.m_responseReceived =
TestIdentityResult::InexistentResp;
identity-storeCredentials(updateInfo);
@@ -539,7 +541,7 @@ void SsoTestClient::multipleRemove()
TEST_USERNAME_1,
methods);
info.setSecret(TEST_PASSWORD_1);
-info.setAccessControlList(QStringList() test_token);
+info.setAccessControlList(QStringList() TEST_AEGIS_TOKEN);
if(!storeCredentialsPrivate(info))
QFAIL(Failed to initialize test for removing identity.);
@@ -628,7 +630,7 @@ void SsoTestClient::queryInfo()
methods);
info.setSecret(TEST_PASSWORD_1);
info.setRealms(QStringList() test_realm);
-info.setAccessControlList(QStringList() test_token);
+info.setAccessControlList(QStringList() TEST_AEGIS_TOKEN);
if(!storeCredentialsPrivate(info))
QFAIL(Failed to initialize test for querying info.);
@@ -693,7 +695,7 @@ void SsoTestClient::addReference()
methods);
info.setSecret(TEST_PASSWORD_1);
info.setRealms(QStringList() test_realm);
-info.setAccessControlList(QStringList() test_token);
+info.setAccessControlList(QStringList() TEST_AEGIS_TOKEN);
if(!storeCredentialsPrivate(info))
QFAIL(Failed to initialize test for querying info.);
@@ -754,7 +756,7 @@ void SsoTestClient::removeReference()
methods);
info.setSecret(TEST_PASSWORD_1);
info.setRealms(QStringList() test_realm);
-info.setAccessControlList(QStringList() test_token);
+info.setAccessControlList(QStringList() TEST_AEGIS_TOKEN);
if(!storeCredentialsPrivate(info))
QFAIL(Failed to initialize test for querying info.);
@@ -818,7 +820,7 @@ void SsoTestClient::verifyUser()
TEST_USERNAME_1,
methods);
info.setSecret(TEST_PASSWORD_1);
-info.setAccessControlList(QStringList() test_token);
+info.setAccessControlList(QStringList() TEST_AEGIS_TOKEN);
if(!storeCredentialsPrivate(info))
QFAIL(Failed to initialize test for verifying user.);
@@ -867,7 +869,7 @@ void SsoTestClient::verifySecret()
TEST_USERNAME_1,
methods);
info.setSecret(TEST_PASSWORD_1);
-info.setAccessControlList(QStringList() test_token);
+info.setAccessControlList(QStringList() TEST_AEGIS_TOKEN);
if(!storeCredentialsPrivate(info))
QFAIL(Failed to initialize test for verifying secret.);
@@ -926,7 +928,7 @@ void SsoTestClient::signOut()
TEST_USERNAME_1,
methods);
info.setSecret(TEST_PASSWORD_1);
-info.setAccessControlList(QStringList() test_token);
+info.setAccessControlList(QStringList()
Re: [MeeGo-dev] [Qt] When the patch for QML_ID will be available?
Hi, Question related to the merger request: How can the id be unique and used for ui test automation??. For example I could have have three list items in a view and will it not fail to differentiate between them thanks, kalyan On Wed, Apr 27, 2011 at 11:34 AM, Tang, Shaofeng shaofeng.t...@intel.comwrote: Actually, I just want to check if the merge request will be accepted or not. And sure, I will add the patch into my bug. -Original Message- From: Zhao, Juan J Sent: Wednesday, April 27, 2011 3:31 PM To: Tang, Shaofeng Cc: meego-dev@meego.com; meego...@lists.meego.com Subject: Re: [MeeGo-dev] [Qt] When the patch for QML_ID will be available? On Wed, 2011-04-27 at 14:47 +0800, Tang, Shaofeng wrote: Hello All, The merge request #2592 https://qt.gitorious.org/qt/qt/merge_requests/2592 has been committed for a while on Qt, and isn’t merged yet. And we also voted for it on Nokia’s forum. This patch is very important to our team for automatically testing QML GUI application. File a bug to qt in qt's bugzilla? That's a matter of upstream. The problem won't stop you because you can file a bug in bugs.meego.com and add you solution there. Add add this patch to meego OBS devel:qml. I wonder if anyone knows when it will be accepted? Or if it has been rejected, please inform me. Thanks Best Regards Shao-Feng -- *^_^* Many thanks Best Regards SSD-OTC Meego Middleware TV Team Zhao Juan ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [Qt] When the patch for QML_ID will be available?
Hi, On 27.4.2011, at 12.11, kalyan reddy wrote: Hi, Question related to the merger request: How can the id be unique and used for ui test automation??. For example I could have have three list items in a view and will it not fail to differentiate between them The id does not need to be unique. It will help to differentiate the Item object from button object. If you need to differentiate between item objects then you need to include also other attributes which combined will make the unique identification possible (order, text, icon etc.). In many cases the id will be unique in the context of the application and will help test automation a lot. Item object is probably one of the few cases where this does not help too much? Petri thanks, kalyan On Wed, Apr 27, 2011 at 11:34 AM, Tang, Shaofeng shaofeng.t...@intel.com wrote: Actually, I just want to check if the merge request will be accepted or not. And sure, I will add the patch into my bug. -Original Message- From: Zhao, Juan J Sent: Wednesday, April 27, 2011 3:31 PM To: Tang, Shaofeng Cc: meego-dev@meego.com; meego...@lists.meego.com Subject: Re: [MeeGo-dev] [Qt] When the patch for QML_ID will be available? On Wed, 2011-04-27 at 14:47 +0800, Tang, Shaofeng wrote: Hello All, The merge request #2592 https://qt.gitorious.org/qt/qt/merge_requests/2592 has been committed for a while on Qt, and isn’t merged yet. And we also voted for it on Nokia’s forum. This patch is very important to our team for automatically testing QML GUI application. File a bug to qt in qt's bugzilla? That's a matter of upstream. The problem won't stop you because you can file a bug in bugs.meego.com and add you solution there. Add add this patch to meego OBS devel:qml. I wonder if anyone knows when it will be accepted? Or if it has been rejected, please inform me. Thanks Best Regards Shao-Feng -- *^_^* Many thanks Best Regards SSD-OTC Meego Middleware TV Team Zhao Juan ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [Qt] When the patch for QML_ID will be available?
Hi, Basically this would work only in case where ui being tested has elements which are unique.(i.e no more than one Button, no more than one text element etc) which could be extreme cases??. br, kalyan On Wed, Apr 27, 2011 at 12:22 PM, Petri Kiiskinen petri.kiiski...@jidokatech.com wrote: Hi, On 27.4.2011, at 12.11, kalyan reddy wrote: Hi, Question related to the merger request: How can the id be unique and used for ui test automation??. For example I could have have three list items in a view and will it not fail to differentiate between them The id does not need to be unique. It will help to differentiate the Item object from button object. If you need to differentiate between item objects then you need to include also other attributes which combined will make the unique identification possible (order, text, icon etc.). In many cases the id will be unique in the context of the application and will help test automation a lot. Item object is probably one of the few cases where this does not help too much? Petri thanks, kalyan On Wed, Apr 27, 2011 at 11:34 AM, Tang, Shaofeng shaofeng.t...@intel.comwrote: Actually, I just want to check if the merge request will be accepted or not. And sure, I will add the patch into my bug. -Original Message- From: Zhao, Juan J Sent: Wednesday, April 27, 2011 3:31 PM To: Tang, Shaofeng Cc: meego-dev@meego.com; meego...@lists.meego.com Subject: Re: [MeeGo-dev] [Qt] When the patch for QML_ID will be available? On Wed, 2011-04-27 at 14:47 +0800, Tang, Shaofeng wrote: Hello All, The merge request #2592 https://qt.gitorious.org/qt/qt/merge_requests/2592 has been committed for a while on Qt, and isn’t merged yet. And we also voted for it on Nokia’s forum. This patch is very important to our team for automatically testing QML GUI application. File a bug to qt in qt's bugzilla? That's a matter of upstream. The problem won't stop you because you can file a bug in bugs.meego.com and add you solution there. Add add this patch to meego OBS devel:qml. I wonder if anyone knows when it will be accepted? Or if it has been rejected, please inform me. Thanks Best Regards Shao-Feng -- *^_^* Many thanks Best Regards SSD-OTC Meego Middleware TV Team Zhao Juan ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Fwd: [MeeGo-ivi] Kernel for 1.2
Joel is correct, Which leads me to my confusion... kernel 2.6.37.6 != kernel 2.6.37.6 Joel pointed out where the automotive version of the kernel was being synced to, and that location has a version of the kernel from 3 months ago. That version isn't 2.6.37.6 (kernel.org has that being released on 2011-03-27). Nasa - Joel Clark joel.cl...@intel.com wrote: On 4/26/2011 Arjan wrote: there isn't really *the* ivi kernel. I believe Nasa is referring to the kernel-adaptation-intel-automotive which is derived from the 2.6.37.6 MeeGo reference kernel. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [Qt] When the patch for QML_ID will be available?
Hi, On 27.4.2011, at 12.44, kalyan reddy wrote: Hi, Basically this would work only in case where ui being tested has elements which are unique.(i.e no more than one Button, no more than one text element etc) which could be extreme cases??. No. You will have different ids for each button, each text element and so on. This is required by qml syntax as is. This way you will be able to identify the exact button, text, etc. using the id which is the same as in qml. Think if you have a form where you have text input for first name, last name and address. These can all be TextInput elements but they all need to have different id. The id usually describes the semantics of the element thus natural ids could be for example fName, lName, address. Also you might have two buttons with ids like Ok and Cancel. List item is the only case I think there is not so much use for this id but I think in all other cases it will be _very_ useful. Also with list items this could be useful if you have two different list items (for example for odd and even items) - then you would be able to use the id to differentiate between those kinds of list items. Petri br, kalyan On Wed, Apr 27, 2011 at 12:22 PM, Petri Kiiskinen petri.kiiski...@jidokatech.com wrote: Hi, On 27.4.2011, at 12.11, kalyan reddy wrote: Hi, Question related to the merger request: How can the id be unique and used for ui test automation??. For example I could have have three list items in a view and will it not fail to differentiate between them The id does not need to be unique. It will help to differentiate the Item object from button object. If you need to differentiate between item objects then you need to include also other attributes which combined will make the unique identification possible (order, text, icon etc.). In many cases the id will be unique in the context of the application and will help test automation a lot. Item object is probably one of the few cases where this does not help too much? Petri thanks, kalyan On Wed, Apr 27, 2011 at 11:34 AM, Tang, Shaofeng shaofeng.t...@intel.com wrote: Actually, I just want to check if the merge request will be accepted or not. And sure, I will add the patch into my bug. -Original Message- From: Zhao, Juan J Sent: Wednesday, April 27, 2011 3:31 PM To: Tang, Shaofeng Cc: meego-dev@meego.com; meego...@lists.meego.com Subject: Re: [MeeGo-dev] [Qt] When the patch for QML_ID will be available? On Wed, 2011-04-27 at 14:47 +0800, Tang, Shaofeng wrote: Hello All, The merge request #2592 https://qt.gitorious.org/qt/qt/merge_requests/2592 has been committed for a while on Qt, and isn’t merged yet. And we also voted for it on Nokia’s forum. This patch is very important to our team for automatically testing QML GUI application. File a bug to qt in qt's bugzilla? That's a matter of upstream. The problem won't stop you because you can file a bug in bugs.meego.com and add you solution there. Add add this patch to meego OBS devel:qml. I wonder if anyone knows when it will be accepted? Or if it has been rejected, please inform me. Thanks Best Regards Shao-Feng -- *^_^* Many thanks Best Regards SSD-OTC Meego Middleware TV Team Zhao Juan ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [SSO]: libsignon-qt Tests Fix
Hi, looks fine, Ship it Regards, Tomi From: meego-dev-boun...@meego.com [meego-dev-boun...@meego.com] on behalf of Popirtac Aurel (EXT-Teleca/Helsinki) Sent: 27 April 2011 12:06 To: meego-dev@meego.com Subject: [MeeGo-dev] [SSO]: libsignon-qt Tests Fix Hi, Fixed the ACLs in the libsignon-qt-tests. Br, Aurel ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Fwd: [MeeGo-ivi] Kernel for 1.2
On 4/27/2011 2:34 AM, Jeremiah Foster wrote: On Wed, Apr 27, 2011 at 3:27 AM, Arjan van de Venar...@linux.intel.com wrote: On 4/26/2011 5:54 PM, Nasa wrote: [...] there isn't really *the* ivi kernel. Each platform (as per TSG decision) has the freedom to pick its own kernel version, as long as it is compatible with the reference kernel and as long as security maintenance etc is done on it. So each vertical can have their own little mini distro as long as it is supported? The only requirement seems to be to pull from MeeGo Core. Is this an accurate description or am I missing something? ??? this is specifically about the kernel, and the it must be compatible sounds easier than it is; being compatible with a 2.6.37 kernel if you're older than 2.6.37 is actually a huge task... ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] FYI -- using fuse-sshfs to mount remote filesystems with only SSH (sftp)
## install fuse-sshfs-2.2-4.30.i586 $ sudo zypper in fuse-sshfs ## f use module must be loaded else fail $ sudo modprobe fuse ## make a permanent mount point in /media $ sudo mkdir /media/gnulem-npm ## allow non-superuser 'npm' to mount $ sudo chown npm.npm /media/gnulem-npm ##mount the sftp filesystem on mount point $ sshfs gnulem: /media/gnulem-npm npm@gnulem's password: ... Now 'df' reports: gnulem: 453G 408G 23G 95% /media/gnulem-npm And the remote system is mounted as if locally, without needing to setup NFS -- just needs SSHD running. Obviously not as fast or performant given the encrypt/decrypt invoked by SSH, but at least it's as secure as SSH and can be further secured by using public/private keypairs in SSH. Niels http://nielsmayer.com ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Fwd: [MeeGo-ivi] Kernel for 1.2
I've noticed that there is no matching kernel-headers for any of the kernels being used: For example I have installed (from http://download.meego.com/live/devel:/kernel/Trunk/ ) kernel-2.6.37.2-256.2.i586 kernel-devel-2.6.37.2-256.2.i586 kernel-adaptation-pinetrail-2.6.38.2-8.1.i586 kernel-adaptation-pinetrail-devel-2.6.38.2-8.1.i586 But there's no associated kernel-headers and the only one installed doesn't match the .38 kernel that i'm now using. meegolem-71-~ zypper info kernel-headers Loading repository data... Reading installed packages... Information for package kernel-headers: Repository: @System Name: kernel-headers Version: 2.6.37-3.2 Arch: i586 Vendor: meego Installed: Yes Status: up-to-date Installed Size: 2.4 MiB Summary: Headers describing the kernel ABI Description: The kernel-headers package contains the header files that describe the kernel ABI. This package is mostly used by the C library and some low level system software, and is only used indirectly by regular applications. -- Niels http://nielsmayer.com ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Fwd: [MeeGo-ivi] Kernel for 1.2
On 4/27/2011 9:47 AM, Niels Mayer wrote: I've noticed that there is no matching kernel-headers for any of the kernels being used: that's fine. the kernel ABI to glibc does not change, and the kernel-headers should really describe the reference ABI there... what makes you think this is a problem ? ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Fwd: [MeeGo-ivi] Kernel for 1.2
On Wed, 27 Apr 2011, Arjan van de Ven wrote: On 4/27/2011 9:47 AM, Niels Mayer wrote: I've noticed that there is no matching kernel-headers for any of the kernels being used: that's fine. the kernel ABI to glibc does not change, and the kernel-headers should really describe the reference ABI there... what makes you think this is a problem ? So... we can use the 2.6.37 kernel-headers package for building out-of-tree kernel modules for a 2.6.38 adaptation kernel? If no -- then that's the problem. -gabriel ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Fwd: [MeeGo-ivi] Kernel for 1.2
On 4/27/2011 10:07 AM, Gabriel M. Beddingfield wrote: On Wed, 27 Apr 2011, Arjan van de Ven wrote: On 4/27/2011 9:47 AM, Niels Mayer wrote: I've noticed that there is no matching kernel-headers for any of the kernels being used: that's fine. the kernel ABI to glibc does not change, and the kernel-headers should really describe the reference ABI there... what makes you think this is a problem ? So... we can use the 2.6.37 kernel-headers package for building out-of-tree kernel modules for a 2.6.38 adaptation kernel? If no -- then that's the problem. you can never use a kernel-headers package for building kernel modules of any shape or flavor... since these are the headers for glibc, they're not the kernel sources needed for kernel modules. (and never were). ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Fwd: [MeeGo-ivi] Kernel for 1.2
On Wed, 27 Apr 2011, Arjan van de Ven wrote: what makes you think this is a problem ? So... we can use the 2.6.37 kernel-headers package for building out-of-tree kernel modules for a 2.6.38 adaptation kernel? If no -- then that's the problem. you can never use a kernel-headers package for building kernel modules of any shape or flavor... since these are the headers for glibc, they're not the kernel sources needed for kernel modules. (and never were). It appears that I am a Bear of Very Little Brain... kernel-XXX-devel is used for making out-of-tree modules. Thanks to you and Carsten for pointing out my error. Sorry! -gabriel ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] how to port meego to snapdragon
Hi, I'm sorry, but I can't help you with that. I was only forwarding the .ks file. I hope someone else can help you. Cheers, Conny On Wed, 2011-04-27 at 16:49 +0800, Bo Liu wrote: Dear Cornelius and Martin, After all the rootfs was built with attached .ks successfully. Then I copied this rootfs into phone's SD card, which was mounted after kernel booting. Then the whole system (kernel + rootfs) run, but no meego GUI appears. I cat the /var/log/uxlaunch.log and found that Xorg always exited. The log is below. On the serial console, if I run command: $/usr/bin/Xorg :0 -logfile /tmp/Xorg.0.meego.log -dpi 120 -nolisten tcp -noreset -auth /home/meego/.Xauthority vt2 then x cursor appeared. So it seems that X server can run mannually. After Xorg running, I run: $export DISPLAY=:0 $xterm then xterm window appeared. So it seems that client can connect to X. So maybe the failure result from autostarting of desktop? log file is as below: [00.03] [4278] uxlaunch v0.59 started. [00.000236] [4278] user meego, tty #2, session /usr/bin/mcompositor -software [00.002746] [4278] Xauth cookie file: /var/run/uxlaunch/Xauth-meego-Y15ywv [00.003040] [4278] Entering set_tty [00.003171] [4278] Using /dev/tty2 as display device [00.037658] [4278] Entering switch_to_user [00.038419] [4278] Unable to setpgid() [00.038493] [4278] Unable to setsid() [00.225219] [4278] Setting AG_PROVIDERS to /usr/share/accounts/providers [00.225398] [4278] Setting AG_SERVICES to /usr/share/accounts/services [00.225469] [4278] Setting AG_SERVICE_TYPES to /usr/share/accounts/service-types [00.225535] [4278] Setting DISPLAY to :0 [00.225588] [4278] Setting G_BROKEN_FILENAMES to 1 [00.225646] [4278] Setting HISTCONTROL to ignoredups [00.225713] [4278] Setting HISTSIZE to 1000 [00.225771] [4278] Setting HOME to /home/meego [00.225825] [4278] Setting HOSTNAME to localhost.localdomain [00.225882] [4278] Setting LANG to en_US.UTF-8 [00.225942] [4278] Setting LESSOPEN to |/usr/bin/lesspipe.sh %s [00.226000] [4278] Setting LOGNAME to meego [00.226052] [4278] Setting LS_COLORS to [00.226107] [4278] Setting MAIL to /var/spool/mail/meego [00.226160] [4278] Setting M_DECORATED to 0 [00.226288] [4278] Setting PATH to /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/home/meego/bin:/home/meego/bin [00.226382] [4278] Setting QMF_PLUGINS to /usr/lib/qmf/plugins [00.226442] [4278] Setting QT_IM_MODULE to MInputContext [00.226502] [4278] Setting SHELL to /bin/bash [00.226554] [4278] Setting SHLVL to 2 [00.226611] [4278] Setting USER to meego [00.226664] [4278] Setting XAUTHORITY to /home/meego/.Xauthority [00.227304] [4278] entering set_i18n [00.252902] [4278] Started Xorg[4302] [00.253084] [4278] Entering wait_for_X_signal [00.259096] [4302] starting X server with: /usr/bin/Xorg :0 -logfile /tmp/Xorg.0.meego.log -dpi 120 -nolisten tcp -noreset -auth /home/meego/.Xauthority vt2 [10.253350] [4278] done [10.311201] [4278] launching session bus: dbus-daemon --fork --session --print-pid 9 --print-address 11 [10.374446] [4278] --- environment variable dump: [10.374535] [4278] USER=meego [10.374547] [4278] LOGNAME=meego [10.374559] [4278] HOME=/home/meego [10.374570] [4278] SHELL=/bin/bash [10.374581] [4278] MAIL=/var/spool/mail/meego [10.374592] [4278] DISPLAY=:0 [10.374602] [4278] PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/home/meego/bin:/home/meego/bin [10.374614] [4278] XAUTHORITY=/home/meego/.Xauthority [10.374625] [4278] AG_PROVIDERS=/usr/share/accounts/providers [10.374636] [4278] AG_SERVICES=/usr/share/accounts/services [10.374647] [4278] AG_SERVICE_TYPES=/usr/share/accounts/service-types [10.374658] [4278] G_BROKEN_FILENAMES=1 [10.374669] [4278] HISTCONTROL=ignoredups [10.374679] [4278] HISTSIZE=1000 [10.374689] [4278] HOSTNAME=localhost.localdomain [10.374700] [4278] LANG=en_US.UTF-8 [10.374710] [4278] LESSOPEN=|/usr/bin/lesspipe.sh %s [10.374721] [4278] LS_COLORS= [10.374732] [4278] M_DECORATED=0 [10.374742] [4278] QMF_PLUGINS=/usr/lib/qmf/plugins [10.374753] [4278] QT_IM_MODULE=MInputContext [10.374764] [4278] SHLVL=2 [10.374774] [4278] XDG_CACHE_HOME=/home/meego/.cache [10.374785] [4278] XDG_CONFIG_HOME=/home/meego/.config [10.374796] [4278] OOO_FORCE_DESKTOP=gnome [10.374806] [4278] LIBC_FATAL_STDERR_=1 [10.374817] [4278] SSH_AUTH_SOCK=/tmp/ssh-Ngzmjf4321/agent.4321 [10.374827] [4278] SSH_AGENT_PID=4323 [10.374838] [4278] XDG_SESSION_COOKIE=b529482f43151258dbb86a360004-317689444.585938-366484378 [10.374849] [4278] DBUS_SESSION_BUS_PID=4329 [10.374860] [4278] DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-CEJ8huWDVH,guid=078d53d68f21f432fe27bee00261 [10.374871] [4278]
Re: [MeeGo-dev] how to port meego to snapdragon
Hi, in order to make sure that everything is in place to start the handset UX, make sure that either GLES is working (by e.g. running some 3D demos from xterm) or make sure that you run the handset UX with software rendering (which in turn would result in a barely usable slow UX, but at least should give you something). Till Am Mittwoch 27 April 2011 schrieb Cornelius Hald: Hi, I'm sorry, but I can't help you with that. I was only forwarding the .ks file. I hope someone else can help you. Cheers, Conny On Wed, 2011-04-27 at 16:49 +0800, Bo Liu wrote: Dear Cornelius and Martin, After all the rootfs was built with attached .ks successfully. Then I copied this rootfs into phone's SD card, which was mounted after kernel booting. Then the whole system (kernel + rootfs) run, but no meego GUI appears. I cat the /var/log/uxlaunch.log and found that Xorg always exited. The log is below. On the serial console, if I run command: $/usr/bin/Xorg :0 -logfile /tmp/Xorg.0.meego.log -dpi 120 -nolisten tcp -noreset -auth /home/meego/.Xauthority vt2 then x cursor appeared. So it seems that X server can run mannually. After Xorg running, I run: $export DISPLAY=:0 $xterm then xterm window appeared. So it seems that client can connect to X. So maybe the failure result from autostarting of desktop? log file is as below: [00.03] [4278] uxlaunch v0.59 started. [00.000236] [4278] user meego, tty #2, session /usr/bin/mcompositor -software [00.002746] [4278] Xauth cookie file: /var/run/uxlaunch/Xauth-meego-Y15ywv [00.003040] [4278] Entering set_tty [00.003171] [4278] Using /dev/tty2 as display device [00.037658] [4278] Entering switch_to_user [00.038419] [4278] Unable to setpgid() [00.038493] [4278] Unable to setsid() [00.225219] [4278] Setting AG_PROVIDERS to /usr/share/accounts/providers [00.225398] [4278] Setting AG_SERVICES to /usr/share/accounts/services [00.225469] [4278] Setting AG_SERVICE_TYPES to /usr/share/accounts/service-types [00.225535] [4278] Setting DISPLAY to :0 [00.225588] [4278] Setting G_BROKEN_FILENAMES to 1 [00.225646] [4278] Setting HISTCONTROL to ignoredups [00.225713] [4278] Setting HISTSIZE to 1000 [00.225771] [4278] Setting HOME to /home/meego [00.225825] [4278] Setting HOSTNAME to localhost.localdomain [00.225882] [4278] Setting LANG to en_US.UTF-8 [00.225942] [4278] Setting LESSOPEN to |/usr/bin/lesspipe.sh %s [00.226000] [4278] Setting LOGNAME to meego [00.226052] [4278] Setting LS_COLORS to [00.226107] [4278] Setting MAIL to /var/spool/mail/meego [00.226160] [4278] Setting M_DECORATED to 0 [00.226288] [4278] Setting PATH to /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/home/meego/bin:/home/meego/bin [00.226382] [4278] Setting QMF_PLUGINS to /usr/lib/qmf/plugins [00.226442] [4278] Setting QT_IM_MODULE to MInputContext [00.226502] [4278] Setting SHELL to /bin/bash [00.226554] [4278] Setting SHLVL to 2 [00.226611] [4278] Setting USER to meego [00.226664] [4278] Setting XAUTHORITY to /home/meego/.Xauthority [00.227304] [4278] entering set_i18n [00.252902] [4278] Started Xorg[4302] [00.253084] [4278] Entering wait_for_X_signal [00.259096] [4302] starting X server with: /usr/bin/Xorg :0 -logfile /tmp/Xorg.0.meego.log -dpi 120 -nolisten tcp -noreset -auth /home/meego/.Xauthority vt2 [10.253350] [4278] done [10.311201] [4278] launching session bus: dbus-daemon --fork --session --print-pid 9 --print-address 11 [10.374446] [4278] --- environment variable dump: [10.374535] [4278] USER=meego [10.374547] [4278] LOGNAME=meego [10.374559] [4278] HOME=/home/meego [10.374570] [4278] SHELL=/bin/bash [10.374581] [4278] MAIL=/var/spool/mail/meego [10.374592] [4278] DISPLAY=:0 [10.374602] [4278] PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/home/meego/bin:/home/meego/bin [10.374614] [4278] XAUTHORITY=/home/meego/.Xauthority [10.374625] [4278] AG_PROVIDERS=/usr/share/accounts/providers [10.374636] [4278] AG_SERVICES=/usr/share/accounts/services [10.374647] [4278] AG_SERVICE_TYPES=/usr/share/accounts/service-types [10.374658] [4278] G_BROKEN_FILENAMES=1 [10.374669] [4278] HISTCONTROL=ignoredups [10.374679] [4278] HISTSIZE=1000 [10.374689] [4278] HOSTNAME=localhost.localdomain [10.374700] [4278] LANG=en_US.UTF-8 [10.374710] [4278] LESSOPEN=|/usr/bin/lesspipe.sh %s [10.374721] [4278] LS_COLORS= [10.374732] [4278] M_DECORATED=0 [10.374742] [4278] QMF_PLUGINS=/usr/lib/qmf/plugins [10.374753] [4278] QT_IM_MODULE=MInputContext [10.374764] [4278] SHLVL=2 [10.374774] [4278] XDG_CACHE_HOME=/home/meego/.cache [10.374785] [4278] XDG_CONFIG_HOME=/home/meego/.config [10.374796] [4278]
Re: [MeeGo-dev] how to port meego to snapdragon
On 04/27/11 01:49, Bo Liu wrote: Dear Cornelius and Martin, After all the rootfs was built with attached .ks successfully. Then I copied this rootfs into phone's SD card, which was mounted after kernel booting. Then the whole system (kernel + rootfs) run, but no meego GUI appears. I cat the /var/log/uxlaunch.log and found that Xorg always exited. The log is below. On the serial console, if I run command: $/usr/bin/Xorg :0 -logfile /tmp/Xorg.0.meego.log -dpi 120 -nolisten tcp -noreset -auth /home/meego/.Xauthority vt2 then x cursor appeared. So it seems that X server can run mannually. After Xorg running, I run: $export DISPLAY=:0 $xterm then xterm window appeared. So it seems that client can connect to X. So maybe the failure result from autostarting of desktop? the 10 second delay suggest that Xorg failed to start with the options that uxlaunch passes. did you build your own Xorg? please include the contents of /home/meego/.xsession-errors, after the normal graphical startup crashes. (do not start a manual Xorg). This should provide some debugging information as to why Xorg failed to start. Auke ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] how to port meego to snapdragon
Dear all, content of file /home/meego/.xsession-errors is as below. seems that there are many errors... localuser:meego being added to access control list Initializing tracker-store... Starting log: File:'/home/meego/.local/share/tracker/tracker-store.log' sion 0 Build Operating System: Linux 2.6.37-4-default armv7l Current Operating System: Linux localhost.localdomain 2.6.32.9 #11 PREEMPT Fri Apr 15 08:05:58 EDT 2011 armv7l Kernel command line: root=/dev/mmcblk0p1 rw rootfs=ext2 init=/sbin/init rootwait noinitrd console=ttyMSM2,115200n8 androidboot.hardware=qcom Build Date: 24 April 2011 07:32:54PM Build ID: xorg-x11-server 1.9.0-11.20 Current version of pixman: 0.20.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (++) Log file: /tmp/Xorg.0.meego.log, Time: Sat Jan 26 17:49:30 1980 (==) Using config file: /etc/X11/xorg.conf (==) Using config directory: /etc/X11/xorg.conf.d Primary device is not PCI (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument .. (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument (EE) PreInit returned NULL for cm3602-proximity (EE) PreInit returned NULL for kxsd9 (EE) PreInit returned NULL for W88_CTP (EE) PreInit returned NULL for surf_keypad (EE) PreInit returned NULL for docking event (EE) PreInit returned NULL for 8k_handset sh: /usr/bin/gnome-screensaver: No such file or directory Adding Master Pointer: Virtual core pointer ( 2 ) Skipping non-Touch device: Virtual core XTEST pointer ( 4 ) Skipping non-Touch device: cm3602-light ( 6 ) Adding Master Pointer: Virtual core pointer ( 2 ) Skipping non-Touch device: Virtual core XTEST pointer ( 4 ) Skipping non-Touch device: cm3602-light ( 6 ) libEGL warning: DRI2: failed to authenticate Adding Master Pointer: Virtual core pointer ( 2 ) Skipping non-Touch device: Virtual core XTEST pointer ( 4 ) Skipping non-Touch device: cm3602-light ( 6 ) Loading meegotouch-qt-style for plain qt app. PhoneProvider Initializing phone provider PhoneProvider First subscriber appeared, connecting to CallVolume modem count: 0 Adding Master Pointer: Virtual core pointer ( 2 ) Skipping non-Touch device: Virtual core XTEST pointer ( 4 ) Skipping non-Touch device: cm3602-light ( 6 ) Use system compositor void MIndicatorServiceClient::connectToIndicatorDBus() MInputContextDBusConnection was unable to connect to indicator server: The name com.meego.core.MInputMethodStatusIndicator was not provided by any .service files Adding Master Pointer: Virtual core pointer ( 2 ) Skipping non-Touch device: Virtual core XTEST pointer ( 4 ) Skipping non-Touch device: cm3602-light ( 6 ) Not loading meegotouch-qt-style for meegotouch app. meegotouch-qt-style loading success. Only the MeeGo and the native graphicssystem are supported to create shareable pixmaps. /usr/bin/sysuid Connection timeout when waiting for packet 3 Retrying. /usr/bin/sysuid Connection timeout when waiting for packet 3 Retrying. /usr/bin/sysuid Connection timeout when waiting for packet 3 Retrying. /usr/bin/sysuid Connection timeout when waiting for packet 3 Retrying. /usr/bin/sysuid Connection timeout when waiting for packet 3 Retrying. ... (repeat many times) /usr/bin//meego-im-uiserver Connection timeout when waiting for packet 3 Retrying. /usr/bin/meego-im-uiserver Connection timeout when waiting for packet 3 Retrying. ... (repeat many times) Best Regards Auke Kok auke-jan.h@intel.com 2011-04-28 02:22 To Bo Liu li...@lenovo.com cc Cornelius Hald h...@icandy.de, meego-dev@meego.com meego-dev@meego.com Subject Re: [MeeGo-dev] how to port meego to snapdragon On 04/27/11 01:49, Bo Liu wrote: Dear Cornelius and Martin, After all the rootfs was built with attached .ks successfully. Then I copied this rootfs into phone's SD card, which was mounted after kernel booting. Then the whole system (kernel + rootfs) run, but no meego GUI appears. I cat the /var/log/uxlaunch.log and found that Xorg always exited. The log is below. On the serial console, if I run command: $/usr/bin/Xorg :0 -logfile /tmp/Xorg.0.meego.log -dpi 120 -nolisten tcp -noreset -auth /home/meego/.Xauthority vt2 then x cursor appeared. So it seems that X server can run mannually. After Xorg running, I run: $export DISPLAY=:0 $xterm then xterm window appeared. So it seems that client can connect to X. So maybe the failure result from autostarting of desktop? the 10 second delay suggest that Xorg failed to start with the options that uxlaunch passes. did you build your own Xorg? please include the contents of /home/meego/.xsession-errors, after the normal graphical startup crashes. (do not
Re: [MeeGo-dev] How can I using the Accelerometer in MeeGo Tablet OS
There's a known issue with orientation sensor plugin on ExoPC. https://bugs.meego.com/show_bug.cgi?id=14818 So that libqtsensors_meego.so is not used on ExoPC, thus qt mobility accelerometer API can't work on ExoPC. Thanks, Forrest From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Pai, Cary Sent: Wednesday, April 27, 2011 12:05 PM To: meego-dev@meego.com Subject: [MeeGo-dev] How can I using the Accelerometer in MeeGo Tablet OS Hi, All, I have a project need to use the Accelerometer in MeeGo Tablet OS, I run the qt mobility example accel in ExoPC with MeeGo tablet 1.2 pre-alpha OS, but it shows the error message tell me Accelerometer didn't start!, and tracing the code obviously the accelerometer didn't start normally, please tell me how can I start the accelerometer in MeeGo successfully, is there any settings that I need to set? Best Regards. Intel Software Service Group [cid:image001.jpg@01CC0593.6AE892E0] B1 #205 Tun-Hwa North Rd, Taipei, Taiwan Desk +886-2-2514-4603 Mobile +886-987-369-617 E-Mail cary@intel.commailto:gorden.n...@intel.com inline: image001.jpg___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
