Re: [MeeGo-dev] [Meego-qa] Faild to build image for armv7hl with latest mic

Hi, the problem in here is that you are not using bootstrap mode. armv7hl architecture is not supported by your host distribution tools and thus you can't use legacy mode to build armv7hl image. So add --run-mode=1 to the cmdline and you should be fine. Also should be noted that to build armv7hl i

Re: [MeeGo-dev] Can not tracker *.rm/rmvb files

Hi Adrien Bustany thanks for your reply Can you please run /usr/libexec/tracker-extract -f on your video file > and > paste the output somewhere? ->the attachment is the output of the command line /usr/libexec/tracker-extract -f /home/meego/Videos/rm/rm_30.rm. According to the output,it see

Re: [MeeGo-dev] Faild to build image for armv7hl with latest mic

yes, but in mic/imgcreate/pkgmanagers/yumpkgmgr.py 50 <#line50> class Yum(yum.YumBase): 51 <#line51> def __init__(self, creator = None, recording_pkgs=None): 52 <#line52> if not isinstance(creator, ImageCreator): 53 <#line53> raise CreatorError("Invalid argument:

Re: [MeeGo-dev] Faild to build image for armv7hl with latest mic

I am using the latest version of mic from Gitorious: in image-creator/tools/mic-image-creator, it shows arch armv7hl is supported. 615 if options.release and options.run_mode == 0:

Re: [MeeGo-dev] Faild to build image for armv7hl with latest mic

>>> rpmUtils.arch.arches.keys() ['ppc', 'x86_64', 'armv5tejl', 'i586', 'sparc', 'geode', 'ppc64', 'i486', 'alphapca56', 'alphaev7', 'alphaev6', 'i386', 'alphaev45', 'armv5tel', 'sh4a', 'alpha', 'ia64', 'ppc64iseries', 'ia32e', 'sparcv9v', 's390', 'athlon', 'sh3', 'sh4', 'amd64', 'sparcv8', 'sparcv9

Re: [MeeGo-dev] Can not tracker *.rm/rmvb files

On Tue, 12 Apr 2011 09:33:10 +0800, yinxb wrote: Hi Hi there I encounters a confusing problem that the *.rm/rmvb video files can not be trackered by the following SQL Not SQL, SPARQL :) "SELECT nie:url(nie:isStoredAs(?video)) WHERE{?video a nmm:Video}"; You don't need the isStoredAs he

Re: [MeeGo-dev] meego table screen saver

On 04/11/2011 08:48 PM, Mark S. Townsley wrote: Hi I am running the meego table release. The screen saver is nice but I want to turn it off at times. I look under settings but cannot find relevant settings. Is there a way to do so? I looked under /etc/X11 but did not see anything either.

[MeeGo-dev] meego table screen saver

Hi I am running the meego table release. The screen saver is nice but I want to turn it off at times. I look under settings but cannot find relevant settings. Is there a way to do so? I looked under /etc/X11 but did not see anything either. Thanks Mark __

[MeeGo-dev] Faild to build image for armv7hl with latest mic

*OS:* FC 13 *MIC* version: 0.24.8 *Cmdline:* mic-image-creator --arch=armv7hl --pkgmgr=yum --format=raw --save-kernel --package=tar.gz --config=meego-handset-armv7hl-n900-1.1.99.1.20110406.102.ks *run-mode* = 0 (legacy) *Error: failed to create image : Invalid target arch: armv7hl* * * I deep i

[MeeGo-dev] Can not tracker *.rm/rmvb files

Hi I encounters a confusing problem that the *.rm/rmvb video files can not be trackered by the following SQL "SELECT nie:url(nie:isStoredAs(?video)) WHERE{?video a nmm:Video}"; I analysed the /usr/share/mime/packages/freedesktop.org.xml that the mime type []is defined. Also,I found only

[MeeGo-dev] Dialer Project meeting - Agenda for Tuesday 4/12

First, my apologies for limited communications last week, I fell ill on Wednesday and was out sick until Monday morning PST Second, if you would like to add to this agenda, please send me your request by 7am PST (14:00UTC IIRC) Tuesday. Agenda for the Dialer Project meeting - Tuesday, April 12th,

Re: [MeeGo-dev] Fwd: [MeeGo-ivi] Bug #12777 - usbtouchscreen driver

- "Carsten Munk" wrote: > 2011/4/11 Clark, Joel : > > These conneXt kernel changes? > > > http://lists.meego.com/pipermail/meego-commits/2011-March/019591.html > > > http://lists.meego.com/pipermail/meego-commits/2011-April/020569.html > > Yeah, just needs to be passed on to Trunk:Testing -

