Re: [MeeGo-dev] mic2: can't get netbook to boot
Hi, I created a netbook liveusb image using the instructions here[1]. When I boot, all I get is boot:. If I enter 'vmlinuz0', it tries to boot but fails because I didn't specify a root fs. Any clues on where I went wrong? Build System: Ubuntu 10.04 on Core 2 Solo CPU Versions: mic2 0.21.1 (meego repos) syslinux 2:4.02 (meego repos) Target System: Atom N450 CPU I found one similar bug.[2] However, it got marked INVALID because of the OP's target system. I noticed this issue. It's likely a bug in mic2. Official netbook weekly build image are working. If you take the same ks file and try to create the image yourself on Debian/Ubuntu, you'll be able to generate an image successfully but the image is broken somehow. I noticed the generated image is ~100 Mb larger (~850 Mb instead of 750Mb). Cheers, Fathi ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] dbus-send command/python dbus way for launching voip call through GTalk on N900
I did dbus-monitor on manual voip Gtalk call and from the dump, I think that
the below trace is actually making the call. here I called from my Gmail
account(prawin1...@gmail.com) to another gmail account(
mail_under_t...@gmail.com) through Gtalk.
*method call sender=:1.17 - dest=org.freedesktop.Telepathy.Client.CallUI
serial=262 path=/org/freedesktop/Telepathy/Client/CallUI;
interface=org.freedesktop.Telepathy.Client.Interface.Requests;
member=AddRequest*
* object path /com/nokia/MissionControl/requests/r4*
* array [*
* dict entry(*
* string org.freedesktop.Telepathy.ChannelRequest.Account*
* variant object path
/org/freedesktop/Telepathy/Account/gabble/jabber/prawin_40gmail_2ecom0
*
* )*
* dict entry(*
* string org.freedesktop.Telepathy.ChannelRequest.UserActionTime*
* variant uint64 1234133*
* )*
* dict entry(*
* string org.freedesktop.Telepathy.ChannelRequest.PreferredHandler
*
* variant string *
* )*
* dict entry(*
* string org.freedesktop.Telepathy.ChannelRequest.Interfaces*
* variant array [*
*]*
* )*
* dict entry(*
* string org.freedesktop.Telepathy.ChannelRequest.Requests*
* variant array [*
* array [*
* dict entry(*
* string
org.freedesktop.Telepathy.Channel.TargetHandleType*
* variant uint32 1*
* )*
* dict entry(*
* string org.freedesktop.Telepathy.Channel.TargetID*
* variant string
mail_under_t...@gmail.com*
* )*
* dict entry(*
* string org.freedesktop.Telepathy.Channel.ChannelType
*
* variant string
org.freedesktop.Telepathy.Channel.Type.StreamedMedia*
* )*
* ]*
*]*
* )*
* ]*
Please anybody help me writing python-dbus code or dbus-send command for the
above dbus-monitor trace.
Thanks in advance.
On Wed, Oct 6, 2010 at 10:35 AM, praveen koduru prawin1...@gmail.comwrote:
I am looking for voice call through Gtalk on N900 from command line like
dbus-send command or python-dbus.
I am able to set the status i.e GTalk presence(Online/Offline/Busy)
through mc-tool command,
*mc-tool account presence*
*
*
*python-dbus way:*
*
xmppaccount=/org/freedesktop/Telepathy/Account/gabble/jabber/prawin_40gmail_2ecom0
def set_status(presence_type):
print screen has been off for defined number of seconds
sessionbus = dbus.SessionBus()
gmailobj =
sessionbus.get_object('org.freedesktop.Telepathy.AccountManager',
xmppaccount)
gmailinterface=dbus.Interface(gmailobj,
'org.freedesktop.DBus.Properties')
gmailstruct=dbus.Struct((dbus.UInt32(presence_type), '', ''))
gmailinterface.Set('org.freedesktop.Telepathy.Account',
'RequestedPresence', gmailstruct)
bus = dbus.SystemBus()
set_status(telepathy.constants.CONNECTION_PRESENCE_TYPE_BUSY)
*
*
*
And also I am able to do voice call through GSM network using dbus-send
command.
*dbus-send --system --type=method_call --print-reply
--dest=com.nokia.csd.Call /com/nokia/csd/call com.nokia.csd.Call.CreateWith
string:$NUMBER uint32:0*
But i need to make a voice call through Gtalk using dbus-send or
python-dbus.
Thanks for the time. and Help needed.
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] [Qt-mobility-feedback] qt-mobility unconference/BoF/meetup
-Original Message- From: qt-mobility-feedback-boun...@trolltech.com [mailto:qt-mobility- feedback-boun...@trolltech.com] On Behalf Of ext Michael Leibowitz The QtMobility APIs are a key part of MeeGo and MeeGo will emerge as a key user and hopefully driver of some of these APIs. I propose that a unconference/BoF/meetup at the 2010 MeeGo conference in November of interested parties to discuss current and future activities around the QtMobility project in MeeGo. If interested, please chime in. Just as an update. Mobility developers will attend the conference too. -- Alex ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] [meego-packaging] QtMobility has branched
Hi, QMF 2010w36 and Qt Mobility 1.1.0 beta 2 packages are submitted to Trunk:Testing (SR#8109 and SR#8110). Qt Mobility 1.1.x devel project: http://build.meego.com/package/show?package=qt-mobilityproject=devel:qt-mtf Qt Mobility 1.2.x devel project: http://build.meego.com/package/show?package=qt-mobilityproject=devel:qt-mtf:qt-mobility:1.2 Cheers, Fathi ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] [meego-packaging] QtMobility has branched
Em Terça-feira 05 Outubro 2010, às 18:51:45, Arjan van de Ven escreveu: On 10/5/2010 8:53 AM, Thiago Macieira wrote: Released in final versions at feature freeze? Would a beta or RC suffice for feature freeze of core components? I don't think it's realistic to already plan to be late... if a realistic schedule slips a week or two, well sh** happens. But if at the plan level it doesn't line up, that's not going to work. So we're not going to update to X.org 1.10? This will seriously impact any plans to provide proper touch support. If we're not upgrading to X.org 1.10 in MeeGo 1.2, we'll get out of headless chicken mode for now and plan proper touch support for MeeGo 1.3. Taking the cue from: http://www.mail-archive.com/xorg-de...@lists.x.org/msg12373.html What are the options to pull in the QtMobility 1.2 schedule ? Min will probably say what the options are. But I've already got a couple of desperate emails in my inbox on this subject. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Senior Product Manager - Nokia, Qt Development Frameworks PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 Qt Developer Days 2010 - Munich Oct 11-13 - San Francisco Nov 1-3 For more information and to register: http://qt.nokia.com/qtdevdays2010 signature.asc Description: This is a digitally signed message part. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] dbus-send command/python dbus way for launching voip call through GTalk on N900
Hi Praveen, praveen koduru wrote: I am looking for voice call through Gtalk on N900 from command line like dbus-send command or python-dbus. I'm afraid I don't have an answer to your question, but if/when you get an answer, would you mind taking a minute to synthesise it into a use-case in the wiki, please? It will help enrich it as a knowledge base for those coming after you. You might consider using the use-case template at http://wiki.maemo.org/Documentation/Use_case_template and adding the page to the bottom of http://wiki.maemo.org/Documentation (perhaps the page name could be http://wiki.maemo.org/Launching_GTalk_voice_call ?) Cheers, Dave. -- maemo.org docsmaster Email: dne...@maemo.org Jabber: bo...@jabber.org ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] mic2: can't get netbook to boot
On Wednesday, October 06, 2010 01:08:54 am you wrote: If you take the same ks file and try to create the image yourself on Debian/Ubuntu, you'll be able to generate an image successfully but the image is broken somehow. Did it ever work on Debian/Ubuntu? Would it be worthwhile if I did a bisect? Thanks, Gabriel ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] mic2: can't get netbook to boot
On Wednesday, October 06, 2010 01:08:54 am you wrote: If you take the same ks file and try to create the image yourself on Debian/Ubuntu, you'll be able to generate an image successfully but the image is broken somehow. Did it ever work on Debian/Ubuntu? I don't know. Would it be worthwhile if I did a bisect? Ubuntu 10.04 being a supported host, it makes more sense to open a bug report and make sure it's reproducible. If you're able to debug and fix the issue, it's even better. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Tracker (Content FW) unconference/BOF
Hi, I propose also an uncoferenced session about Tracker in Meego. Application developers should get at least an idea of what it does, specially if all the data is going to be there! Added in the wiki. [1] Hope to see you there! Ivan Frade [1] http://wiki.meego.com/MeeGo_Conference_2010/Unconference ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] TSG meeting cancelled - sorry
Hi, There was a TSG meeting starting in few minutes but we must cancel it due to lack of quorum. Sorry about that. We will communicate the new date and agenda as soon as it's ready. For more information about TSG Meetings check http://wiki.meego.com/Technical_Steering_Group_meetings -- Quim Gil ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Compliance spec before final approval
Hi: Do you have a near-final version somewhere I can download? Thanks --Mark On Sun, Oct 3, 2010 at 3:15 PM, Skarpness, Mark mark.skarpn...@intel.comwrote: Hi Carsten, Yes, I agree - we will work to get a near final version of the spec out at least a week before requesting approval at the TSG meeting. Regards, -Mark On 9/29/10 10:34 AM, Carsten Munk cars...@maemo.org wrote: Hi Mark, I noticed at the TSG meeting schedule on wiki that the final compliance spec will be scheduled for final approval either on oct 13 or 20 by TSG. Would it be possible to publish the intended-to-be-approved compliance spec publically either one or two weeks before final approval so there is time for possibly implicated people and companies to comment on the spec before it's approved? While the compliance spec usually raises a lot of discussion, I think it's worthwhile to help get input from the people and companies that will in the last end have to deal with the compliance spec to catch early errors, technological impossibilities and to help plan work within compliance area for 1.2 timeframe. Best regards, Carsten Munk ___ 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] [meego-packaging] QtMobility has branched
Hi Arjan, The Qt Mobility 1.2 integration plan has been discussed within MeeGo Core OS program stream and feature freeze in December is new to me. Although it is a draft, the feature freeze is end of January according to the release engineering plan of MeeGo 1.2. http://wiki.meego.com/Release_Engineering/Plans/1.2 Can you tell me the source of December deadline so I can confirm? We will have to adjust Mobility release plan if needed. Regards, Min -Original Message- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of ext Arjan van de Ven Sent: Wednesday, 6 October 2010 1:22 AM To: Thiago Macieira Cc: meego-dev@meego.com Subject: Re: [MeeGo-dev] [meego-packaging] QtMobility has branched On 10/5/2010 8:19 AM, Thiago Macieira wrote: Em Terça-feira 05 Outubro 2010, às 17:04:03, Arjan van de Ven escreveu: for QtMobility 1.2 to be an option for MeeGo 1.2, it needs to be released by the end of December. I assume the Nokia QtMobility guys are committing to this. But this means we need to get a beta version few weeks before that, and an alpha a few weeks before that. guess what it's pretty soon already so the period of instability is going to be really really short, short enough for MeeGo to just wait it out. I think the Mobility 1.2 release is January, not December. then it's not going to make MeeGo 1.2, and will make MeeGo 1.3 instead Feature freeze in December means what it means; all fundamental, core libraries and components need to be released at that point. And QtMobility certainly is such a core fundamental library. ___ 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] qt-mobility unconference/BoF/meetup
Hi, Definitely a good idea. Qt Mobility PMs including myself are attending the event. It would be a great opportunity to discuss Mobility 1.2 activities and 1.3 roadmap as well. We plan to align the Qt Mobility release cycle with the MeeGo release cycle. It seem we can only post a session on that day. http://wiki.meego.com/MeeGo_Conference_2010/Unconference Regards, Min -Original Message- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of ext Thiago Macieira Sent: Tuesday, 5 October 2010 4:57 PM To: meego-dev@meego.com Subject: Re: [MeeGo-dev] qt-mobility unconference/BoF/meetup On Tuesday 5. October 2010 05.47.24 Michael Leibowitz wrote: The QtMobility APIs are a key part of MeeGo and MeeGo will emerge as a key user and hopefully driver of some of these APIs. I propose that a unconference/BoF/meetup at the 2010 MeeGo conference in November of interested parties to discuss current and future activities around the QtMobility project in MeeGo. If interested, please chime in. Sounds like a good idea. Please write it on the unconference wiki so we'll gather the interested people there. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Senior Product Manager - Nokia, Qt Development Frameworks PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] [meego-packaging] QtMobility has branched
Arjan all, If I remember correctly some F2F discussions on this topic (on a place close to Espoo), december deadline is not valid for those components that we are specifically developing for MeeGo 1.2, like QtMobility 1.2 in question. If it is not obvious already, this QtM release is designed for MeeGo 1.2 purposes. So what was suggested by Thiago should be OK for MeeGo 1.2. Br, //Harri From: meego-dev-boun...@meego.com [meego-dev-boun...@meego.com] On Behalf Of ext minjung.s...@nokia.com [minjung.s...@nokia.com] Sent: Wednesday, October 06, 2010 10:54 PM To: ar...@linux.intel.com; thi...@kde.org Cc: meego-dev@meego.com Subject: Re: [MeeGo-dev] [meego-packaging] QtMobility has branched Hi Arjan, The Qt Mobility 1.2 integration plan has been discussed within MeeGo Core OS program stream and feature freeze in December is new to me. Although it is a draft, the feature freeze is end of January according to the release engineering plan of MeeGo 1.2. http://wiki.meego.com/Release_Engineering/Plans/1.2 Can you tell me the source of December deadline so I can confirm? We will have to adjust Mobility release plan if needed. Regards, Min -Original Message- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of ext Arjan van de Ven Sent: Wednesday, 6 October 2010 1:22 AM To: Thiago Macieira Cc: meego-dev@meego.com Subject: Re: [MeeGo-dev] [meego-packaging] QtMobility has branched On 10/5/2010 8:19 AM, Thiago Macieira wrote: Em Terça-feira 05 Outubro 2010, às 17:04:03, Arjan van de Ven escreveu: for QtMobility 1.2 to be an option for MeeGo 1.2, it needs to be released by the end of December. I assume the Nokia QtMobility guys are committing to this. But this means we need to get a beta version few weeks before that, and an alpha a few weeks before that. guess what it's pretty soon already so the period of instability is going to be really really short, short enough for MeeGo to just wait it out. I think the Mobility 1.2 release is January, not December. then it's not going to make MeeGo 1.2, and will make MeeGo 1.3 instead Feature freeze in December means what it means; all fundamental, core libraries and components need to be released at that point. And QtMobility certainly is such a core fundamental library. ___ 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 ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] libsatsolver usabililty
Hi, building and dependency resolving is for the MeeGo project usually done with an automated buildsystem called OBS: http://en.opensuse.org/Portal:Build_Service OBS itself also uses libsatsolver in its scheduler to calculate dependencies automatically. Since OBS is such a robot, we do usually not cal many dependencies these days by hand anymore. Martin ssrk wrote: Hi, I found this package 'libsatsolver' in the meego repo. From the description got know that this library is used for package dependency solving and also came to know that this internally used by zypper package manager. I am trying to build many meego packages and so before start building I want to know the list of dependencies for each package Is there any possible way to use this library APIs by external programs and generate the dependency list of input packages ? Is there any API documentation available for this library? Please help. Thanks in advance -- Regards, ssrk ___ 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] Compliance spec before final approval
Mark please publish the spec and give the teams a week to review and comment. Thanks Chris From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Mark S. Townsley Sent: Wednesday, October 06, 2010 12:11 PM To: Skarpness, Mark Cc: meego-dev Subject: Re: [MeeGo-dev] Compliance spec before final approval Hi: Do you have a near-final version somewhere I can download? Thanks --Mark On Sun, Oct 3, 2010 at 3:15 PM, Skarpness, Mark mark.skarpn...@intel.com wrote: Hi Carsten, Yes, I agree - we will work to get a near final version of the spec out at least a week before requesting approval at the TSG meeting. Regards, -Mark On 9/29/10 10:34 AM, Carsten Munk cars...@maemo.org wrote: Hi Mark, I noticed at the TSG meeting schedule on wiki that the final compliance spec will be scheduled for final approval either on oct 13 or 20 by TSG. Would it be possible to publish the intended-to-be-approved compliance spec publically either one or two weeks before final approval so there is time for possibly implicated people and companies to comment on the spec before it's approved? While the compliance spec usually raises a lot of discussion, I think it's worthwhile to help get input from the people and companies that will in the last end have to deal with the compliance spec to catch early errors, technological impossibilities and to help plan work within compliance area for 1.2 timeframe. Best regards, Carsten Munk ___ 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] Tracker (Content FW) unconference/BOF
Hi~~ Is there any information of the session? document or slide ?? Thanks a lot. 2010/10/6 Ivan Frade ivan.fr...@gmail.com Hi, I propose also an uncoferenced session about Tracker in Meego. Application developers should get at least an idea of what it does, specially if all the data is going to be there! Added in the wiki. [1] Hope to see you there! Ivan Frade [1] http://wiki.meego.com/MeeGo_Conference_2010/Unconference ___ 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
[MeeGo-dev] SSO
Hi~~ I found that there is a session of SSO on 24 Sep 2010 11:52:11 (UTC). Is there any information of the session? document or slide ?? Thanks a lot. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
