[MeeGo-dev] signon-qt: ABI/ABI break
Hello! Summary: a backwards incompatible change in signon-qt has entered MeeGo Trunk, apps using it need to be updated and recompiled. Details: I just noticed that one of my executables using signon-qt stopped working after an update to recent MeeGo Trunk: it starts, but fails to connect to signal SignOn::AuthService::identities(const QListIdentityInfo ). The reason is that the signon-qt API was cleaned up. It now provides SignOn::AuthService::identities(const QListSignOn::IdentityInfo ), with namespace for IdentityInfo. Same for Error and SessionData. Apps are no longer forced to use using namespace SignOn to compile and now must use the SignOn:: prefix in slots/signals. Note that the soname of signon-qt wasn't changed, so my executable continued to run. I would have preferred to get a libsignon-qt.so.1 not found error. I was expecting this change to happen and knew what to look for, but others might spend more time debugging this... I can no longer verify it (old files gone), but it seems that the database layout in .signon also changed, which removed all of my stored credentials. Alberto, is that possible? It's not a big deal at this point, but once signon really holds end-user data, a better upgrade path would be useful. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Qt uses OpenSSL, and fails?
Hello! A bug report about Buteo not syncing with Google via https [1] showed that Qt tries to load OpenSSL libraries, which fails because they are not installed where they are expected [2]. There is an open request to change that [3]. First, is someone working on 7813? The original issue # was marked as resolved with a comment that Fix is already available in 1.1 branch., but it doesn't say what the fix was, and Trunk obviously is still affected. Makoto, can you clarify? Second, as mentioned in # and elsewhere [4], there is a license conflict between OpenSSL and GPL. Does opening OpenSSL via dlopen() at runtime really work around this conflict? I'm not a lawyer, but given that the way how linking is achieved is typically not specified in detail in licenses, I doubt that using dlopen() instead of ld.so really works around the license issue. [1] http://bugs.meego.com/show_bug.cgi?id=11024 [2] http://bugs.meego.com/show_bug.cgi?id=#c3 [3] http://bugs.meego.com/show_bug.cgi?id=7813 [4] http://people.gnome.org/~markmc/openssl-and-the-gpl.html -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] signon-qt: ABI/ABI break
On Mi, 2010-12-08 at 08:08 +, Patrick Ohly wrote: The reason is that the signon-qt API was cleaned up. It now provides SignOn::AuthService::identities(const QListSignOn::IdentityInfo ), with namespace for IdentityInfo. Same for Error and SessionData. Error now is passed by value, so use SignOn::Error, not const SignOn::Error . -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo
Em Terça-feira, 7 de Dezembro de 2010, às 20:49:37, Gabriel M. Beddingfield escreveu: Another clue: following issue: Program received signal SIGILL, Illegal instruction. 0xa144 in __aeabi_d2lz () ^^ While this /could/ be a valid pointer, this address looks like a bogus pointer to me. I rarely see pointers this low in an application. This also suggests a buffer overrun and a corrupted stack. It probably is a valid pointer, because the debugger resolved it to __aeabi_d2lz. I looked at the ABI spec and it says d2lz is convert double to C long and it may be implemented either in software or in hardware. Looks to me like you installed a libgcc_s.so which is not compatible with your hardware. -- 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 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] fennec(Illegal instruction) issue on MeeGo
Hi Thiago, Thank you so much and I found an instruction which not supported by my processor in '__aeabi_d2lz'. :) B.R Paul -Original Message- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Thiago Macieira Sent: 2010年12月8日 17:50 To: meego-dev@meego.com Subject: Re: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo Em Terça-feira, 7 de Dezembro de 2010, às 20:49:37, Gabriel M. Beddingfield escreveu: Another clue: following issue: Program received signal SIGILL, Illegal instruction. 0xa144 in __aeabi_d2lz () ^^ While this /could/ be a valid pointer, this address looks like a bogus pointer to me. I rarely see pointers this low in an application. This also suggests a buffer overrun and a corrupted stack. It probably is a valid pointer, because the debugger resolved it to __aeabi_d2lz. I looked at the ABI spec and it says d2lz is convert double to C long and it may be implemented either in software or in hardware. Looks to me like you installed a libgcc_s.so which is not compatible with your hardware. -- 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] signon-qt: ABI/ABI break
Em Quarta-feira, 8 de Dezembro de 2010, às 10:09:32, Patrick Ohly escreveu: Error now is passed by value, so use SignOn::Error, not const SignOn::Error . That's the same thing for Qt's signal-slot mechanism. It's actually recommended that you write T instead of const T and use no spaces around commas or parentheses. -- 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 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] Qt uses OpenSSL, and fails?
Em Quarta-feira, 8 de Dezembro de 2010, às 09:51:18, Patrick Ohly escreveu: A bug report about Buteo not syncing with Google via https [1] showed that Qt tries to load OpenSSL libraries, which fails because they are not installed where they are expected [2]. There is an open request to change that [3]. First, is someone working on 7813? The original issue # was marked as resolved with a comment that Fix is already available in 1.1 branch., but it doesn't say what the fix was, and Trunk obviously is still affected. Makoto, can you clarify? The Qt fix was applied as e4407012815a805d9a7d1a3beb7038a93cdd74dd but it isn't in any release yet. It's post 4.7.1. -- 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 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] Qt uses OpenSSL, and fails?
On Mi, 2010-12-08 at 10:17 +, Thiago Macieira wrote: Em Quarta-feira, 8 de Dezembro de 2010, às 09:51:18, Patrick Ohly escreveu: A bug report about Buteo not syncing with Google via https [1] showed that Qt tries to load OpenSSL libraries, which fails because they are not installed where they are expected [2]. There is an open request to change that [3]. First, is someone working on 7813? The original issue # was marked as resolved with a comment that Fix is already available in 1.1 branch., but it doesn't say what the fix was, and Trunk obviously is still affected. Makoto, can you clarify? The Qt fix was applied as e4407012815a805d9a7d1a3beb7038a93cdd74dd but it isn't in any release yet. It's post 4.7.1. Was it released in the 1.1 branch, as Makoto said? Is 4.7.1 expected to be in Trunk soon (this month)? If not, can someone backport the fix to Qt in Trunk? -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] ConnMan fails to detect wlan interface.
Connman fails to detect wifi interface, when I execute connman test list-device its only showing eth0 interface not wlan0 but my wifi working when i give static ip and edit resolv.conf. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Reducing rebuilds by patching away __DATE__ and __TIME__ usage in sources?
On Wed, Dec 8, 2010 at 12:28 PM, Carsten Munk cars...@maemo.org wrote: Hi, I've spent a little too much time watching rebuilds of the basesystem lately due to the ARM hardfp work. So, a bit of background: * OBS uses the build-compare tool in order to tell if there is a difference between the newly built package and the build results in previous run * If the package is 'new', all packages that depend on it, will rebuild as well. * If not, don't signal a rebuild One common thing is that many programs/libs gratuitously include the C macros __DATE__ and/or __TIME__ in their source codes, causing every rebuild of theirs to be different, but only in those areas. This causes unneeded rebuilds. And we already have an indication of the build time of a package due to the RPM database on a system. If the scanning is being done on binaries AFTER they have been rebuilt isn't that a bit fruitless ie, build this package to compare it with the last one to see if it needs rebuilding? surely If the source is the same it should not be built in the first place? My proposal: * Identify packages using OBS build logs that include __DATE__ or __TIME__ (should be possible to grep for the usual patterns of __DATE__ and __TIME__) * Patch those usages away in spec file. or * Make build-compare able to notice a build change is 'just' because of __DATE__ and __TIME__ and otherwise similar. What do you think? BR 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] ConnMan fails to detect wlan interface.
On Wednesday, December 08, 2010 07:01:27 am Varun wrote: Connman fails to detect wifi interface, when I execute connman test list-device its only showing eth0 interface not wlan0 but my wifi working when i give static ip and edit resolv.conf. What wifi card do you have? (`lspci -nn`) -gabriel ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Qt uses OpenSSL, and fails?
Hi, Patrick Ohly wrote: Second, as mentioned in # and elsewhere [4], there is a license conflict between OpenSSL and GPL. Does opening OpenSSL via dlopen() at runtime really work around this conflict? I'm not a lawyer, but given that the way how linking is achieved is typically not specified in detail in licenses, I doubt that using dlopen() instead of ld.so really works around the license issue. I am definitely not a lawyer, but I have previously worked for a company who routinely included functionality at runtime if we detected the presence of certain GPL incompatible shared objects. We did receive legal advice that this was not incompatible with the GPL, since we (the application authors) were not shipping the non-GPL GPL code together. Presumably the same applies to Qt, unless Qt unconditionally depends on OpenSSL. Some related data points: Fluendo also heavily researched this question (for obvious reasons) and have a question about it in their licensing FAQ: http://www.gstreamer.net/data/doc/gstreamer/head/faq/html/chapter-legal.html#legal-gpl-program Jacob Kaplan once wrote a series of unanswered GPL related questions exploring the grey areas around the GPL - this question is related to his questions 1 and 4: http://jacobian.org/writing/gpl-questions/ The question came up on Stack Overflow a while back too: http://stackoverflow.com/questions/2069200/designing-a-gpl-library-with-weak-dependencies-on-proprietary-libs-best-approach Hope all this helps! 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
[MeeGo-dev] Extending Qt Mobility's encoder support
Hi, The Gstreamer plugin in Qt Mobility contains a list of hard coded audio encoders and another for video encoders. Audio: http://qt.gitorious.org/qt-mobility/qt-mobility/blobs/master/plugins/multimedia/gstreamer/mediacapture/qgstreameraudioencode.cpp#line58 Video: http://qt.gitorious.org/qt-mobility/qt-mobility/blobs/master/plugins/multimedia/gstreamer/mediacapture/qgstreamervideoencode.cpp#line54 What are the options for extending the lists with support for other encoders and profiles, e.g. AAC, HEAACv1 v2, H.263, base/main/high profiles etc? I suppose the most obvious option is to patch the classes by adding the new components in the same way they are added now. In case the gst components are not available in the platform, the factory function will fail and the encoder will not be exposed up to QMediaRecorder. But is there a more dynamic way of doing it in the current design? If not, is the current design going to stay or will the discovery of encoders be done differently? I suppose I should take the last question to the qt-mobility mailing list, unless some of the Mobility devs are listening in on this list as well. BR Fredrik ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] From where video player takes the files?
Hi, Im compiling and installing meego-handset-video-0.2.3 code by using qmake,make,sudo make install. After that if I launch from the 'startmeego' ,Im unable to view the video files in the meegovideo playlist. Im using the same existing videos(big buck kitten ) from the /home/meego/videos folder only. Can anybody let me know from where video player takes the files? If it is taking from X folder only ,then why my compiled meegovideo is unable to take from that X folder,as I haven't modified the SDK files. rgds, Ramesh ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Qt uses OpenSSL, and fails?
On Wednesday 08 December 2010 15:39:26 ext Dave Neary, you wrote: Patrick Ohly wrote: Second, as mentioned in # and elsewhere [4], there is a license conflict between OpenSSL and GPL. Does opening OpenSSL via dlopen() at runtime really work around this conflict? I'm not a lawyer, but given that the way how linking is achieved is typically not specified in detail in licenses, I doubt that using dlopen() instead of ld.so really works around the license issue. I am definitely not a lawyer, but I have previously worked for a company who routinely included functionality at runtime if we detected the presence of certain GPL incompatible shared objects. We did receive legal advice that this was not incompatible with the GPL, since we (the application authors) were not shipping the non-GPL GPL code together. Neither am I, but I doubt that way works if a MeeGo vendor ships both (L)GPL'd Qt and LGPLv2-incompatible OpenSSL on its device. There are other ways out though: - claim that OpenSSL is a component of the operating system, hence needs not be (L)GPL'd. - use GnuTLS or NSS instead of OpenSSL, - use (L)GPL version 3, which I think is on-purpose compatible with OpenSSL- style licenses (obviously not an option for MeeGo, just for completeness). -- Rémi Denis-Courmont Nokia Devices RD, Maemo Software, Helsinki ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Qt uses OpenSSL, and fails?
On 12/8/2010 8:44 AM, Rémi Denis-Courmont wrote: - use GnuTLS or NSS instead of OpenSSL, we should be using NSS anyway wherever possible, not just for the licensing side, but also because openssl has a history of ABI mess. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Qt uses OpenSSL, and fails?
On 12/8/2010 3:00 AM, fathi.bou...@nokia.com wrote: Hi, The fix is in MeeGo 1.1 but still not in Trunk. how on earth did that happen??? things are not allowed to go into 1.1 updates until the fix is in Trunk! ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Qt menus not showing up and QDesktopServices::openUrl() not working?
Hi, Hope someone can help me here, menu options are not visible within an application, this is what we are doing: QMenu* menu = new QMenu(this); m_clearAllAction = new QAction(tr(Clear all history), this); connect(m_clearAllAction,SIGNAL(triggered()), this, SLOT(clearSearchHistory()) ); menu-addAction(m_clearAllAction); menu-addAction(tr(About), this, SLOT(about())); m_clearAllAction-setEnabled(false); QAction* myMenuKey = new QAction(tr(Options), this); myMenuKey-setSoftKeyRole(QAction::PositiveSoftKey); myMenuKey-setMenu(menu); addAction(myMenuKey ); QAction* exitAction = new QAction(tr(Exit), this); exitAction-setSoftKeyRole(QAction::NegativeSoftKey); addAction(exitAction ); connect(exitAction, SIGNAL(triggered()), qApp, SLOT(quit())); Also, we are not able to launch the default browser from application using QDesktopServices::openUrl() (using MeeGo SDK), any ideas? Thanks Costas - Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 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
Re: [MeeGo-dev] Qt menus not showing up and QDesktopServices::openUrl() not working?
On 12/08/2010 11:01 AM, Stylianou, Costas wrote: Hi, ... Also, we are not able to launch the default browser from application using QDesktopServices::openUrl() (using MeeGo SDK), any ideas? The platform may not have any protocol handlers registered for http:. Internally, QDesktopServices forks xdg-open, passing it the Url. xdg-open then uses the gconf key matching the protocol name under /desktop/gnome/url-handlers. The value for 'command' is then launched, substituting the full Url for %s. You can use the gconf editor to see if a gconf key is configured for the protocol. Please file a bug on bugs.meego.com with what you discover. Thanks, James ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Qt uses OpenSSL, and fails?
Em Quarta-feira, 8 de Dezembro de 2010, às 08:49:30, Arjan van de Ven escreveu: On 12/8/2010 8:44 AM, Rémi Denis-Courmont wrote: - use GnuTLS or NSS instead of OpenSSL, we should be using NSS anyway wherever possible, not just for the licensing side, but also because openssl has a history of ABI mess. Which should hopefully be a thing of the past now that OpenSSL has reached version 1.0. NSS is an alternative, but I think our legal department ruled out any Qt-NSS code a while ago. I remember this because when the LSB wanted to standardise on NSS, we reported we could never use it. I don't know if the circumstances are still the same. -- 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 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
[MeeGo-dev] Activate GPS device on AAVA
Hey, I'm wondering if there's a way to activate the internal GPS on the AAVA device. I haven't find anything in the UI to do this for me yet... Thanks, Chris ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] From where video player takes the files?
Hi, I don't know what meegovideo in concrete is using, but it should retrieve the video files querying tracker. Run tracker-sparql -v .it should list all the videos recognized by tracker. If the list is ok, it is a bug in the application querying tracker. If it doesn't work check the error messages (if any) and check the tracker configuration under ~/.config/tracker/miner-fs.cfg There you specify what directories should be monitored. Regards, Ivan On Wed, Dec 8, 2010 at 10:39 AM, rams k krkram...@gmail.com wrote: Hi, Im compiling and installing meego-handset-video-0.2.3 code by using qmake,make,sudo make install. After that if I launch from the 'startmeego' ,Im unable to view the video files in the meegovideo playlist. Im using the same existing videos(big buck kitten ) from the /home/meego/videos folder only. Can anybody let me know from where video player takes the files? If it is taking from X folder only ,then why my compiled meegovideo is unable to take from that X folder,as I haven't modified the SDK files. rgds, Ramesh ___ 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] CFP - FOSDEM embedded devroom
Hi all, I'm slightly involved in the FOSDEM embedded devroom this year again, and I'd love to see some MeeGo content there. The devroom is generally pretty tech oriented - focussed on hardware, platforms or domain-specific stuff, so it'd be a good opportunity to present some of the more interesting aspects of MeeGo. Please find below the Call for Participation - we will be finalising the line-up quite late, but we can try to let people know earlier if they need approval to attend. Cheers, Dave. == FOSDEM embedded and mobile devroom CALL FOR PROPOSALS == FOSDEM will be held the February 5 and 6, 2011 in Brussels, Belgium. For the seventh time, FOSDEM will also feature an embedded and mobile room. We are looking for people who would like to do a presentation about a project in the realm of embedded or mobile that has some bearing on Free Software or Open Source. Some example projects are Arduino, MeeGo, Yocto, Beagleboard and its decendants, Openembedded, Android, Qt, OpenWrt, NetBSD... We are looking for short tutorials, feature presentations, project overviews, talks about achievements or failures, hardware and hardware hacking, real life deployments, and more... All submissions will be reviewed by our panel. Good proposals consist of an abstract of the talk and a short speaker biography. They should be submitted to fosdem.embed...@gmail.com. before January 5, 2011. We will confirm to the speakers no later than January 10, 2011. The review panel consists of: Philippe De Swert, Nokia Peter De Schrijver, Nokia Klaas Van Gend, MontaVista Software Dave Neary, Neary Consulting Michael Opdenacker, Free Electrons and Linaro´ -- 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] From where video player takes the files?
Meegovideo retrieve the video files by querying the tracker. But there is bug in old version: http://bugs.meego.com/show_bug.cgi?id=10287blocked::http://bugs.meego.com/show_bug.cgi?id=10287. Update your tracker and tracker-utils. Try tracker-search -v It should list the video files. If it is, then try to run meegovideo. -Zhenqiang From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Ivan Frade Sent: 2010年12月9日 5:18 To: rams k Cc: meego-dev; meego-...@meego.com Subject: Re: [MeeGo-dev] From where video player takes the files? Hi, I don't know what meegovideo in concrete is using, but it should retrieve the video files querying tracker. Run tracker-sparql -v .it should list all the videos recognized by tracker. If the list is ok, it is a bug in the application querying tracker. If it doesn't work check the error messages (if any) and check the tracker configuration under ~/.config/tracker/miner-fs.cfg There you specify what directories should be monitored. Regards, Ivan On Wed, Dec 8, 2010 at 10:39 AM, rams k krkram...@gmail.commailto:krkram...@gmail.com wrote: Hi, Im compiling and installing meego-handset-video-0.2.3 code by using qmake,make,sudo make install. After that if I launch from the 'startmeego' ,Im unable to view the video files in the meegovideo playlist. Im using the same existing videos(big buck kitten ) from the /home/meego/videos folder only. Can anybody let me know from where video player takes the files? If it is taking from X folder only ,then why my compiled meegovideo is unable to take from that X folder,as I haven't modified the SDK files. rgds, Ramesh ___ MeeGo-dev mailing list MeeGo-dev@meego.commailto: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] Extending Qt Mobility's encoder support
Hi Fredrik, On Thu, 9 Dec 2010 12:02:21 am ext Fredrik HENRICSSON wrote: Hi, The Gstreamer plugin in Qt Mobility contains a list of hard coded audio encoders and another for video encoders. Audio: http://qt.gitorious.org/qt-mobility/qt-mobility/blobs/master/plugins/multimedia/gstreamer/mediacapture/qgstreameraudioencode.cpp#line58 Video: http://qt.gitorious.org/qt-mobility/qt-mobility/blobs/master/plugins/multimedia/gstreamer/mediacapture/qgstreamervideoencode.cpp#line54 What are the options for extending the lists with support for other encoders and profiles, e.g. AAC, HEAACv1 v2, H.263, base/main/high profiles etc? I suppose the most obvious option is to patch the classes by adding the new components in the same way they are added now. In case the gst components are not available in the platform, the factory function will fail and the encoder will not be exposed up to QMediaRecorder. But is there a more dynamic way of doing it in the current design? If not, is the current design going to stay or will the discovery of encoders be done differently? I suppose I should take the last question to the qt-mobility mailing list, unless some of the Mobility devs are listening in on this list as well. This probably will be changed from hard coded settings to configuration files + dynamic discovery of additional installed codecs, but currently it's necessary to modify backend sources. The reason the configuration is hard coded - the backend does not just put the encoder element into pipeline but also performs some configuration to provide presets like api (quality parameter), which is hard to do for unknown element. When no codec is selected the backend should choose the optimal codec and settings for the current platform, application can also modify for example only the quality parameter and/or choose only the codec. If no codec is specified backend can also choose the best codec supported on the device, for example H264 encoder for lower resolutions or mpeg4 for high res video. This is hard to implement for dynamically discovered codecs. Just FYI, mediacapture part of gstreamer backend is used as a fallback when camerabin element and gstreamer photography are not available, but probably should be deprecated after camerabin gstreamer element becomes stable and widespread. Regards Dmytro. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] From where video player takes the files?
Hi, rams If you want to compile and make install, You better git clone the code from gitorious rather than get it from OBS (meego-handset-video-0.2.3 like you mentioned). Because some of the code in gitorious hasn’t been put into OBS due to our internal assignment changes. From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Chen, Zhenqiang Sent: Thursday, December 09, 2010 9:11 AM To: 'rams k' Cc: 'meego-dev'; 'meego-...@meego.com' Subject: Re: [MeeGo-dev] From where video player takes the files? Meegovideo retrieve the video files by querying the tracker. But there is bug in old version: http://bugs.meego.com/show_bug.cgi?id=10287blocked::http://bugs.meego.com/show_bug.cgi?id=10287. Update your tracker and tracker-utils. Try tracker-search -v It should list the video files. If it is, then try to run meegovideo. -Zhenqiang From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Ivan Frade Sent: 2010年12月9日 5:18 To: rams k Cc: meego-dev; meego-...@meego.com Subject: Re: [MeeGo-dev] From where video player takes the files? Hi, I don't know what meegovideo in concrete is using, but it should retrieve the video files querying tracker. Run tracker-sparql -v .it should list all the videos recognized by tracker. If the list is ok, it is a bug in the application querying tracker. If it doesn't work check the error messages (if any) and check the tracker configuration under ~/.config/tracker/miner-fs.cfg There you specify what directories should be monitored. Regards, Ivan On Wed, Dec 8, 2010 at 10:39 AM, rams k krkram...@gmail.commailto:krkram...@gmail.com wrote: Hi, Im compiling and installing meego-handset-video-0.2.3 code by using qmake,make,sudo make install. After that if I launch from the 'startmeego' ,Im unable to view the video files in the meegovideo playlist. Im using the same existing videos(big buck kitten ) from the /home/meego/videos folder only. Can anybody let me know from where video player takes the files? If it is taking from X folder only ,then why my compiled meegovideo is unable to take from that X folder,as I haven't modified the SDK files. rgds, Ramesh ___ MeeGo-dev mailing list MeeGo-dev@meego.commailto: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] about http://developer.meego.com/?
http://developer.meego.com/need login name and password...why? ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] about http://developer.meego.com/?
It was stated because it is still in beta and they'd like to keep it out of search indexing. -Original Message- Date: Wednesday, December 08, 2010 6:50:33 pm To: meego-dev@meego.com meego-dev@meego.com From: Ñk fire...@gmail.com Subject: [MeeGo-dev] about http://developer.meego.com/? Attachments: ATT1.txt (137 bytes) http://developer.meego.com/need login name and password...why? ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] What mediaplayer is used in netbook and handset?
Hi, Guys, Do you know what media players are used in netbook and handset, respectively? Thanks Harry ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo
Hi All, Thank you so much for your help and I found the root cause of this issue on my board, fennec generates an instruction that our processor cannot deal with which is 'vmov d16, r0, r1'. It uses the higher 16x64 extension registers which does not have in our processor. I can run this app now, but all the pages I opened were blank and cannot display anything, could you give me some suggestions? I suppose maybe some configuration files are not correct. B.R Paul -Original Message- From: Paul Li Sent: 2010年12月8日 9:43 To: 'imdat.so...@nokia.com'; auke-jan.h@intel.com Cc: meego-dev@meego.com; Lea Li Subject: RE: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo Hi Imdat, Thank you for your reply and I will check if this is the root cause. B.R Paul -Original Message- From: imdat.so...@nokia.com [mailto:imdat.so...@nokia.com] Sent: 2010年12月8日 4:48 To: auke-jan.h@intel.com Cc: Paul Li; meego-dev@meego.com Subject: Re: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo On Dec 7, 2010, at 15:38 , ext Auke Kok wrote: On 12/07/10 01:25, Paul Li wrote: Hi All, I met an issue with fennec on MeeGo, I recompiled this app with ‘-march=armv7-a -mtune=cortex-a8 -mlittle-endian -mfpu=vfpv3-d16 -mfloat-abi=softfp’ and ‘-march=armv7-a -mtune=cortex-a8 -mlittle-endian -mfpu=vfpv3-d16 -mfloat-abi=soft’. Both of them met the following issue: Program received signal SIGILL, Illegal instruction. 0xa144 in __aeabi_d2lz () Could anyone give me some suggestions? Thank you. :) you broke it. illegal instruction means that you instructed the compiler to generate processor instructions that are invalid for your processor type. If the app was running (i.e. you didn't get that when you started), then it can also mean that your stack was corrupted, resulting in an illegal instruction on the stack. Check whether you did anything on your stack that might have negative impact on stack consistency. Imdat ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] about http://developer.meego.com/?
On 12/08/2010 07:50 PM, 金鑫 wrote: http://developer.meego.com/need login name and password...why? ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev It's still in beta. The username is meego and the password is password iirc. It will go away (the username and password) once it's ready for prime time I believe. Jeremy ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo
the root cause of this issue on my board, fennec generates an instruction that our processor cannot deal with which is 'vmov d16, r0, r1'. It uses the higher 16x64 extension registers which does not have in our processor. So you should definitely remove mtune=cortex-a8 for your all building, not just for this app. Otherwise, you don't know when you would trigger this similar issue again. I can run this app now, but all the pages I opened were blank and cannot display anything, could you give me some suggestions? Are you talking about one feature bug? It did not relate with above issue. -Original Message- From: Paul Li [mailto:e...@marvell.com] Sent: Thursday, December 09, 2010 11:36 AM To: cars...@maemo.org; Kok, Auke-jan H; gabrb...@gmail.com; thi...@kde.org; Zhang, Austin; imdat.so...@nokia.com Cc: meego-dev@meego.com; Lea Li Subject: RE: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo Hi All, Thank you so much for your help and I found the root cause of this issue on my board, fennec generates an instruction that our processor cannot deal with which is 'vmov d16, r0, r1'. It uses the higher 16x64 extension registers which does not have in our processor. I can run this app now, but all the pages I opened were blank and cannot display anything, could you give me some suggestions? I suppose maybe some configuration files are not correct. B.R Paul -Original Message- From: Paul Li Sent: 2010年12月8日 9:43 To: 'imdat.so...@nokia.com'; auke-jan.h@intel.com Cc: meego-dev@meego.com; Lea Li Subject: RE: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo Hi Imdat, Thank you for your reply and I will check if this is the root cause. B.R Paul -Original Message- From: imdat.so...@nokia.com [mailto:imdat.so...@nokia.com] Sent: 2010年12月8日 4:48 To: auke-jan.h@intel.com Cc: Paul Li; meego-dev@meego.com Subject: Re: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo On Dec 7, 2010, at 15:38 , ext Auke Kok wrote: On 12/07/10 01:25, Paul Li wrote: Hi All, I met an issue with fennec on MeeGo, I recompiled this app with ‘-march=armv7-a -mtune=cortex-a8 -mlittle-endian -mfpu=vfpv3-d16 -mfloat-abi=softfp’ and ‘-march=armv7-a -mtune=cortex-a8 -mlittle-endian -mfpu=vfpv3-d16 -mfloat-abi=soft’. Both of them met the following issue: Program received signal SIGILL, Illegal instruction. 0xa144 in __aeabi_d2lz () Could anyone give me some suggestions? Thank you. :) you broke it. illegal instruction means that you instructed the compiler to generate processor instructions that are invalid for your processor type. If the app was running (i.e. you didn't get that when you started), then it can also mean that your stack was corrupted, resulting in an illegal instruction on the stack. Check whether you did anything on your stack that might have negative impact on stack consistency. Imdat ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo
Hi Austin, Yes, on my board this is another issue. Could you give me some suggestions? Thank you so much.:) B.R Paul -Original Message- From: Zhang, Austin [mailto:austin.zh...@intel.com] Sent: 2010年12月9日 11:56 To: Paul Li; cars...@maemo.org; Kok, Auke-jan H; gabrb...@gmail.com; thi...@kde.org; imdat.so...@nokia.com Cc: meego-dev@meego.com; Lea Li Subject: RE: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo the root cause of this issue on my board, fennec generates an instruction that our processor cannot deal with which is 'vmov d16, r0, r1'. It uses the higher 16x64 extension registers which does not have in our processor. So you should definitely remove mtune=cortex-a8 for your all building, not just for this app. Otherwise, you don't know when you would trigger this similar issue again. I can run this app now, but all the pages I opened were blank and cannot display anything, could you give me some suggestions? Are you talking about one feature bug? It did not relate with above issue. -Original Message- From: Paul Li [mailto:e...@marvell.com] Sent: Thursday, December 09, 2010 11:36 AM To: cars...@maemo.org; Kok, Auke-jan H; gabrb...@gmail.com; thi...@kde.org; Zhang, Austin; imdat.so...@nokia.com Cc: meego-dev@meego.com; Lea Li Subject: RE: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo Hi All, Thank you so much for your help and I found the root cause of this issue on my board, fennec generates an instruction that our processor cannot deal with which is 'vmov d16, r0, r1'. It uses the higher 16x64 extension registers which does not have in our processor. I can run this app now, but all the pages I opened were blank and cannot display anything, could you give me some suggestions? I suppose maybe some configuration files are not correct. B.R Paul -Original Message- From: Paul Li Sent: 2010年12月8日 9:43 To: 'imdat.so...@nokia.com'; auke-jan.h@intel.com Cc: meego-dev@meego.com; Lea Li Subject: RE: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo Hi Imdat, Thank you for your reply and I will check if this is the root cause. B.R Paul -Original Message- From: imdat.so...@nokia.com [mailto:imdat.so...@nokia.com] Sent: 2010年12月8日 4:48 To: auke-jan.h@intel.com Cc: Paul Li; meego-dev@meego.com Subject: Re: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo On Dec 7, 2010, at 15:38 , ext Auke Kok wrote: On 12/07/10 01:25, Paul Li wrote: Hi All, I met an issue with fennec on MeeGo, I recompiled this app with ‘-march=armv7-a -mtune=cortex-a8 -mlittle-endian -mfpu=vfpv3-d16 -mfloat-abi=softfp’ and ‘-march=armv7-a -mtune=cortex-a8 -mlittle-endian -mfpu=vfpv3-d16 -mfloat-abi=soft’. Both of them met the following issue: Program received signal SIGILL, Illegal instruction. 0xa144 in __aeabi_d2lz () Could anyone give me some suggestions? Thank you. :) you broke it. illegal instruction means that you instructed the compiler to generate processor instructions that are invalid for your processor type. If the app was running (i.e. you didn't get that when you started), then it can also mean that your stack was corrupted, resulting in an illegal instruction on the stack. Check whether you did anything on your stack that might have negative impact on stack consistency. Imdat ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo
Roger (in CC list) should be able to give some suggestions on this. -Original Message- From: Paul Li [mailto:e...@marvell.com] Sent: Thursday, December 09, 2010 11:59 AM To: Zhang, Austin; cars...@maemo.org; Kok, Auke-jan H; gabrb...@gmail.com; thi...@kde.org; imdat.so...@nokia.com Cc: meego-dev@meego.com; Lea Li Subject: RE: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo Hi Austin, Yes, on my board this is another issue. Could you give me some suggestions? Thank you so much.:) B.R Paul -Original Message- From: Zhang, Austin [mailto:austin.zh...@intel.com] Sent: 2010年12月9日 11:56 To: Paul Li; cars...@maemo.org; Kok, Auke-jan H; gabrb...@gmail.com; thi...@kde.org; imdat.so...@nokia.com Cc: meego-dev@meego.com; Lea Li Subject: RE: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo the root cause of this issue on my board, fennec generates an instruction that our processor cannot deal with which is 'vmov d16, r0, r1'. It uses the higher 16x64 extension registers which does not have in our processor. So you should definitely remove mtune=cortex-a8 for your all building, not just for this app. Otherwise, you don't know when you would trigger this similar issue again. I can run this app now, but all the pages I opened were blank and cannot display anything, could you give me some suggestions? Are you talking about one feature bug? It did not relate with above issue. -Original Message- From: Paul Li [mailto:e...@marvell.com] Sent: Thursday, December 09, 2010 11:36 AM To: cars...@maemo.org; Kok, Auke-jan H; gabrb...@gmail.com; thi...@kde.org; Zhang, Austin; imdat.so...@nokia.com Cc: meego-dev@meego.com; Lea Li Subject: RE: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo Hi All, Thank you so much for your help and I found the root cause of this issue on my board, fennec generates an instruction that our processor cannot deal with which is 'vmov d16, r0, r1'. It uses the higher 16x64 extension registers which does not have in our processor. I can run this app now, but all the pages I opened were blank and cannot display anything, could you give me some suggestions? I suppose maybe some configuration files are not correct. B.R Paul -Original Message- From: Paul Li Sent: 2010年12月8日 9:43 To: 'imdat.so...@nokia.com'; auke-jan.h@intel.com Cc: meego-dev@meego.com; Lea Li Subject: RE: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo Hi Imdat, Thank you for your reply and I will check if this is the root cause. B.R Paul -Original Message- From: imdat.so...@nokia.com [mailto:imdat.so...@nokia.com] Sent: 2010年12月8日 4:48 To: auke-jan.h@intel.com Cc: Paul Li; meego-dev@meego.com Subject: Re: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo On Dec 7, 2010, at 15:38 , ext Auke Kok wrote: On 12/07/10 01:25, Paul Li wrote: Hi All, I met an issue with fennec on MeeGo, I recompiled this app with ‘-march=armv7-a -mtune=cortex-a8 -mlittle-endian -mfpu=vfpv3-d16 -mfloat-abi=softfp’ and ‘-march=armv7-a -mtune=cortex-a8 -mlittle-endian -mfpu=vfpv3-d16 -mfloat-abi=soft’. Both of them met the following issue: Program received signal SIGILL, Illegal instruction. 0xa144 in __aeabi_d2lz () Could anyone give me some suggestions? Thank you. :) you broke it. illegal instruction means that you instructed the compiler to generate processor instructions that are invalid for your processor type. If the app was running (i.e. you didn't get that when you started), then it can also mean that your stack was corrupted, resulting in an illegal instruction on the stack. Check whether you did anything on your stack that might have negative impact on stack consistency. Imdat ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo
Hi Roger and all, I can start fennec on my board, but all the pages I opened were blank and cannot display anything, could you give me some suggestions? I suppose maybe some configuration files are not correct. Thank you. B.R Paul Li -Original Message- From: Zhang, Austin [mailto:austin.zh...@intel.com] Sent: 2010年12月9日 12:04 To: Paul Li; cars...@maemo.org; Kok, Auke-jan H; gabrb...@gmail.com; thi...@kde.org; imdat.so...@nokia.com Cc: meego-dev@meego.com; Lea Li; Wang, Roger Subject: RE: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo Roger (in CC list) should be able to give some suggestions on this. -Original Message- From: Paul Li [mailto:e...@marvell.com] Sent: Thursday, December 09, 2010 11:59 AM To: Zhang, Austin; cars...@maemo.org; Kok, Auke-jan H; gabrb...@gmail.com; thi...@kde.org; imdat.so...@nokia.com Cc: meego-dev@meego.com; Lea Li Subject: RE: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo Hi Austin, Yes, on my board this is another issue. Could you give me some suggestions? Thank you so much.:) B.R Paul -Original Message- From: Zhang, Austin [mailto:austin.zh...@intel.com] Sent: 2010年12月9日 11:56 To: Paul Li; cars...@maemo.org; Kok, Auke-jan H; gabrb...@gmail.com; thi...@kde.org; imdat.so...@nokia.com Cc: meego-dev@meego.com; Lea Li Subject: RE: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo the root cause of this issue on my board, fennec generates an instruction that our processor cannot deal with which is 'vmov d16, r0, r1'. It uses the higher 16x64 extension registers which does not have in our processor. So you should definitely remove mtune=cortex-a8 for your all building, not just for this app. Otherwise, you don't know when you would trigger this similar issue again. I can run this app now, but all the pages I opened were blank and cannot display anything, could you give me some suggestions? Are you talking about one feature bug? It did not relate with above issue. -Original Message- From: Paul Li [mailto:e...@marvell.com] Sent: Thursday, December 09, 2010 11:36 AM To: cars...@maemo.org; Kok, Auke-jan H; gabrb...@gmail.com; thi...@kde.org; Zhang, Austin; imdat.so...@nokia.com Cc: meego-dev@meego.com; Lea Li Subject: RE: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo Hi All, Thank you so much for your help and I found the root cause of this issue on my board, fennec generates an instruction that our processor cannot deal with which is 'vmov d16, r0, r1'. It uses the higher 16x64 extension registers which does not have in our processor. I can run this app now, but all the pages I opened were blank and cannot display anything, could you give me some suggestions? I suppose maybe some configuration files are not correct. B.R Paul -Original Message- From: Paul Li Sent: 2010年12月8日 9:43 To: 'imdat.so...@nokia.com'; auke-jan.h@intel.com Cc: meego-dev@meego.com; Lea Li Subject: RE: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo Hi Imdat, Thank you for your reply and I will check if this is the root cause. B.R Paul -Original Message- From: imdat.so...@nokia.com [mailto:imdat.so...@nokia.com] Sent: 2010年12月8日 4:48 To: auke-jan.h@intel.com Cc: Paul Li; meego-dev@meego.com Subject: Re: [MeeGo-dev] fennec(Illegal instruction) issue on MeeGo On Dec 7, 2010, at 15:38 , ext Auke Kok wrote: On 12/07/10 01:25, Paul Li wrote: Hi All, I met an issue with fennec on MeeGo, I recompiled this app with ‘-march=armv7-a -mtune=cortex-a8 -mlittle-endian -mfpu=vfpv3-d16 -mfloat-abi=softfp’ and ‘-march=armv7-a -mtune=cortex-a8 -mlittle-endian -mfpu=vfpv3-d16 -mfloat-abi=soft’. Both of them met the following issue: Program received signal SIGILL, Illegal instruction. 0xa144 in __aeabi_d2lz () Could anyone give me some suggestions? Thank you. :) you broke it. illegal instruction means that you instructed the compiler to generate processor instructions that are invalid for your processor type. If the app was running (i.e. you didn't get that when you started), then it can also mean that your stack was corrupted, resulting in an illegal instruction on the stack. Check whether you did anything on your stack that might have negative impact on stack consistency. Imdat ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] signon-qt: ABI/ABI break
On 12/08/2010 10:08 AM, ext Patrick Ohly wrote: Note that the soname of signon-qt wasn't changed, so my executable continued to run. I would have preferred to get a libsignon-qt.so.1 not found error. I was expecting this change to happen and knew what to look for, but others might spend more time debugging this... Thanks for the heads up. I should have done that, indeed. I can no longer verify it (old files gone), but it seems that the database layout in .signon also changed, which removed all of my stored credentials. Alberto, is that possible? It's not a big deal at this point, but once signon really holds end-user data, a better upgrade path would be useful. Yes. Writing queries to migrate to the new DB format seemed to be overkill now, when we are not aware of anyone using our storage in MeeGo. But this version introduces a way to track DB versions and have some code run when upgrading. So hopefully this won't happen anymore. Ciao, Alberto -- http://blog.mardy.it -- geek in un lingua international! ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Where can i find a known-good NAND image(meego_qemu_nand.img)?
Hi, I want to run meego N900 on qemu and I saw this website: http://wiki.meego.com/ARM/Meego_on_Qemu and http://forum.meego.com/showthread.php?t=787 As it mentioned, The meego SD card image for n900 (.raw) does not contain a boot loader or kernel, only the root file system so it alone is not sufficient to boot the OS. Easiest way to get the missing parts is to obtain the**nokia provided NAND image (*meego_qemu_nand*.*img*) for N900**which already contains the boot loader and all the other necessary bits and then just use qflasher to overwrite the kernel area in the NAND image with qflasher with the command line you have been using. I recognize this is a bit wasteful as most of the NAND image is not used in this scenario during emulation because most of the NAND image is reserved for the root file system which in our use case is not used since the root file system is located on SD card rather than NAND. The wiki page said http://tablets-dev.nokia.com/meego-codedrop.php can find the NAND image, but it didn't have.So, where can i get the image? BR chen rui ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