Re: [MeeGo-dev] Fwd: [MeeGo-ivi] Bug #12777 - usbtouchscreen driver

2011/4/11 Clark, Joel : > These conneXt kernel changes? > http://lists.meego.com/pipermail/meego-commits/2011-March/019591.html > http://lists.meego.com/pipermail/meego-commits/2011-April/020569.html Yeah, just needs to be passed on to Trunk:Testing - then we can slide in the evdev fix and nothing

Re: [MeeGo-dev] Fwd: [MeeGo-ivi] Bug #12777 - usbtouchscreen driver

These conneXt kernel changes? http://lists.meego.com/pipermail/meego-commits/2011-March/019591.html http://lists.meego.com/pipermail/meego-commits/2011-April/020569.html regards Joel -Original Message- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of

Re: [MeeGo-dev] Fwd: [MeeGo-ivi] Bug #12777 - usbtouchscreen driver

2011/4/11 Nasa : > Hi gang, > > Per Joel's suggestion, I Wanted to ask a quick question...  The patch from > the 12777 bug report seems > to have fixed tsc2007 - looking at the code for usbtouchscreen.c, I don't > see why a similar patch couldn't be done for it (and possbily others).  Does > anyon

Re: [MeeGo-dev] Audio performance in MeeGo

>> I was able to reduce CPU load in audio playback in meego-ivi a few months >> back. This was all done by tweaking the buffer parameters of audio sink >> while playing with Gstreamer. How can we make sure that the user benefits >> from the changes? >> What are the players in meego-ivi that uses Gs

Re: [MeeGo-dev] [Meego-architecture] Another architecture direction mail

On 05/04/11 08:59, Antti Kaijanmäki wrote: On Fri, 2011-04-01 at 09:07 -0700, Arjan van de Ven wrote: Late last year, in the Architecture meeting, we had agreed to include timed, MCE, Sharing Framework, Non-Graphics-Feedback (NGF), Profiles, and Qt style APIs (QmSystem) identified on the http:/

Re: [MeeGo-dev] Audio performance in MeeGo

did these adjustments get merged into MeeGo's gstreamer then? Auke On 04/11/11 09:58, Clark, Joel wrote: This really applies to all MeeGo players using gstreamer, not just the IVI ones. regards Joel From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Alam

[MeeGo-dev] Fwd: [MeeGo-ivi] Bug #12777 - usbtouchscreen driver

Hi gang, Per Joel's suggestion, I Wanted to ask a quick question... The patch from the 12777 bug report seems to have fixed tsc2007 - looking at the code for usbtouchscreen.c, I don't see why a similar patch couldn't be done for it (and possbily others). Does anyone know if that is being addr

Re: [MeeGo-dev] Audio performance in MeeGo

This really applies to all MeeGo players using gstreamer, not just the IVI ones. regards Joel From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Alam, Nahid M Sent: Monday, April 11, 2011 9:37 AM To: meego-dev@meego.com Subject: [MeeGo-dev] Audio performance in

Re: [MeeGo-dev] FW: execute MTF application by command line error

On Apr 11, 2011, at 12:57 AM, Pai, Cary wrote: > Hi, > > I have a simple MTF application, I want to get the error message from this > application, so I want to launch the application from command line, and I can > easily get the error message from command line, but after I launch the MTF > a

[MeeGo-dev] Audio performance in MeeGo

Hello, I was able to reduce CPU load in audio playback in meego-ivi a few months back. This was all done by tweaking the buffer parameters of audio sink while playing with Gstreamer. How can we make sure that the user benefits from the changes? What are the players in meego-ivi that uses Gstream

Re: [MeeGo-dev] Window Manager Issues (Handset and Tablet)

On 04/11/2011 07:33 AM, Gabriel Beddingfield wrote: Hi Rusty, On Sat, Apr 9, 2011 at 11:53 AM, Rusty Lynch wrote: On 04/09/2011 06:52 AM, Gabriel M. Beddingfield wrote: On the latest daily builds for Handset and Tablet there are no title bars (including app switcher button and app c

Re: [MeeGo-dev] ANNOUNCE: [ABI break] MeeGo 1.2 ARM architecture will only support hardfp ABI

On 11/04/11 17:26, ext Arjan van de Ven wrote: can you, for completeness, list a set of ARM SOC's that this hardfp will run on... omap3 tegra? qualcom ? asking because if it's only omap3 then I think this is a step in the wrong direction and we should revisit the TSG decision. Hi, supporti

Re: [MeeGo-dev] ANNOUNCE: [ABI break] MeeGo 1.2 ARM architecture will only support hardfp ABI

2011/4/11 Arjan van de Ven : > On 4/11/2011 5:28 AM, Juha Kallioinen wrote: >> >> Hello, >> >> the hardfp floating point ABI for ARM will be made default and mandatory >> for MeeGo 1.2 and later. This decision was made and approved back in >> December 2010 in the MeeGo TSG and the impact has been d

Re: [MeeGo-dev] Window Manager Issues (Handset and Tablet)

Hi Rusty, On Sat, Apr 9, 2011 at 11:53 AM, Rusty Lynch wrote: > On 04/09/2011 06:52 AM, Gabriel M. Beddingfield wrote: >> >> On the latest daily builds for Handset and Tablet there are >> no title bars (including app switcher button and app close >> button). Will there be any?  Nor do apps get au

Re: [MeeGo-dev] ANNOUNCE: [ABI break] MeeGo 1.2 ARM architecture will only support hardfp ABI

On 4/11/2011 5:28 AM, Juha Kallioinen wrote: Hello, the hardfp floating point ABI for ARM will be made default and mandatory for MeeGo 1.2 and later. This decision was made and approved back in December 2010 in the MeeGo TSG and the impact has been described in MeeGo wiki [1]. The hardfp sc

Re: [MeeGo-dev] Window Manager Issues (Handset and Tablet)

On Mon, 11 Apr 2011, Kimmo Hämäläinen wrote: The fullscreen ones don't have WM buttons at all and are resized to fullscreen by the WM. Currently the non-fullscreen ones get buttons and are resized so that they fill the remaining free space. [snip] This is what the git version does, I'm no

Re: [MeeGo-dev] Window Manager Issues (Handset and Tablet)

On 04/09/11 16:52, ext Gabriel M. Beddingfield wrote: On the latest daily builds for Handset and Tablet there are no title bars (including app switcher button and app close button). Will there be any? Nor do apps get automatically expanded to fit the screen. Will they be? There are two kinds

Re: [MeeGo-dev] ANNOUNCE: [ABI break] MeeGo 1.2 ARM architecture will only support hardfp ABI

On 04/11/2011 03:28 PM, Juha Kallioinen wrote: Hello, the hardfp floating point ABI for ARM will be made default and mandatory for MeeGo 1.2 and later. This decision was made and approved back in December 2010 in the MeeGo TSG and the impact has been described in MeeGo wiki [1]. The hardfp

Re: [MeeGo-dev] ANNOUNCE: [ABI break] MeeGo 1.2 ARM architecture will only support hardfp ABI

2011/4/11 Thiago Macieira : > Em segunda-feira, 11 de abril de 2011, às 15:28:59, Juha Kallioinen escreveu: >> The hardfp scheduler is called armv8el and is up and running in MeeGo Trunk. > > Why are we calling it ARMv8? All I can find about it are future references, Long story short, we ran into a

Re: [MeeGo-dev] ANNOUNCE: [ABI break] MeeGo 1.2 ARM architecture will only support hardfp ABI

Em segunda-feira, 11 de abril de 2011, às 15:28:59, Juha Kallioinen escreveu: > The hardfp scheduler is called armv8el and is up and running in MeeGo Trunk. Why are we calling it ARMv8? All I can find about it are future references, like: http://drdobbs.com/210800195 and talking about fut

Re: [MeeGo-dev] FW: execute MTF application by command line error

Em segunda-feira, 11 de abril de 2011, às 12:42:02, Stanislav Ionascu escreveu: > If the apps launch as a user, then do: > $ echo $DBUS_SESSION_BUS_ADDRESS > > and then as root export the result: > # export DBUS_SESSION_BUS_ADDRESS=result_of_echo_as_user Not necessarily. $ sudo DBUS_SESSION_BUS_A

[MeeGo-dev] ANNOUNCE: [ABI break] MeeGo 1.2 ARM architecture will only support hardfp ABI

Hello, the hardfp floating point ABI for ARM will be made default and mandatory for MeeGo 1.2 and later. This decision was made and approved back in December 2010 in the MeeGo TSG and the impact has been described in MeeGo wiki [1]. The hardfp scheduler is called armv8el and is up and running

[MeeGo-dev] [SSO] Fixed Storage Dir Permissions + Authentication Core Cache Improvements

Hi, Please review a few fixes and improvements: 1. Fixed permissions for the Signon storage directory. This will allow `Restore` operation to work. https://gitorious.org/accounts-sso/signon/commit/955acb690aab318633a64d0c536f5137362e95e6 2. Allow authentication core cache to append BLOB auth

Re: [MeeGo-dev] FW: execute MTF application by command line error

Could you please try "export $(dbus-launch)" first before run the application? Regards, Jammy On Mon, Apr 11, 2011 at 5:09 PM, Pai, Cary wrote: > HI, Stanislav, > > I have tried your suggestion, and I can't find the file named > "session_bus_address.user", so I create on by myself under tmp fol

Re: [MeeGo-dev] FW: execute MTF application by command line error

Hi, If the apps launch as a user, then do: $ echo $DBUS_SESSION_BUS_ADDRESS and then as root export the result: # export DBUS_SESSION_BUS_ADDRESS=result_of_echo_as_user Then you should be able to launch the app as root. Best Regards, Stanislav Ionascu. On Mon, 2011-04-11 at 17:09 +0800, ext Pa

Re: [MeeGo-dev] FW: execute MTF application by command line error

Em segunda-feira, 11 de abril de 2011, às 16:56:00, Pai, Cary escreveu: > Thanks for your response, I am using the root to launch the application, and > the DISPLAY have already set to 0, after I tested and the result is the > application can be launched successfully if you do not use the root to >

Re: [MeeGo-dev] Candidate specification for a generic video player from the TV list

On 11 April 2011 10:21, Stefan Kost wrote: > My suggestion is to avoid this scenario totally. Having different > pipelines depending on systems state is increasing the complexity of > your system a lot. Apply the KISS pattern. Multimedia is complex enough > due to the sheer amount of formats, code

Re: [MeeGo-dev] FW: execute MTF application by command line error

HI, Stanislav, I have tried your suggestion, and I can't find the file named "session_bus_address.user", so I create on by myself under tmp folder, but it still shows the same error message, thanks for your response. Best Regards. Intel Software & Service Group     B1 #205 Tun-Hwa North Rd

Re: [MeeGo-dev] FW: execute MTF application by command line error

Hi, To launch MTF application as root, you need to do first as root: # export DISPLAY=:0 # source /tmp/session_bus_address.user And then you can launch your application. Best Regards, Stanislav Ionascu On Mon, 2011-04-11 at 16:56 +0800, ext Pai, Cary wrote: > Hi, Marko, > > Thanks for your res

Re: [MeeGo-dev] FW: execute MTF application by command line error

Hi, Marko, Thanks for your response, I am using the root to launch the application, and the DISPLAY have already set to 0, after I tested and the result is the application can be launched successfully if you do not use the root to launch it. Best Regards. Intel Software & Service Group   

Re: [MeeGo-dev] how to run meego-ux's meego-app-camera on MeeGo 1.2 Netbook?

On 04.04.2011 02:27, Niels Mayer wrote: > After doing > $ zypper ar > http://download.meego.com/live/devel:/meego-ux/Trunk/devel:meego-ux.repo > $ zypper zypper clean --all ; zypper --gpg-auto-import-keys refresh > $ zypper in meego-app-camera meego-app-video meego-app-photos > meego-app-not

Re: [MeeGo-dev] Candidate specification for a generic video player from the TV list

hi, On 25.03.2011 18:28, Cory T. Tusar wrote: > On 03/25/2011 11:23 AM, Edward Hervey wrote: > >> On Fri, 2011-03-25 at 10:58 -0400, Cory T. Tusar wrote: > >>> On 03/17/2011 06:57 AM, Stefan Kost wrote: > >> > >> > >> > >>> In "7 Transparency" you need to highlight what your proposal adds > to th

Re: [MeeGo-dev] FW: execute MTF application by command line error

Hi, Did you export DISPLAY=:0 and are you running the app as normal user and not root? Also it might be that you need to export DBUS variables to the environment, see bug: https://bugs.meego.com/show_bug.cgi?id=9049 Regards, Marko On 04/11/2011 10:57 AM, Pai, Cary wrote: Hi, I have a sim

[MeeGo-dev] FW: execute MTF application by command line error

Hi, I have a simple MTF application, I want to get the error message from this application, so I want to launch the application from command line, and I can easily get the error message from command line, but after I launch the MTF application, I get error message about : "ERROR : No DBUS sessi