[MeeGo-dev] unblocking China distribution for VoiceToGoog -- will removing 'YouTube Search Selection(s)' function pass validation?
For VoiceToGoog ( http://store.nokia.com/content/195998
http://code.google.com/p/voicetogoog/ ) for the Nokia N9 (and Linux/MeeGo
etc)... I'm trying to fix the following issue:
// By Ben_CN (NS-QA) (Nov 7th 2011 06:45:22 UTC)
// Content failed in China because it contains a few options which China
user can't access, such as "Youtube".
What is a correct and portable way of fixing such internationalization,
portability and regional issues?
I've currently implemented this fix, very simply, by disabling access to
the "YouTube Search Selection(s)" function if the locale is set to 'zh-CN'.
Is the code below sufficient to allow bugfix update VoiceToGoog 0.2.1
(soon to be submitted) to be distributed in China? Other than YouTube, what
other external functions of VoiceToGoog might be blocked in China? And what
might be a suggested equivalent alternative for blocked sites?
The VoiceToGoog "drive" "mail" and "contact" menu options invoke the
platform navigation, mail, and contacts programs per platform handlers (
http://standards.freedesktop.org/desktop-entry-spec/latest/
http://harmattan-dev.nokia.com/docs/library/html/qt4/qdesktopservices.html).
The only remaining potential issues would be Google Web Search and
Google Map Search, which I assume are also available in China.
Here's the full list of external actions/activities that use transcribed
voice-to-text for their data, e.g. enabling voice-based web search, map,
search functionality available in VoiceToGoog:
>From source: voicetogoog/qml/voicetogoog/MenuModel.qml
..
mModel.append({ name: "Launch External Programs ", icon: "",
menuState: null,
cmd: CMD.noOpSeparator});
mModel.append({ name: "Web Search Selection(s)",icon:
"ui-images/browser_search.png",
menuState: null,
cmd: CMD.webSearchSelections});
// Fix issue from Nokia blocking release in China:
// By Ben_CN (NS-QA) (Nov 7th 2011 06:45:22 UTC)
// Content failed in China because it contains a few options which China
user can't access, such as "Youtube".
if (appLang != 'zh-CN') { //'zh-CN' <-> "Mandarin for Mainland China" ;
'appLang' set from $LANG in main.cpp
mModel.append({ name: "YouTube Search Selection(s)",icon:
"ui-images/icn_youtube_logo.png",
menuState: null,
cmd: CMD.youTubeSearchSelections});
}
mModel.append({ name: "Google Map Selection(s)",icon:
"ui-images/google_maps48x48.png",
menuState: null,
cmd: CMD.mapSearchSelections});
mModel.append({ name: "Drive to Selection Route",icon:
"ui-images/redhat-starthere.png",
menuState: null,
cmd: CMD.driveToSelectionRoute});
mModel.append({ name: "Drive to Selection Position",icon:
"ui-images/navigate.png",
menuState: null,
cmd: CMD.driveToSelectionPosition});
mModel.append({ name: "Contact/Call/SMS Selection", icon:
"ui-images/phone.png",
menuState: null,
cmd: CMD.callToSelection});
mModel.append({ name: "Mail Selection(s) Contents",icon:
"ui-images/kontact_mail.png", //was: meego-app-email.png
menuState: null,
cmd: CMD.mailSelectionsContents});
.
-- Niels
http://nielsmayer.com
PS: I believe my latest version of VoiceToGoog will be quite useful for
handset language entry in Chinese speaking regions (as well as Turkey,
Russia, etc) where language entry on a mobile keyboard might be
challenging...
* VoiceToGoog 0.2.0: Second release to
http://store.nokia.com/content/195998 ( see also
http://code.google.com/p/voicetogoog/ ).
* Adds language selection menu/button/icon with flag and language-code
display, showing current recognition language and clarifying which language
is recognized by default at application startup based on user's locale.
* Locales not matching existing voice recognition languages default to
British English [en-GB] with the language selection button showing a UK
flag to indicate default input language to be used.
* Switch language locales on-the-fly via GUI for voice-to-text languages
British English [en-GB], Amercian English [en-US], Mandarin Chinese
[zh-guoyu,zh-CN], Japanese [ja], French [fr], Italian [it], German [de].
Spanish [es], Korean [ko].
* New voice-to-text support and language switching for Australian English
[en-AU], Indian English [en-IN], New Zealand English [en-NZ], South African
English [en-ZA], Latin American Spanish [es-419], Indonesian [ind],
Malaysian [zsm], Mandarin for Taiwan [zh-TW], Turkish [tr], Russian [ru],
Czech [cs], Polish [pl], Brazilian Portuguese [pt-BR], Dutch [nl],
Afrikaans [af], and Zulu [zu].
* For some new languages, Latin American Spanish [es-419], Indonesian
[ind], Malaysian [zsm], Zulu [zu], text-to-speech output doesn't work;
voice-recogniztion language for English dialects doesn't produce the same
accent on text-to-spee
Re: [MeeGo-dev] Regarding "Qt with HTML5 layer" from MeeGo Smart TV WG Meeting Minutes for 9/20/2011
On Mon, Oct 3, 2011 at 12:01 PM, wrote: > Here is the whitepaper: > http://qt.nokia.com/files/pdf/whitepaper-qt-hybrid-server-driven-ui/at_download/file Dilip -- Thanks for the response. I guess I've already read that paper almost a year ago... :-) -rw-r--r-- 1 npm npm 196168 2010-11-04 23:14 /home/npm/Download/Qt_ServerDrivenUIHybrid_Whitepaper.pdf > The critical, and missing, context here is that Qt WebKit hybrid is a way to > build native apps, not apps that run in a browser. Another way to think about > it: Qt WebKit hybrid lets you build an app-specific "web browser" that is > designed to run that particular app Indeed, that is exactly what I'm beginning to explore with Qtzibit ( http://nielsmayer.com/meego/qml/qtzibit.xhtml ). Using it to display and provide faceted browsing of QML datamodels, local data, or internet data. Thus Qtzibit and "mashup" stye browser displays can be used to augment existing means of display using QML -- best of both worlds, using QML as best-tool-for-the-job when it fits, and using HTML5 and a more DOM and CSS based approach when it works best. Since qtzibit and Exhibit are based on their own JSON-based abstract datamodels, it is quite complementary to the way QML works -- they can exchange JSON data much like a webserver/browser exchange HTML. Also, the "server" in this kind of app is "virtual" in that everything runs locally, but you might want to make calls out to other webservices, or the local "virtual" server to get local application or mobility data. With qtzibit, apps that normally run on a website run locally (although the google-map-based ones require an internet connection, the timeline, timeplot, chart, visualizations don't). These can run "standalone" and the associated JavaScript is loaded in from the local filesystem, computed in QML/JavaScript/C++ or transferred from the web or local SQL datastore. Qt/QML can be used to visualize arbitrary datamodels as JSON in QML, and in-turn, this JSON can be rendered via QtWebKit in Exhibit. In many ways, it duplicates or complements the "delegate"-based rendering of datamodels in Qt/QML, but uses Web-based layouts and rendering. Also, it makes sense for there to be a QML "glue layer" between the many Qt-Mobility interfaces that one may want to access in HTML5 via javascript. Finally, it's possible that such a QML "glue layer" architecture between Qt/QtMobility and QtWebKit could also be where the extra layers of security could be placed between the free-for-all world of JavaScript in the browser (cross-site scripting and malicious advertising) and system-level functionality for which this glue layer, plus Qt/QtMobility and QML would act as "middleware." For example, one can envision a kind of self-expiring-one-time-pad-like-crypto-token build into the QML middleware layer so as to ensure that only certain apps, can access certain data for certain amounts of time, etc. Similar technique could be used to secure access to DRM-protected media streams and data, where Qt and QML encapsulate native C++ code to perform secure network access or media decryption. -- 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
[MeeGo-dev] Regarding "Qt with HTML5 layer" from MeeGo Smart TV WG Meeting Minutes for 9/20/2011
In "MeeGo Smart TV WG Meeting Minutes for 9/20/2011" I noticed:
> o Dilip Kenchammana: Qt with HTML5 layer Dilip has
> provided a white paper via e-mail. Discussion postponed to next meeting.
Is it possible to get a copy of this whitepaper? I have serious
concerns all-around over the approach being taken, and am curious how
a number of issues are being resolved. Especially w/r/t/ security, and
also because silly breakage needs to be done to very hairy browser
code in order to "poke holes" for video acceleration and/or
DRM-protection. And once that breakage has been perpetrated, a
tidal-wave of bugreports will ensue because the HTML5 standard permits
"canvas" like operations on top of the video; also dynamically
altering the video frame. An extreme example:
http://www.craftymind.com/factory/html5video/CanvasVideo.html
Especially troubling for the "Tizen" approach, are statements like:
http://lists.meego.com/pipermail/meego-tv/2011-September/000103.html
> Q: Narm, is there privacy controls to prevent rogue JavaScript from accessing
> private data.
> A: Doninique, not that he's seen. Designed for closed system.
> Access to scripts and code inside the box is limited by physical security.
.
FYI, my own "qt and html5" project: http://code.google.com/p/qtzibit/
http://nielsmayer.com/meego/qml/qtzibit.xhtml
"qtzibit: tiny programs make amazing web mashups using Simile-Widgets
Exhibit, QtWebKit and QML"
( http://nielsmayer.com/meego/qml/qtzibit_0_1_0.i586.rpm
http://nielsmayer.com/meego/qml/qtzibit_0.1.0_armel.deb )
Also, MeeGo/Qt and "TV" related:
http://nielsmayer.com/meego/qml/qmltube.xhtml
("qmltube: Port/fork of cutetube-qml for Linux, MeeGo Netbook, Tablet
and Harmattan.")
( http://nielsmayer.com/meego/qml/qmltube_1_11_2.i586.rpm
http://nielsmayer.com/meego/qml/qmltube_1.11.1_armel.deb )
PS: Coming soon to a Nokia N9 (validation-willing) near you, my new
app 'voicetogoog':
http://nielsmayer.com/voicetogoog/voicetogoog-map-view.png
http://nielsmayer.com/voicetogoog/voicetogoog-details-view.png
http://nielsmayer.com/voicetogoog/voicetogoog-menu-view.png
http://nielsmayer.com/voicetogoog/voicetogoog-recording-voice.png
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] [LAU] Fwd: Presenting VMPK for Nokia N950
Regarding http://midi-clorianos.blogspot.com/2011/08/presenting-vmpk-for-nokia-n950.html : On Sat, Aug 27, 2011 at 8:58 AM, Pedro Lopez-Cabanillas wrote: > I've released a beta of VMPK for Nokia N950 (Meego 1.2 Harmattan) containing > FluidSynth. > You can download source and binary packages from SourceForge: > > http://sourceforge.net/projects/vmpk/files/vmpkn9/ > > Please test. Your feedback will be appreciated. More info and screenshots: Just installed on "my" N950 -- this thing is AWESOME!! RESPONSIVE!! (I immediately went for fluidsynth's "Analog Drums" voice and went all autechre for a moment) MULTITOUCH!! The perfect handheld synth! Feature request: integrate http://qmidinet.sourceforge.net/qmidinet-index.html so it can be used as a remote midi controller too. Now to look at the sourcecode so i can understand how you did your integration into QML... Do you have any plans to port this to the MeeGo Netbook or Tablet? It would work well on a larger touchscreen with a faster processor too. It's quite nice to be able to have the exact same apps running on both MeeGo phones and MeeGo Netbook/Tablet (e.g. http://nielsmayer.com/meego/qml/qtzibit_0_1_0.i586.rpm vs http://nielsmayer.com/meego/qml/qtzibit_0_1_0_armel.deb or http://nielsmayer.com/meego/qml/qmltube_1_11_2.i586.rpm vs http://nielsmayer.com/meego/qml/qmltube_1.11.1_armel.deb ). -- 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] Is this a reliable way for app to know it's running on MeeGo Tablet vs. Netbook?
On Mon, Aug 29, 2011 at 9:44 AM, Kok, Auke-jan H
wrote:
> A better approach is to look at the device itself. Does it have a
> 102key keyboard? Then it's a laptop, desktop or netbook. Touch screen?
> Then it's not a netbook or at least a hybrid, and the touch model
> applies.
Hi Auke -- thanks for the reply.
The issue is that this suggestion doesn't tell the appropriate
information, after all, this is about sofware, not hardware. For
example, I could be running the tablet UX on the Lenovo s10-3t instead
of Netbook UX. If that was the case, I'd want the nonstandard
"tablet" way of handling, framing /decorating, and window-managing
applications; if the application finds itself on a desktop or netbook
UX, I'd use code that attempted
http://standards.freedesktop.org/wm-spec/latest/ compliance.
Is there some "portable" Qt or QML code to do this? or a
meego-compatible equivalent of http://apidocs.meego.com/1.2/qmsystem/
-- which is present on Nokia's Harmattan but appears missing from
MeeGo. Otherwise using
http://apidocs.meego.com/1.2/qmsystem/classMeeGo_1_1QmKeys.html seems
like a potential API for your suggestion.
> Using random files on disk sounds bad too, why not just parse
> /etc/meego-release?
I wanted to do that, but unfortunately, it's the same for both netbook
and tablet:
meegotab-2-~> cat /etc/meego-release #Tablet-UX:
MeeGo release 1.2.0.90 (MeeGo)
meegolem-8-~> cat /etc/meego-release #Netbook UX:
MeeGo release 1.2.0.90 (MeeGo)
> Ultimately, if you need 100% coverage, you need to read /etc/boardname
> and maintain a mapping table of all 'boards' out there.
Unfortunately, that would just tell me hardware. So it wouldn't solve
the case of running tablet-UX on the Lenovo s10-3t or other hybrid
netbook/touchscreen.
meegotab-3-~> cat /etc/boardname
10-pegatron
meegolem-9-~> cat /etc/boardname
ia32_lenovo_caucasus2_rev_1_0_
> This is a very debatable topic. Especially using preprocessor symbols
> might not be the right thing, it's quite likely that other people will
> just turn those on in order to make a piece of software work on
> another platform
I didn't mention that some of the preprocessor symbols are generated
by qmake and passed on during compilation. For example:
http://ytd-meego.googlecode.com/svn/trunk/playground/qmltube/qmltube.pro
## NPM workaround to missing define(MEEGO_EDITION_HARMATTAN) suggested by
##
http://wiki.meego.com/index.php?title=Porting_Fremantle_Applications_to_Harmattan&oldid=44545#Harmattan_scope
exists($$QMAKE_INCDIR_QT"/../qmsystem2/qmkeys.h"):!contains(MEEGO_EDITION,harmattan):
{
MEEGO_VERSION_MAJOR = 1
MEEGO_VERSION_MINOR = 2
MEEGO_VERSION_PATCH = 0
MEEGO_EDITION = harmattan
DEFINES += MEEGO_EDITION_HARMATTAN
## Other harmattan-specific things:
## Add qmsystem2 http://apidocs.meego.com/1.2/qmsystem/main.html
## for MeeGo::QmDisplayState()::setBlankingPause(), etc.
CONFIG += qmsystem2 \
mobility
MOBILITY += multimedia
}
## NPM: Add libresourceqt1 to support resource policy manager and
define MEEGO_HAS_POLICY_FRAMEWORK
## (
http://www.developer.nokia.com/Community/Wiki/Harmattan:Developer_Library/Best_practices_for_application_development/Selecting_the_resource_application_class
)
## NPM: Although this is also Harmattan-specific, make it a separate
configuration option in-case
## running on MeeGo platform employing the policy framework. If the
header is absent then skip the
## extra configurations in controller.h, controller.cpp and main.cpp
exists($$QMAKE_INCDIR_QT"/../resource/qt4/policy/resource-set.h") {
DEFINES += MEEGO_HAS_POLICY_FRAMEWORK
CONFIG += link_pkgconfig
PKGCONFIG += libresourceqt1
}
...
-- 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
[MeeGo-dev] Is this a reliable way for app to know it's running on MeeGo Tablet vs. Netbook?
In order for a package to run reasonably on both netbook and tablet
UX's, is the following Qt C++ a good way of determining whether an
application is running on MeeGo Netbook or Tablet?
+#ifdef Q_WS_MAEMO_5
+isMeegoTablet = false; // NPM
+#elif defined(MEEGO_EDITION_HARMATTAN)
+isMeegoTablet = false;
+#elif defined(Q_WS_X11)
+/* NPM: package 'tablet-target-config' is in the Tablet KS
+
http://ftp-nyc.osuosl.org/pub/meego/builds/1.2.0.90/1.2.0.90.12.20110809.2/images/meego-tablet-ia32-pinetrail/meego-tablet-ia32-pinetrail-1.2.0.90.12.20110809.2.packages
+ but not in
+
http://ftp-nyc.osuosl.org/pub/meego/builds/1.2.0.90/1.2.0.90.12.20110809.2/images/meego-netbook-ia32/meego-netbook-ia32-1.2.0.90.12.20110809.2.packages
+ Package 'tablet-target-config' contains a single file
/usr/share/meegotouch/targets/tablet.conf
+ if present, then assume we're on MeeGo tablet UX.
+*/
+if (QFile::exists("/usr/share/meegotouch/targets/tablet.conf"))
+ isMeegoTablet = true;
+else
+ isMeegoTablet = false;
+#else
+isMeegoTablet = false; // NPM
+#endif
The idea is that this ultimately sets a property
'Controller.isMeegoTablet' accessible from QML so that code does
different things on difft platforms:
onButtonClicked: {
if (Controller.isMeegoTablet) {//NPM
mainWindow.fullScreen =
!(mainWindow.fullScreen);
mainWindow.pageUsingFullScreen =
!(mainWindow.pageUsingFullScreen);
}
else if (!Controller.isMaemo) {
Controller.toggleState();
}
else {
Controller.minimize();
}
Niels
http://nielsmayer.com
PS: The code works :-) And successfully invokes the tablet-UX "window
framing" versus the netbook-UX. and associated different behaviors for
the "full-screen" button on the app. For details,
" svn checkout http://ytd-meego.googlecode.com/svn/trunk/playground/qmltube/ "
" qtcreator qmltube/qmltube.pro "
___
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] RPM .spec file "%files -f" macro not working in madde-0.7.63 ?
On Thu, Aug 25, 2011 at 8:05 PM, Jian-feng Ding
wrote:
> I think you need not to doubt the "-f" syntax of spec. It works well for a
> quite long time.
> What's the content in the dynamic generated *.files file? Maybe the errors
> are from them.
Jian-Feng:
Thank you for the reply and confirmation that "-f" works. My file was
just a list of files to be included, much like I did in the first pass
when I inserted the output of "find -f" into the spec file directly.
Rather than having to update the spec file each time I add a QML file
in development, I wanted to run 'find' in an earlier spec-file stage
to get a list of all the QML files.
Do you have a pointer to a working MeeGo 1.2 spec file that uses the
"%files -f" syntax, and creates the files-list from in an earlier
stage of execution in the spec-file? Also an example file in case
there's some special tricky syntax, or documentation on that syntax?
( http://www.rpm.org/max-rpm-snapshot/s1-rpm-build-creating-spec-file.html
didn't help, though looking again, I should run the examples from
"rpmbuild -bl — Check %files list"
from http://www.rpm.org/max-rpm-snapshot/ch-rpm-b-command.html )
If "-f" is working, in the following code:
> elsif ($1 eq 'files') { readfiles ($files{$2} = [ ]); }
> elsif ($1 eq 'pre') { readlines ($pre{$2} = [ ]); }
> elsif ($1 eq 'post') { readlines ($post{$2} = [ ]); }
> elsif ($1 eq 'preun') { readlines ($preun{$2} = [ ]); }
> elsif ($1 eq 'postun') { readlines ($postun{$2} = [ ]); }
> elsif ($1 eq 'files') { readfiles ($files{$2} = [ ]);
perhaps the error message I'm getting is a bad way for the program to
tell me it couldn't find the file? Next time I'm hacking spec files,
I'll have to check the output of
"rpmbuild -bl -vv meego.spec" to see if there's something else going on.
In summary, perhaps the right question to ask is where should I be
writing the file so that files -f can access it? ? In the previous
failure output I posted, based on the file not being located as
hypothesis for failure, I attempted a number of locations:
> '%files -f /tmp/%name-qml.files'
> '%files -f %{buildroot}/qmltube-qml.files'
I also tried writing ../%name/qtc_packaging/qml.files in the master
source tree, and referencing that filename as -f parameter. The builds
are happening in a "shadow-build" environment run out of qtcreator
2.3RC0, so "../%name/qtc_packaging/qml.files" references the master
source location relative to the shadow-build directory.
Thanks.
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
[MeeGo-dev] RPM .spec file "%files -f" macro not working in madde-0.7.63 ?
http://wiki.meego.com/Packaging/Guidelines#Handling_Locale_Files
suggests a way of having a RPM .spec %files macro take a
dynamically-generated file "%{name}.lang".
%files -f %{name}.lang
This useful "-f" syntax is also suggested here:
http://www.techrepublic.com/article/making-rpms-part-4-finishing-the-spec-file/5033542
Unfortunately, whenever I use this form in MeeGo, the only output I
get is an error message "unsupported stanza format":
$ /usr/lib64/madde/linux-x86_64/bin/mad rrpmbuild -bb
/home/npm/appup/qmltube/qtc_packaging/meego.spec
'%files -f /tmp/%name-qml.files': unsupported stanza format.
$ /usr/lib64/madde/linux-x86_64/bin/mad rrpmbuild -bb
/home/npm/appup/qmltube/qtc_packaging/meego.spec
'%files -f %{buildroot}/qmltube-qml.files': unsupported stanza format.
$ /usr/lib64/madde/linux-x86_64/bin/mad rrpmbuild -bb
/home/npm/appup/qmltube/qtc_packaging/meego.spec
'%files -f /dev/null': unsupported stanza format.
Googling the source-code, I didn't see any obvious code to process "-f":
http://meego.gitorious.org/meego-developer-tools/madde/blobs/ffdd033010ed147b42e6b08cb43966499c0fbf85/src/madlib/rrpmbuild.pl
:
...
while (1) {
chomp, die "'$_': unsupported stanza format.\n"
unless /^\s*%(\w+)\s*(\S*?)\s*$/;
if ($1 eq 'package') {
push @pkgnames, $2;
readpackage ($packages{$2} = [ [ ], { } ]);
}
elsif ($1 eq 'description') { readlines ($description{$2} = [ ]); }
elsif ($1 eq 'prep') {readignore \@prep; }
elsif ($1 eq 'build') { readlines \@build; }
elsif ($1 eq 'install') { readlines \@install; }
elsif ($1 eq 'clean') { readlines \@clean; }
elsif ($1 eq 'files') { readfiles ($files{$2} = [ ]); }
elsif ($1 eq 'pre') { readlines ($pre{$2} = [ ]); }
elsif ($1 eq 'post') { readlines ($post{$2} = [ ]); }
elsif ($1 eq 'preun') { readlines ($preun{$2} = [ ]); }
elsif ($1 eq 'postun') { readlines ($postun{$2} = [ ]); }
elsif ($1 eq 'changelog') { readlines \@changelog; }
else { chomp; die "'$1': unsupported stanza macro.\n"; }
last if eof I;
};
...
I'm using Qt Creator 2.3RC and
http://download.meego.com/live/Tools:/SDK:/Host/ versions of MeeGo
SDK:
madde-0.7.63-1.1.x86_64, meego-sdk-i586-toolchain-1.1-4.1.x86_64,
meego-sdk-qt-devel-tools-4.7.2-3.1.x86_64,
meego-1.2-sdk-ia32-toolchain-1.0-6.1.x86_64,
meego-sdk-libqtwebkit4-4.7.2-3.1.x86_64, meego-sdk-ia32-5-1.1.noarch,
meego-sdk-5-1.1.noarch, meego-sdk-common-5-1.1.noarch,
meego-sdk-libqtxml4-4.7.2-3.1.x86_64,
meego-sdk-qt-qmake-4.7.2-3.1.x86_64, meego-sdk-armv7l-5-1.1.noarch
Niels
http://nielsmayer.com
PS: The compromise I came up with is to use the traditional form of
the %files macro and enumerate the directories I want to include and
use wildcards, e.g. "qml/*.qml" :
http://ytd-meego.googlecode.com/svn/trunk/playground/qmltube/qtc_packaging/meego.spec
The resulting MeeGo 1.2 RPM:
http://nielsmayer.com/meego/qml/qmltube-1.11.1-1.i586.rpm
(Harmattan: http://nielsmayer.com/meego/qml/qmltube_1.11.1_armel.deb )
However, the package that really needs "%files -f" is the .spec file
that generated this monster:
http://nielsmayer.com/meego/qml/qtzibit-0.1.0-1.i586.rpm
( http://code.google.com/p/qtzibit/
http://nielsmayer.com/meego/qml/qtzibit_0.1.0_armel.deb )
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Telepathy article in "The Architecture of Open Source Applications"
http://www.aosabook.org/en/index.html has an interesting chapter on Telepathy: http://www.aosabook.org/en/telepathy.html which provides a detailed overview of Telephathy and D-Bus. 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
[MeeGo-dev] minor adjustments needed for ExoPC crystalhd video acceleration -> xen missing from kernel-adaptation-pinetrail-devel
Following instructions at
http://wiki.meego.com/Devices/ExoPC#Crystal_HD_Video_Decoder_.28BCM70015.29
I've successfully got MeeGo 1.2.0.90 Tablet-UX on ExoPC doing
accelerated decoding of some HD video formats.
Once enabled, including the gstreamer plugin, the ExoPC's crystalhd
hardware works "transparently" (modulo bugs and taking long time to
unload/load sometimes) through the QML Video element, and thus works
in meego-app-video (success: big_buck_bunny_720p_h264.mov fails:
big_buck_bunny_1080p_surround.avi ).
http://wiki.meego.com/tubelet-and-cutetube-port , can now playback HD
video, including streaming 720p content from YouTube. (TODO: enable
1020p DL and playback in qmltube now that tablet has a chance of
working with it). Xbmc gets acceleration as well, although the
Fedora/RPMFusion version I use (the one with all the features built
in) still tends to make the machine power-off randomly
(overheating??). Fortunately, my fork of qmltube now subsumes most of
the features I'd been using in xbmc (youtube plugin) and will soon
subsume more (PBS plugin?).
http://labs.adobe.com/downloads/flashplayer11.html works with
acceleration as well, but only properly in
http://wiki.meego.com/MeeGo-Lem-Firefox4 .
Just follow advice from
http://wiki.meego.com/Devices/ExoPC#Hardware_H.264_Video_Decoding_with_Flash_Player
and enable hardware acceleration via configuration file:
...
$ cat /etc/adobe/mms.cfg
EnableLinuxHWVideoDecode=1
OverrideGPUValidation=true
...
Unfortunately, meego-app-browser's click-to-play flash continues to
cause myriad problems with actual real world sites and remains mostly
unusable: example sites that don't work http://turntable.com and
http://music.google.com. Strangely, http://www.hbogo.com which worked
in meego-app-browser prior to enabling hardware decoding, now has
stopped working. In exchange, it now works properly in Firefox4 which
is my preferred browser anyways.
In order to compile the crystalhd driver on MeeGo, I had to use
http://wiki.meego.com/MeeGo-Lem to get the xen-devel package, and
dependencies from Fedora 14. I couldn't find the missing headers in
kernel-adaptation-pinetrail-devel-2.6.38.2-8.26.i586 to prevent these
compilation errors:
.
meegotab-90-.../driver/linux> make
make -C /lib/modules/2.6.38.2-8.26-adaptation-pinetrail/build
SUBDIRS=/usr/local/src/crystalhd/driver/linux modules
make[1]: Entering directory
`/usr/src/kernels/2.6.38.2-8.26-adaptation-pinetrail'
make[1]: Warning: File
`/usr/src/kernels/2.6.38.2-8.26-adaptation-pinetrail/arch/x86/Makefile_32.cpu'
has modification time 3.5e+06 s in the future
make[2]: Warning: File `include/config/auto.conf' has modification
time 3.5e+06 s in the future
CC [M] /usr/local/src/crystalhd/driver/linux/crystalhd_lnx.o
In file included from include/linux/fb.h:408:0,
from /usr/local/src/crystalhd/driver/linux/crystalhd_lnx.h:38,
from /usr/local/src/crystalhd/driver/linux/crystalhd_lnx.c:20:
/usr/src/kernels/2.6.38.2-8.26-adaptation-pinetrail/arch/x86/include/asm/io.h:44:21:
fatal error: xen/xen.h: No such file or directory
compilation terminated.
make[2]: *** [/usr/local/src/crystalhd/driver/linux/crystalhd_lnx.o] Error 1
make[1]: *** [_module_/usr/local/src/crystalhd/driver/linux] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.38.2-8.26-adaptation-pinetrail'
make: *** [all] Error 2
.
To fix, I did "zypper in xen-devel" using MeeGo-Lem, which
transparently installed xen-libs-4.0.1-6.fc14.i686,
xen-devel-4.0.1-6.fc14.i686, xen-licenses-4.0.1-6.fc14.i686 from
Fedora 14 repos. I had to hand-edit the autoconf-generated Makefile to
pickup the missing include:
.
meegotab-5-.../driver/linux> pwd
/usr/local/src/crystalhd/driver/linux
meegotab-6-.../driver/linux> diff -c Makefile.~1~ Makefile
*** Makefile.~1~2011-06-15 23:50:11.625700663 -0700
--- Makefile2011-06-15 23:51:05.055032758 -0700
***
*** 9,14
--- 9,15
INCLUDES += -I$(src)/../../include
INCLUDES += -I$(src)/../../include/link
INCLUDES += -I$(src)/../../include/flea
+ INCLUDES += -I/usr/include
EXTRA_CFLAGS = -D__KERNEL__ -DMODULE $(INCLUDES) $(INC)
EXTRA_CFLAGS += -Wall -Wstrict-prototypes -Wno-trigraphs -Werror -O2
Is there a MeeGo-supported way of compiling this driver? Seems like a
similar problem to https://bugs.meego.com/show_bug.cgi?id=18991 ("xen
missing from kernel-adaptation-intel-automotive-devel") except that in
this case, /usr/src/kernels/2.6.38.2-8.26-adaptation-pinetrail/include/xen
is missing.
This is happening for kernel-adaptation-pinetrail-2.6.38.2-8.26.i586
and kernel-adaptation-pinetrail-devel-2.6.38.2-8.26.i586 .
Niels
http://nielsmayer.com
PS: one problem i've noticed is that I don't see the driver getting
loaded after doing /sbin/pm-suspend. lsmod(1) continues to report
"crystalhd 87942 0 "
whereas after a fresh boot, when an application like qmltube plays
back a vide
[MeeGo-dev] documentation on meego-ux-user-skel and how/when will app-up will install apps to tablet?
I just upgraded my ExoPC tablet to the latest weekly build http://mirrors1.kernel.org/meego/builds/1.2.0.90/1.2.0.90.12.20110809.2/builddata/reports/repodiff-1.2.0.90.10.20110726.2-1.2.0.90.12.20110809.2.html indicates a fix for "Bug 20935 - [REG][Mytablet] Mytablet panel failed to auto detect the appup shadow folder creation/delete" ( https://bugs.meego.com/show_bug.cgi?id=20935 ). Curious, I checked it out: meegotab-4-~> rpm -ql meego-ux-user-skel-0.0.2-1.1.noarch /etc/skel/.gnome2 /etc/skel/.gnome2/keyrings /etc/skel/.gnome2/keyrings/default /etc/skel/.gnome2/keyrings/default.keyring /etc/skel/.local/opt/com.intel.appup-tablet /etc/skel/.local/opt/com.intel.appup-tablet/featured /etc/skel/.local/opt/com.intel.appup-tablet/update meegotab-5-~> ty /etc/skel/.local/opt/com.intel.appup-tablet/featured total 0 drwxr-xr-x 1 root root 0 2011-07-27 09:10 ./ drwxr-xr-x 1 root root 28 2011-07-29 06:42 ../ meegotab-6-~> ty /etc/skel/.local/opt/com.intel.appup-tablet/update total 0 drwxr-xr-x 1 root root 0 2011-07-27 09:10 ./ drwxr-xr-x 1 root root 28 2011-07-29 06:42 ../ meegotab-7-~> ty /etc/skel/.gnome2/keyrings/default.keyring [keyring] display-name=default ctime=1242440505 mtime=1242440505 lock-on-idle=false lock-timeout=0 What's this all for, how is it used, and how are applications installed into these directories by app-up? Is this functionality being developed for some future capability or is this something that can be used now? When can we expect to see app-up as a means of application distribution on our ExoPC tablets? 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] [Meego-qa] No scrub meeting for bugs assigned to triaget...@meego.bugs
On Mon, Aug 1, 2011 at 6:38 AM, Andre Klapper wrote: > The proper fix probably would be to not allow queries embedded in MeeGo > wiki pages to list Security tickets in Bugzilla. That's not the proper fix. The proper fix is to either fix the API, or fix the security bug reporting process so that less critical information is exposed by the bugzilla API for security bugs. For example http://bugs.meego.com/buglist.cgi?quicksearch=NielsMayer&ctype=csv&columnlist=all will return a CSV of all my bugs and http://bugs.meego.com/buglist.cgi?quicksearch=NielsMayer&ctype=js&columnlist=all will return the same as JSON formatted data. Although not containing the contents of potential security bugs, the API will expose the title, reporter, assignee, status, etc. This is one of the many issues I had to deal with over a decade ago when I hacked together Issuezilla for collabnet, against my will, but it was an emergency, the pie-in-the-sky bugtracker wasn't ready, and openoffice.org needed to launch... our system was somewhat different as bugzilla ran inside sourcecast using its authentication system; as it was also designed for use in private extranets with two-factor auth and x509 personal certs, there was a much more sophisticated way of gating private from public issues in "Issuezilla". One of the examples I just got running for Qtzibit ( http://code.google.com/p/qtzibit ) is a mild modification of BugXhibit ( http://www.visophyte.org/blog/2009/05/28/bugxhibit-exhibit-on-bugzilla-results/ ) and makes use of the above API. Looks like: http://nielsmayer.com/meego/qml/bugxhibit.png http://nielsmayer.com/meego/qml/bugzhibit-timeline.png Feel free to try it yourself in your browser (or compile the app in qtcreator from qtzibit.pro)... the timeline sliders work pretty nicely on a touchscreen, although they can conflict with their flickable containers (thus the option of unchecking 'flickable' button in the examples). * svn checkout http://qtzibit.googlecode.com/svn/trunk/ qtzibit * firefox qtzibit/exhibit/src/webapp/examples/Bugxhibit/bugxhibit.html Or run it on your Nokia N950 or N9: * http://nielsmayer.com/meego/qml/qtzibit_0_0_3_armel.deb -- 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] how to get a snapshot of the app
Assuming you're looking for a screenshot (*), perhaps this will be of assistance. Taken from my MeeGo Netbook. It will snapshot the current state of the screen and (over)write it to file screenshot.png (in pwd): .. meegolem-109-~> cat bin/screenshot #!/bin/sh export DISPLAY=:0.0 gst-launch-0.10 ximagesrc num-buffers=1 ! ffmpegcolorspace ! pngenc ! filesink location=screenshot.png ls -l screenshot.png See also http://forum.meego.com/showpost.php?p=27827&postcount=3 ... the fact that this little script works on MeeGo 1.2.0.90 Netbook, MeeGo 1.2.0.90Tablet, my amazing new Harmattan N950 handset, my Fedora desktops, etc is small sign of progress amidst a sea of turmoil... Hopefully, with wayland coming, there's some reasonable replacement for the 'ximagesrc num-buffers-1' part. -- Niels http://nielsmayer.com PS: (*) alternately perhaps this is the kind of application snapshot you're looking for :-) : http://www.stanford.edu/~pgbovine/cde.html http://www.youtube.com/watch?v=6XdwHo1BWwY ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Getting MeeGo-UX&Mobility Camera Working After Upgrade (was Re: how to run meego-ux's meego-app-camera on MeeGo 1.2 Netbook?)
On Tue, Apr 5, 2011 at 4:56 PM, Rusty Lynch wrote:
> Just realized we are still using a work around in the image creation
> process. There is a bug for Qt Mobility bug for this, but I don't recall
> the number so cc'ing Iain for the answer.
I accidentally ran into this note while looking for something else,
and realized it was the re-solution of a problem that happened ever
since I upgraded my MeeGoConf ExoPC tablet to a more recent build of
MeeGo 1.2 ( 1.2.0.90/1.2.0.90.11.20110728.1 currently).
So as not to forget again, I've added it to the roster of re-fixing I
do on each update. This one gets meego-app-camera and the qtmobility
demo camera application working again, so I thought I'd share the
solution.
From my script 'post-fix' which I run after
"zypper dup --from 'MeeGo:1.2:non-oss (MeeGo_1.2)' --from
'MeeGo:1.2:oss (standard)'"
..
#!/bin/bash
sudo zypper in --force hunspell-1.2.12-1.fc14 ##
https://bugs.meego.com/show_bug.cgi?id=16879
sudo zypper in
http://download.meego.com/live/devel:/ux:/handset/Trunk_Testing/i586/meegotouch-inputmethodbridges-0.2.3-7.6.i586.rpm
## http://bugs.meego.com/show_bug.cgi?id=18619
## From http://lists.meego.com/pipermail/meego-dev/2011-April/482507.html
##
#> Just realized we are still using a work around in the image creation
#> process. There is a bug for Qt Mobility bug for this, but I don't recall
#> the number so cc'ing Iain for the answer.
#>
#> But... the gst camera bin doesn't play nicely with the Qt Mobility Video
#> widget. In the ks file we:
#> rm /usr/lib/gstreamer-0.10/libgstcamerabin.so
#>
#> ... which means on each update the file comes back (which is how i
#> remembered since i just did a massive Trunk:Testing update and the camera
#> app stopped working.)
sudo mv /usr/lib/gstreamer-0.10/libgstcamerabin.so
/usr/lib/gstreamer-0.10/libgstcamerabin.so.bak
## Incase the browser gets updated, link it back to firefox.
## where chromium-browser.sh is a simple wrapper
### #!/bin/sh
### exec firefox $*
sudo rm /usr/bin/chromium-browser
sudo ln /usr/bin/chromium-browser.sh /usr/bin/chromium-browser
echo === CHECKING FOR RPMSAVES AND RPMNEWS... ==
sudo find /etc -name '*.rpmsave' -exec ls -l {} \;
sudo find /etc -name '*.rpmnew' -exec ls -l {} \;
echo === CHECKING FOR RPMSAVES AND RPMNEWS... DONE. =
...
#!/bin/bash
sudo rm -f /etc/prelink.cache
sudo /etc/cron.daily/prelink
sudo rm -f /etc/readahead.packed
sudo /etc/init.d/sreadahead-pack start
...
-- 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] QtZibit: Simile-Widgets.org Exhibit runs local in QtWebKit rendering from QML/Json.
On Mon, Jul 11, 2011 at 4:21 PM, Niels Mayer wrote: > Introducing http://code.google.com/p/qtzibit/ Qtzibit is now checked in and working, and ready for people to try on MeeGo and other Linux platforms. The idea is to show off the power of http://simile-widgets.org/exhibit/ and provide a platform for further integration between QML and Exhibit's advanced data rendering functionality. After installation, when you run /opt/qtzibit/bin/qtzibit or click on launcher /usr/share/applications/qtzibit.desktop you'll be presented with a list of Exhibit example/demos to run, which looks like: http://nielsmayer.com/meego/qml/qtzibit-all-examples.png Clicking on one of the example titles brings up an interactive page featuring an Exhibit demo: http://nielsmayer.com/meego/qml/qtzibit-billionaires.png http://nielsmayer.com/meego/qml/qtzibit-cerealbox-characters.png http://nielsmayer.com/meego/qml/qtzibit-medieval-mediterranean-map.png http://nielsmayer.com/meego/qml/qtzibit-mushroom-identification.png http://nielsmayer.com/meego/qml/qtzibit-presidents.png http://nielsmayer.com/meego/qml/qtzibit-redsox-vs-yankees.png http://nielsmayer.com/meego/qml/qtzibit-us-city-population.png http://nielsmayer.com/meego/qml/qtzibit-world-populations.png To get back to the Example Chooser, click the "Browse Examples" link on the upper-left corner of each Exhibit page. This invokes "javascript:window.qml.showExampleChooser();" which also shows how you can call back into QML from JavaScript running in the Exhibit web-page. The qtzibit installation places a number of interesting Exhibit examples directly on the filesystem. In conjunction with the modified exhibit&timeline, most of these examples work directly in the browser. Thus the "billionaries" example in the screenshot above can also be browsed directly e.g. "firefox /opt/qtzibit/exhibit/src/webapp/examples/billionaires/billionaires.html" ... This makes development and debugging of Exhibit JavaScript easier. To checkout, build and run qtzibit, first install QtSDK 1.1.2 ( http://labs.qt.nokia.com/2011/06/21/introducing-meego-1-2-harmattan-to-the-qt-sdk/ ), then do the following steps: svn checkout https://qtzibit.googlecode.com/svn/trunk/ qtzibit qtcreator qtzibit/qtzibit.pro ## --> In "Target Setup" dialog, select "Use Shadow Building" under Desktop details. --> Build All cd qtzibit-build-desktop##created by Shadow Building in qtcreator sudo make install ##need root to install to /opt/qtzibit /opt/qtzibit/bin/qtzibit##run the installed qtzibit! Note that the last step -- installation into /opt/qtzibit -- is necessary because all the HTML/JavaScript expect the Exhibit and Timeline code to reside in /opt/qtzibit/exhibit/* and /opt/qtzibit/timeline/*. Once installed, as long as you're not changing the code for the simile exhibit or timeline widgets, you can do your QML/Javascript development in qtcreator and test/debug in-place. Niels http://nielsmayer.com PS: Next step is to come up with a less "static" demo that mashes-up dynamic javascript data from QML derived from handset or tablet events, GPS data, etc. I think that http://zeitgeist-project.com/ data would be very interesting to present in qtzibit similar to http://seilo.geekyogre.com/2010/07/zeitgeist-geolocation-magic/ , however it's not something i have time to work on nowAnybody else interested? ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] QtZibit: Simile-Widgets.org Exhibit runs local in QtWebKit rendering from QML/Json.
Introducing http://code.google.com/p/qtzibit/ - Simile-widgets'
"Exhibit" running locally in QtWebKit, rendering arbitrary Json data
models from QML, Qt or QtMobility.
Some examples implemented in Exhibit: http://simile-widgets.org/exhibit/
With QtZibit, such apps could run locally (although the
google-map-based ones require an internet connection, the timeline,
timeplot, chart, visualizations don't). These can run "standalone" and
the associated JavaScript is loaded in from the local filesystem,
computed in QML/JavaScript/C++ or transferred from the web or local
SQL datastore. QtZibit can be used to visualize arbitrary datamodels
from JSON in QML, and in-turn, this JSON can be rendered via QtWebKit
in Exhibit. In many ways, it duplicates or complements the
"delegate"-based rendering of datamodels in Qt/QML, but uses Web-based
layouts and rendering.
For example, in
http://trunk.simile-widgets.org/exhibit/examples/polymap/medieval-mediterranean.html
, the rendered data comes from JSON elements that look like:
{"id":"15 - Madonna and Child",
"label":"15 - Madonna and Child",
"type":"Item",
"uri":"http://trunk.simile-widgets.org/exhibit/examples/polymap/item#15%20-%20Madonna%20and%20Child";,
"modified":"no",
"Image":"http://lh5.ggpht.com/_eb5gxCGMANM/SZ8XlfMwLiI/AGE/SbO0e2TncR0/s144/CImabueMadonna.jpg";,
"Century":"13th",
"Building+Name":"Church - Santa Trinita",
"latlng":"43.770031,11.250994",
"Medium":"gesso",
"Author":"Cimabue",
"Title":"Madonna and Child",
"City":"Florence",
"origin":"http://trunk.simile-widgets.org/exhibit/examples/polymap/medieval-mediterranean.html#15%20-%20Madonna%20and%20Child";
},
(See http://trunk.simile-widgets.org/exhibit/examples/polymap/ JSON
files visualized by these these "mashups" ; other examples at
http://trunk.simile-widgets.org/exhibit/examples/ )
The map elements in the "medieval mediterranean" example above are
rendered by extracting ".latlng" ".polyline", etc. entities from the
JSON data elements such as the one from the prior example.
Exhibit also has capabilities for rendering SPARQL queries, which
might be useful to combine with the existing "semantic desktop"
facilities in MeeGo/Harmattan that are based on
http://projects.gnome.org/tracker/ . One app that would be pretty cool
for would be to geolocate all phone events onto a map, or be able to
dial around & visualize all phone events on a single timeline, etc.
Or similarly, automatically render thumbnails for captured media on a
map or timeline based on tracker-extracted metadata.
Niels
http://nielsmayer.com
PS: For Harmattan ( http://swipe.nokia.com/ ) , it sure would be nice
if someone developed an Ovi Maps plugin that worked just like the
Google/OpenLayers/OpenStreetMap/VirtualEarth maps Exhibit supports
currently:
http://code.google.com/p/simile-widgets/source/browse/exhibit/trunk/src/webapp/api/extensions/map/map-extension.js
PPS: Unlike the web version, a Mobile or WebKit version of Exhibit can
call out from Exhibit back to QML and therefore allows invocation of
C++ primitives from an Exhibit UI -- Using
http://doc.qt.nokia.com/4.7/qml-webview.html#javaScriptWindowObjects-prop
... which means apps like
http://nielsmayer.com/xwiki/bin/view/Timeline/NprTimeline won't need
Flash for media playback, they'll just invoke QtMultimediaKit Audio or
Video players
___
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] Icon not visible on Meego Tablet
I've worked around this issue in a number of ways: (1) Put full path to icon in .desktop file, e.g. [Desktop Entry] Version=1.0 Encoding=UTF-8 Name=NPM MeeGoVid Comment=NPM launcher for /usr/share/meego-app-meegovid/main.qml GenericName=NPM MeeGoVid Exec=meego-qml-launcher --opengl --fullscreen --app meego-app-meegovid Terminal=false X-MultipleArgs=false Type=Application Icon=/usr/share/icons/hicolor/48x48/apps/gnome-mplayer.png Categories=Player;Video; (2) Put the icon in /usr/share/pixmaps, e.g.: -rw-r--r-- 1 root root 2960 2011-06-01 10:27 /usr/share/pixmaps/meego-app-npm.png And refer to it as "meego-app-npm" . [Desktop Entry] Version=1.0 Encoding=UTF-8 Name=NPM Launcher Comment=NPM launcher for /usr/share/meego-app-npm/main.qml GenericName=NPM Launcher Exec=meego-qml-launcher --opengl --fullscreen --app meego-app-npm Terminal=false X-MultipleArgs=false Type=Application Icon=meego-app-npm Categories=Player;Video; .. (3) There's also a bug related to breakage if a multi-entry field isn't terminated by ";" https://bugs.meego.com/show_bug.cgi?id=14930 (4) Many standard MeeGo apps (e.g. nautilus) can be installed on the TabletUX but do not show up in the app browser. That's because their desktop files contain "OnlyShowIn=GNOME;" There's also an similar "NotShowIn=X-MEEGO-NB;" Here's how to make the nautilus "$HOME" icon bring up the filebrowser and show the icon. So after doing "zypper in nautilus gnome-icon-theme" do the following for each app/icon you actually want to use: ... $ cp /usr/share/applications/nautilus-home.desktop ~/.local/share/applications/nautilus-home.desktop ## edit/patch with following: $ diff /usr/share/applications/nautilus-home.desktop ~/.local/share/applications/nautilus-home.desktop 189c189 < Icon=user-home --- > Icon=/usr/share/icons/gnome/48x48/places/user-home.png 194c194 < OnlyShowIn=GNOME; --- > # OnlyShowIn=GNOME; ... -- Niels http://nielsmayer.com PS: what's all this mean, and what's the diff between limited/unlimited/managed? /usr/share/applications/meego-app-contacts.desktop:X-MEEGO-CGROUP-PATH=managed /usr/share/applications/meego-app-contacts.desktop:X-MEEGO-CGROUP-CONTROLLERS=freezer /usr/share/applications/meego-app-email.desktop:X-MEEGO-CGROUP-PATH=limited /usr/share/applications/meego-app-email.desktop:X-MEEGO-CGROUP-CONTROLLERS=freezer /usr/share/applications/meego-app-im.desktop:X-MEEGO-CGROUP-PATH=limited /usr/share/applications/meego-app-im.desktop:X-MEEGO-CGROUP-CONTROLLERS=freezer /usr/share/applications/meego-app-music.desktop:X-MEEGO-CGROUP-PATH=unlimited /usr/share/applications/meego-app-music.desktop:X-MEEGO-CGROUP-CONTROLLERS=freeze ___ 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] multiple high security holes in meego browser
Regarding https://bugs.meego.com/show_bug.cgi?id=16284
Chromium browser sandbox feature is not working in MeeGo builds
.
In investigating why even the latest google-chrome emits "you are not
adequately sandboxed" message on MeeGo 1.2, I believe I've discovered a
kernel-shortcoming in MeeGo 1.2 as distributed on the ExoPC's
at 2011 MeeGo SF conference, and on latest
http://download.meego.com/live/MeeGo:/1.2 (for which repos on both
netbook and tablet have updated w/ "zypper dup --from
'MeeGo:1.2:non-oss (MeeGo_1.2)' --from 'MeeGo:1.2:oss (standard)'")
... and yes this egregious security flaw still exists, along with
this new-found related problem in the build of the MeeGo 1.2 pinetrail
kernel:
http://phajdan-jr.blogspot.com/2011/05/chromium-linux-kernel-configuration.html
("Chromium: Linux kernel configuration options needed for SUID
sandbox") suggests the following kernel configuration options which
are apparently missing in MeeGo 1.2 (
kernel-adaptation-pinetrail-2.6.38.2-8.12.i586 ):
General setup --->
-*- Namespaces support --->
[*] PID Namespaces
[*] Network namespace
Here's my test script with detailed comments:
$ diff /usr/bin/meego-app-browser /usr/local/bin/meego-sandboxed-browser
8a9,48
> ## NPM: per
> ## http://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment
> ## chrome-sandbox binary taken from
> ##
> https://dl-ssl.google.com/linux/direct/google-chrome-stable_current_i386.rpm
> ## which installs at:
> ## ROOT-meegotab-108-~> ll /opt/google/chrome/chrome-sandbox
> ## -rwsr-xr-x 1 root root 10420 2011-05-19 18:10
> /opt/google/chrome/chrome-sandbox*
> ## Note that it must be SUID. See below also where
> "--enable-seccomp-sandbox" added to launch
> ## suggested by http://bugs.gentoo.org/363907 ...
> ## checking that this isn't bullshit:
> ## $ strings meego-app-browser | grep SANDBOX
> ## CHROME_DEVEL_SANDBOX
> ## However, it appears MeeGo kernel not config'd correctly per
> ##
> http://phajdan-jr.blogspot.com/2011/05/chromium-linux-kernel-configuration.html
> ## on Fedora the equivalent (google-chrome-stable-11.0.696.71-86024.x86_64)
> version of google-chrome
> ## reports:
> ## Sandbox Status
> ## SUID Sandbox Yes
> ## PID namespaces Yes
> ## Network namespaces Yes
> ## Seccomp sandbox No
> ## You are adequately sandboxed.
> ## On MeeGo 1.2, google-chrome-stable-11.0.696.71-86024.i386, about:sandbox
> reports:
> Sandbox Status
>
> SUID Sandbox Yes
> Seccomp sandbox No
> You are not adequately sandboxed!
> ## The reason for the inadequate sandbox is hidden, but suggested in the
> ## blogpost link above:
> ##
> ## It turned out that to make the SUID sandbox fully effective, the kernel
> ## must support PID (process id) and network namespaces. Adding to the
> ## confusion, when the kernel supports them, about:sandbox displays entries
> ## for "PID namespaces" and "network namespaces" and a green "yes" next to
> ## them. But if the kernel doesn't support those features, nothing is
> ## displayed, which makes it difficult to diagnose what's wrong with the
> ## sandbox.
> ##
> export CHROME_DEVEL_SANDBOX=/opt/google/chrome/chrome-sandbox
>
151c191
< exec $LIBDIR/$APPNAME "--fullscreen" "--opengl"
"--disable-accelerated-compositing" "--enable-click-to-play" "--tabs-limit=8"
"$@"
---
> exec $LIBDIR/$APPNAME "--fullscreen" "--opengl"
> "--disable-accelerated-compositing" "--enable-seccomp-sandbox"
> "--tabs-limit=8" "$@"
152a193,194
>
>
...
-- Niels
http://nielsmayer.com
PS: my test script failed to deliver an adequately sandboxed browser
on my ExoPC tablet, which is why I started investigating what was
going on with my "reference" software and sandbox, the latest stable
chrome browser from google.com .
PPS: On the ExoPC MeeGo Tablet UX, I'm happily using using
http://wiki.meego.com/MeeGo-Lem-Firefox4 which runs everything in its
own version of the sandbox. Perhaps one not vulnerable to the same
class of attack as
http://www.vupen.com/demos/VUPEN_Pwning_Chrome.php
https://threatpost.com/en_us/blogs/researchers-say-new-bugs-can-bypass-google-chrome-sandbox-050911
___
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] Top Application in Meego Tablet
On Mon, May 23, 2011 at 7:25 AM, Arjan van de Ven wrote: > I'm pretty sure the answer is that the concept of "top application" outright > does not exist. Assuming we're talking the Window System "X" and its standards, then yes it does exist, and has existed for a long time -- in a standard-bearing form since OSF/Motif and CDE (e.g. XmDIALOG_SYSTEM_MODAL ). Freedesktop.org has updated the original architecture. However, it certainly is a concept that exists in X windows. (how else would "always keep window on top" be implemented in many desktops, or tool panels, etc). It is concerning to me, after the attending the recent conference, that MeeGo may be adding nonstandard extensions and functionality to the window manager (for video). So it would be nice to understand the official MeeGo position on working within accepted norms of X Windows and X Window Manager Protocols. And if they're being extended, that "upstream" agrees with the wisdom of the extensions. Having worked with X window managers since the very beginning, (prior having worked on X10 which didn't have the concept of a separate window manager), this is not the sort of thing that should be extended or overloaded in a cavalier fashion, even for a new paradigm like "Tablet." For more info, regarding the standard window types and their behavior, see below: http://standards.freedesktop.org/wm-spec/wm-spec-1.4.html#id2551529 /// _NET_WM_WINDOW_TYPE _NET_WM_WINDOW_TYPE, ATOM[]/32 This SHOULD be set by the Client before mapping to a list of atoms indicating the functional type of the window. This property SHOULD be used by the window manager in determining the decoration, stacking position and other behavior of the window. The Client SHOULD specify window types in order of preference (the first being most preferable) but MUST include at least one of the basic window type atoms from the list below. This is to allow for extension of the list of types whilst providing default behavior for Window Managers that do not recognize the extensions. Rationale: This hint is intended to replace the MOTIF hints. One of the objections to the MOTIF hints is that they are a purely visual description of the window decoration. By describing the function of the window, the Window Manager can apply consistent decoration and behavior to windows of the same type. Possible examples of behavior include keeping dock/panels on top or allowing pinnable menus / toolbars to only be hidden when another window has focus (NextStep style). _NET_WM_WINDOW_TYPE_DESKTOP, ATOM _NET_WM_WINDOW_TYPE_DOCK, ATOM _NET_WM_WINDOW_TYPE_TOOLBAR, ATOM _NET_WM_WINDOW_TYPE_MENU, ATOM _NET_WM_WINDOW_TYPE_UTILITY, ATOM _NET_WM_WINDOW_TYPE_SPLASH, ATOM _NET_WM_WINDOW_TYPE_DIALOG, ATOM _NET_WM_WINDOW_TYPE_NORMAL, ATOM _NET_WM_WINDOW_TYPE_DESKTOP indicates a desktop feature. This can include a single window containing desktop icons with the same dimensions as the screen, allowing the desktop environment to have full control of the desktop, without the need for proxying root window clicks. _NET_WM_WINDOW_TYPE_DOCK indicates a dock or panel feature. Typically a Window Manager would keep such windows on top of all other windows. _NET_WM_WINDOW_TYPE_TOOLBAR and _NET_WM_WINDOW_TYPE_MENU indicate toolbar and pinnable menu windows, respectively (i.e. toolbars and menus "torn off" from the main application). Windows of this type may set the WM_TRANSIENT_FOR hint indicating the main application window. _NET_WM_WINDOW_TYPE_UTILITY indicates a small persistent utility window, such as a palette or toolbox. It is distinct from type TOOLBAR because it does not correspond to a toolbar torn off from the main application. It's distinct from type DIALOG because it isn't a transient dialog, the user will probably keep it open while they're working. Windows of this type may set the WM_TRANSIENT_FOR hint indicating the main application window. _NET_WM_WINDOW_TYPE_SPLASH indicates that the window is a splash screen displayed as an application is starting up. _NET_WM_WINDOW_TYPE_DIALOG indicates that this is a dialog window. If _NET_WM_WINDOW_TYPE is not set, then windows with WM_TRANSIENT_FOR set MUST be taken as this type. _NET_WM_WINDOW_TYPE_NORMAL indicates that this is a normal, top-level window. Windows with neither _NET_WM_WINDOW_TYPE nor WM_TRANSIENT_FOR set MUST be taken as this type. /// Specifically, http://standards.freedesktop.org/wm-spec/wm-spec-1.4.html#id2505639 / Layered stacking order Some window managers keep the toplevel windows not in a single linear stack, but subdivide the stack into several layers. There is a lot of variation among the features of layered stacking order implementations. The number of layers may or may not be fixed. The layer of a toplevel window may be explicit and directly modifiable or derived from other properties of the window, e.g. the type of the window. The stacking order may or may not be strict, i.e. not all
Re: [MeeGo-dev] application for testing sensors
On Wed, May 18, 2011 at 1:37 AM, wrote: > Qt mobility sensors examples: > > http://www.qt.gitorious.org/qt-mobility/qt-mobility/trees/master/examples/sensors A slightly older (beta0, vs beta1+ on git) version is also available in MeeGo 1.2 see http://download.meego.com/live/MeeGo:/1.2.0:/oss/standard/i586/qt-mobility-examples-1.2.0~beta0+git2726-9.31.i586.rpm But on the lenovo s10-3t it doesn't work ( https://bugs.meego.com/show_bug.cgi?id=10885 ?): /// meegolem-168-.../local/src> /usr/lib/qtmobility/demos/smallsensors [...] loaded the Generic plugin loaded the grue plugin Loaded the MeeGo sensor plugin Request for interface not granted... Request for interface not granted... Request for interface not granted... Request for interface not granted... /// Any suggestions for getting this to work on the s10-3t, or is this only working on the n900? Here's the contained files in the MeeGo Mobility examples distibution : /// meegolem-169-.../local/src> rpm -ql qt-mobility-examples-1.2.0~beta0+git2726-9.31.i586 /usr/lib/qt4/plugins/sensors/libqtsensors_grueplugin.so /usr/lib/qt4/plugins/serviceframework/libserviceframework_bluetoothtransferplugin.so /usr/lib/qt4/plugins/serviceframework/libserviceframework_filemanagerplugin.so /usr/lib/qt4/plugins/serviceframework/libserviceframework_landlinedialerservice.so /usr/lib/qt4/plugins/serviceframework/libserviceframework_notesmanagerplugin.so /usr/lib/qt4/plugins/serviceframework/libserviceframework_voipdialerservice.so /usr/lib/qtmobility/demos /usr/lib/qtmobility/demos/lightmaps_with_location /usr/lib/qtmobility/demos/nmealog.txt /usr/lib/qtmobility/demos/player /usr/lib/qtmobility/demos/qmlcontacts /usr/lib/qtmobility/demos/serviceactions /usr/lib/qtmobility/demos/smallsensors /usr/lib/qtmobility/demos/weatherinfo_with_location /usr/lib/qtmobility/examples /usr/lib/qtmobility/examples/accel /usr/lib/qtmobility/examples/annotatedurl /usr/lib/qtmobility/examples/arrowkeys /usr/lib/qtmobility/examples/audiodevices /usr/lib/qtmobility/examples/audioinput /usr/lib/qtmobility/examples/audiooutput /usr/lib/qtmobility/examples/audiorecorder /usr/lib/qtmobility/examples/battery-publisher /usr/lib/qtmobility/examples/battery-subscriber /usr/lib/qtmobility/examples/battery-subscriber/battery-subscriber.qml /usr/lib/qtmobility/examples/battery-subscriber/content /usr/lib/qtmobility/examples/battery-subscriber/content/bubble.png /usr/lib/qtmobility/examples/btchat /usr/lib/qtmobility/examples/btfiletransfer /usr/lib/qtmobility/examples/btscanner /usr/lib/qtmobility/examples/bttennis /usr/lib/qtmobility/examples/calendardemo /usr/lib/qtmobility/examples/camera /usr/lib/qtmobility/examples/content-sfw-dialer /usr/lib/qtmobility/examples/content-sfw-dialer/DialButton.qml /usr/lib/qtmobility/examples/content-sfw-dialer/DialScreen.qml /usr/lib/qtmobility/examples/content-sfw-dialer/DialerList.qml /usr/lib/qtmobility/examples/content-sfw-dialer/call.png /usr/lib/qtmobility/examples/content-sfw-dialer/hangup.png /usr/lib/qtmobility/examples/content-sfw-dialer/qmldir /usr/lib/qtmobility/examples/content-sfw-notes /usr/lib/qtmobility/examples/content-sfw-notes/Button.qml /usr/lib/qtmobility/examples/content-sfw-notes/Dialog.qml /usr/lib/qtmobility/examples/content-sfw-notes/InputDialog.qml /usr/lib/qtmobility/examples/content-sfw-notes/Main.qml /usr/lib/qtmobility/examples/content-sfw-notes/icons /usr/lib/qtmobility/examples/content-sfw-notes/icons/addIcon.png /usr/lib/qtmobility/examples/content-sfw-notes/icons/deleteIcon.png /usr/lib/qtmobility/examples/content-sfw-notes/icons/nextIcon.png /usr/lib/qtmobility/examples/content-sfw-notes/icons/prevIcon.png /usr/lib/qtmobility/examples/content-sfw-notes/icons/searchIcon.png /usr/lib/qtmobility/examples/content-sfw-notes/qmldir /usr/lib/qtmobility/examples/cubehouse /usr/lib/qtmobility/examples/declarative-music-browser /usr/lib/qtmobility/examples/declarative-sfw-dialer.qml /usr/lib/qtmobility/examples/declarative-sfw-notes.qml /usr/lib/qtmobility/examples/dialer_service /usr/lib/qtmobility/examples/documentproperties /usr/lib/qtmobility/examples/flickr.qml /usr/lib/qtmobility/examples/flickrcommon /usr/lib/qtmobility/examples/flickrcommon/Progress.qml /usr/lib/qtmobility/examples/flickrcommon/RestModel.qml /usr/lib/qtmobility/examples/flickrcommon/ScrollBar.qml /usr/lib/qtmobility/examples/flickrcommon/Slider.qml /usr/lib/qtmobility/examples/flickrcommon/qmldir /usr/lib/qtmobility/examples/flickrdemo /usr/lib/qtmobility/examples/flickrmobile /usr/lib/qtmobility/examples/flickrmobile/Button.qml /usr/lib/qtmobility/examples/flickrmobile/GeoTab.qml /usr/lib/qtmobility/examples/flickrmobile/GridDelegate.qml /usr/lib/qtmobility/examples/flickrmobile/ImageDetails.qml /usr/lib/qtmobility/examples/flickrmobile/ListDelegate.qml /usr/lib/qtmobility/examples/flickrmobile/TitleBar.qml /usr/lib/qtmobility/examples/flickrmobile/ToolBar.qml /usr/lib/qtmobility/examples/flic
Re: [MeeGo-dev] multiple high security holes in meego browser
On Tue, May 17, 2011 at 7:20 AM, An Ahooja wrote: > This was reported to meego bugzilla but got no response. > > The meego-app-browser to be released in MeeGo 1.2 is still based on chromium > 12.0.712.0. It is a trunk version released on late March and misses multiple > security fixes in chrome 11.0.696.57, which was released on a different branch > in late April. More issues not receiving adequate response: (1) Chromium browser sandbox feature is not working in MeeGo builds https://bugs.meego.com/show_bug.cgi?id=16284 In particular, note that the issue also applies to meego-tv-browser and meego-app-browser: /// https://bugs.meego.com/show_bug.cgi?id=16284#c5 (In reply to comment #4) ryanware 2011-05-03 22:24:07 UTC > We really need to figure out how to fix this before release. This allows > protections *when* future arbitrary code execution issues are found in > Chromium. Without sandboxing, we're running without [sic] safeties off. That's why I proposed this issue as a release blocker. MeeGo can have all the security in the world, and then a small omission like this can leave a gaping web-sized hole being exposed through the browser. Furthermore, I see no updates to the sanity test plans (e.g. "run about:sandbox" and "about:plugins" in chromium on each image) to make sure this kind of error doesn't regress, which is probably easy enough to do with a tiny change of configuration in the build rules of such complex programs. Also, I haven't seen any follow-up regarding all the other places this issue surfaces. For example: Repository: oss Name: meego-tv-browser Version: 8.0.552.0-1.22 Arch: i586 Vendor: meego Installed: No Status: not installed Installed Size: 57.8 MiB Summary: A Qt-based WebKit powered web browser Description: Qt-based Chromium is an open-source web browser, powered by WebKit. Repository: oss Name: meego-app-browser Version: 8.0.552.0-6.18 Arch: i586 Vendor: meego Installed: No Status: not installed Installed Size: 56.6 MiB Summary: A Qt-based WebKit powered web browser Description: Qt-based Chromium is an open-source web browser, powered /// (2) Finally, if you invoke a text field in the browser with spelling checking option enabled, you'll crash, given the pervasive-crash-causing ability (evolution, browsers, pidgin, etc) of having a language dictionary installed alongside 'hunspell'. It's a pretty easy thing to test... just try composing an email message in gmail/yahoo/ovi/etc. "hunspell dumps core with default english dictionary, and is installed with no default dictionary" ( https://bugs.meego.com/show_bug.cgi?id=16879 ). Niels http://nielsmayer.com PS: All of the above, and also recent personal preference after having used chrome for years, is why I'm running http://wiki.meego.com/MeeGo-Lem-Firefox4 and got awesome firefox4-based BlueGriffon wysiwyg thrown in for "even more free" also I'm enjoying the delights of pretending i'm on an i-pad using the meego- 1.2 touch netbook with http://chrispederick.com/work/user-agent-switcher/ firefox plugin ___ 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] PDF reader for tablets running MeeGo
I installed Fedora's http://xournal.sourceforge.net/ on MeeGo 1.2 Netbook UX && Lenovo s10-3t (using http://wiki.meego.com/MeeGo-Lem ). ( See http://koji.fedoraproject.org/koji/buildinfo?buildID=199012 for SRPMs and RPMs ). Xournal is awesome on a touchscreen. Even if you're not planning to use it for handwriting notes and annotations onto an existing PDF, you can put it in "hand scroll" mode and then just flick the PDF document around to scroll, much like you would in a touch-enabled browser. I've made it my default PDF viewer on my systems as it's more "ready to hand", as Heidegger would say, on a touchscreen, compared to okular or acroread. IMHO, Xournal should be a standard part of MeeGo. Its availability on Maemo/n900 shows it translates well to touchscreen and mobile usage: http://maemo.org/downloads/product/Maemo5/xournal/ ... meegolem-1-~> zypper info xournal Loading repository data... Reading installed packages... Information for package xournal: Repository: Fedora 14 - i386 Name: xournal Version: 0.4.5-7.fc14 Arch: i686 Vendor: Fedora Project Installed: No Status: not installed Installed Size: 593.0 KiB Summary: Notetaking, sketching, PDF annotation and general journal Description: Xournal is an application for notetaking, sketching, keeping a journal and annotating PDFs. Xournal aims to provide superior graphical quality (subpixel resolution) and overall functionality. meegolem-2-~> sudo zypper in xournal Loading repository data... Reading installed packages... Resolving package dependencies... Problem: xournal-0.4.5-7.fc14.i686 requires libpoppler.so.7, but this requirement cannot be provided uninstallable providers: poppler-0.14.4-1.fc14.i686[fedora] Solution 1: Following actions will be done: [... uninstall everything to satisfy fedora libpoppler ] Solution 2: do not install xournal-0.4.5-7.fc14.i686 Solution 3: break xournal by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c] (c): 3 Resolving dependencies... Resolving package dependencies... The following NEW package is going to be installed: xournal 1 new package to install. Overall download size: 255.0 KiB. After the operation, additional 593.0 KiB will be used. Continue? [y/n/?] (y): y Retrieving package xournal-0.4.5-7.fc14.i686 (1/1), 255.0 KiB (593.0 KiB unpacked) Retrieving: xournal-0.4.5-7.fc14.i686.rpm [done] Installing: xournal-0.4.5-7.fc14 [done] . Just a little hack to take care of libpoppler version diffs between Fedora and MeeGo (needed after choosing zypper's "Solution 3: break xournal by ignoring some of its dependencies") meegolem-3-~> sudo ln -s /usr/lib/lib/libpoppler.so.13.0.0 /usr/lib/libpoppler.so.7 meegolem-4-~> ll /usr/lib/libpoppler.so* lrwxrwxrwx 1 root root 20 2011-04-18 11:09 /usr/lib/libpoppler.so.13 -> libpoppler.so.13.0.0* -rwxr-xr-x 1 root root 1880016 2011-04-18 02:23 /usr/lib/libpoppler.so.13.0.0* lrwxrwxrwx 1 root root 20 2011-04-09 15:42 /usr/lib/libpoppler.so.7 -> libpoppler.so.13.0.0* .. and we're good to go with yet-another excellent fedora-quality&fedora-curated Linux package: meegolem-5-~> env DISPLAY=:0.0 xournal .. Next! -- 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
[MeeGo-dev] why does booting with "nohpet" solve suspend bug in 1.2 Netbook?
Is anybody else seeing https://bugs.meego.com/show_bug.cgi?id=17233
("Netbook display often broken after suspend, especially after
starting legacy X programs")
It appears to be a longstanding (since 1.1) bug for some platforms, e.g.
"[Toshiba NB 305 / Lenovo Ideapad S10-3t] fails to resume from suspend"
https://bugs.meego.com/show_bug.cgi?id=10351
Based on a suggestion in the above, I disabled hpet at boot and now my
1.2 "trunk" netbook recovers from suspend even after running a
terminal or emacs. Without it, you'd see a guaranteed dead display on
resume if you used any of these programs.
So what's the downside to booting with "nohpet" ?
For example, even w/ nohpet, I still get high precision timers in the
main place I want, ALSA, so nothing but benefit here:
.
meegolem-50-~> cat /proc/asound/timers
G0: system timer : 1000.000us (1000 ticks)
G3: HR timer : 0.001us (10 ticks)
P0-0-0: PCM playback 0-0-0 : SLAVE
P0-0-1: PCM capture 0-0-1 : SLAVE
.
And also the ALSA midi seq interface on this '.38 pinetrail adaptation
kernel has HR timers for snd_seq_midi despite seemingly-missing
snd_hrtimer (
http://lists.meego.com/pipermail/meego-kernel/2011-March/002282.html
) (nice!):
.
meegolem-52-~> qtractor & ## http://qtractor.sourceforge.net
[...]
meegolem-53-~> cat /proc/asound/seq/timer
Timer for queue 0 : HR timer
Period time : 0.0
Skew : 65536 / 65536
.
However, even booting with "nohpet" , one can trigger the "display is
dead until reboot" bug by suspending while running programs like
qtractor that enable hrtimer usage in the alsa midi seq interface, as
indicated by the presenence of HPET timer i/proc/asound/seq/timer .
And once "cat /proc/asound/seq/timer" outputs something at all, then
https://bugs.meego.com/show_bug.cgi?id=17233 is seen consistently.
(Therefore with or without the "nohpet" fix, one shouldn't suspend
after running qtractor, just power-down).
Perhaps too many uses/users of a limited
http://www.kernel.org/doc/Documentation/timers/hpet.txt resource is
happening, and/or some mutex locking mechanism on the limited timers
resource is failing?
Bug 17233 - Netbook display often broken after suspend, especially
after starting legacy X programs
BUILD IMAGE:
"1.2" == 2.6.38.2-8.6-adaptation-pinetrail
+
http://download.meego.com/snapshots/latest-testing-1.2/repos/oss/ia32/packages
+ http://download.meego.com/live/devel:/connectivity:/latest/Trunk
HARDWARE MODEL:
Lenovo S10-3t
BUG DETAILED DESCRIPTIONS
===
If you boot up MeeGo 1.2 and just play around with various netbook-UX panels
but don't launch any programs, then suspend, the display will often work after
suspend.
However, if you launch any gnome programs that haven't specifically been
customized for the netbook display (like evolution), such as,
gnome-terminal(1), emacs(1), etc... then if you suspend, you might as well shut
down, because that's the only way you'll be able to use the display again. The
X display is running, and hitting the powerbutton probably pops up the 30
second dialog (because it shuts down 30 seconds later)... it's just that you
can't see anything on the display, and no amount of turning on/off display
switching display ports or anything gets it back again, other than a reboot.
To work-around, I added the following boot entry and now boot into a system
with HPET disabled
# Fix suspend bug? https://bugs.meego.com/show_bug.cgi?id=10351
label 2.6.38.2-8.6-adaptation-pinetrail
menu label no-HPET 1.2 (2.6.38.2-7.1-adaptation-pinetrail)
menu default
kernel vmlinuz-2.6.38.2-8.6-adaptation-pinetrail
append ro root=/dev/sda5 quiet vga=current nohpet
With HPET disabled on this 2.6.38.2-8.6 kernel, the display can be seen after
suspend and it doesn't matter if legacy-X apps like emacs(1) or
gnome-terminal(1) have been run.
EXACT STEPS LEADING TO PROBLEM:
===
1. boot Meego 1.2
2. bring up gnome-terminal
3. close lid of netbook until lights indicate it has suspended
4. reopen netbook
5. display is dark, all work lost, and there's no way to recover w/o
power-cycle.
EXPECTED OUTCOME:
===
Netbook suspends and resumes with display and applications working and no
hangs.
ACTUAL OUTCOME:
===
Netbook must be rebooted. Display won't work. Work not automatically saved by
shutting down apps is lost.
USER IMPACT:
===
Netbook cannot be used as one would expect to use a netbook, in a mobile
situation, with lots of suspend/resumes and not needing to pay attention to
what apps bork up the display and force you to reboot each suspend.
REPRODUCIBILI
Re: [MeeGo-dev] https://bugs.meego.com/ can not work now, when will it be recovered?
On Wed, May 4, 2011 at 8:39 PM, Alexander Bokovoy wrote: >> (https://bugs.meego.com) > There seem to be some misconfiguration of SSL setup at meego.com. I > tried with QtWebkit and it also unable to reach and render it. KDE's Konqueror browser also cannot browse bugs.meego.com over SSL. It outputs the following error: http://nielsmayer.com/meego/bugs-meego-com-bad-certificate.png It's as if the WebKit based browsers (such as Konqueror) do not recognize Go Daddy as CA. (Note the empty certificate chain and "this certificate is not signed by any trusted authority" in image above). FireFox4 has the GoDaddy cert built-in and therefore recognizes it: http://nielsmayer.com/meego/bugs-meego-com-go-daddy-cert.png http://nielsmayer.com/meego/bugs-meego-com-go-daddy-ca.png Perhaps the webkit based browsers need the GoDaddy CA certificate added on or installed separately in order to browse/login to bugs.meego.com. Typically most browsers have some way of adding private or unrecognized certificates. If the web transaction fails as early as checking the validity of the SSL certificate, you will certainly see very little on the wire. It will bail out immediately, as you noted, with a "handshake failure." That's the whole point of using a http://en.wikipedia.org/wiki/Public_key_infrastructure in the first place. Why is cheapskate GoDaddy certificate being used in the first place? I always associated GoDaddy with pornsites and other fly-by-night businesses. Certainly not for "serious" websites. Doesn't meego.com deserve a pricy and widely recognized Verisign cert? Also, to keep MeeGo.com's certificates "under control" it might be wise (as opposed to pound foolish) to use the same wildcard cert (*.meego.com) for all MeeGo.com sites needing SSL (e.g. OBS, wiki, etc). http://www.verisign.com/ssl-certificates/wildcard-ssl-certificates/ 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] FYI -- prevent tracker or other services from starting up in MeeGo 1.2 netbook
On Thu, Apr 28, 2011 at 2:23 PM, Martyn Russell wrote: > On 28/04/11 20:55, Niels Mayer wrote: >> Although I intend to investigate all the features tracker provides in >> MeeGo, I don't want to do it right now. And it was unpredictably >> taking up precious CPU cycles on this wee Atom N455, every drop of >> which is needed for processing multimedia happening "right now." > [...] > Well, you can expect it to return out of date search results when looking up > files in your applications. Especially if those files are the multimedia > you're wanting to process. Which applications would be affected? How do I invoke tracker search on the MeeGo 1.2 netbook (other than command-line)? > Depending on your version on the device, this situation has been improved > recently. > > We've added some measures like: [...] Thanks. I will definitely look into these once I begin to explore and better understand tracker's role in various different MeeGo platform offerings. My comments were about the MeeGo 1.2 Netbook UX on kernel-adaptation-pinetrail-2.6.38.2-8.2. > I am concerned about your report of ill performance from Tracker though. > It's not what we've experienced in Harmattan for some time now. Can you > provide more details (perhaps in a bug report) to try to improve the > situation? In some recent updates of tracker, I've found the fan running at times when I expected the netbook to be silent (it has SSD). Or when it's on battery. Or using some multimedia apps (e.g. qtractor with various plugins), openshot, xbmc, that need all of the CPU. That's what prompted me to disable tracker, until I decide to start using it explicitly. Furthermore, I notice it running when I mount external memory cards and/or network disks (sshfs?), perhaps indexing external disks and causing unexpected network and processor load. It may need some "throttling" on a MeeGo netbook with SSD-based filesystem, because the processor has less time to do other tasks while waiting on the last set of tracker disk I/O requests. And consequently, higher load associated with the increased disk system data-rate, than what might be seen on with slower disks. Similar issues may exist when indexing fast external network disks, alongside network loading. IMHO, it shouldn't run automatically at all when on battery. The user should be given a GUI option to control when it runs, or run manually. For resource-intensive programs, or those manipulating the very data tracker needs to index, something like pasuspender(1) might be useful, to wrap the invocation of some resource-needing program to prevent competition for resources. It could also manually run the tracker-update on completion of the program -- e.g., after the media being captured or edited can be guaranteed quiescent on disk. Alternately, as mentioned, an interface that starts/stops tracker whenever the computer is "idle." I like the idea of a visualizing screensaver as I like the computer/GUI to have some kind of representation of what it's doing "under the hood" when some special resource-consuming process is running. Even better, to have the "screensaver" provide a visualization of what it's adding to the information repository, which may help in serendipitous discovery. > What version of Tracker are you using there? tracker-utils-0.10.6-1.23.i586 libqttracker-devel-6.12.6-2.105.i586 libqtsparql-tracker-extensions-0.0.7-1.13.i586 libqtsparql-tracker-0.0.21-1.6.i586 qtcontacts-tracker-4.11.8.1-1.5.i586 libqtcontacts-tracker-extensions-4.11.8.1-1.5.i586 libqttracker-6.12.6-2.105.i586 tracker-0.10.6-1.23.i586 libqtsparql-tracker-direct-0.0.21-1.6.i586 libqtsparql-tracker-extensions-devel-0.0.7-1.13.i586 libqtcontacts-tracker-extensions-devel-4.11.8.1-1.5.i586 it appears that the following hasn't been installed by default, | tracker-upnp | UPnP miner for Tracker | package > What makes you think it is Tracker which is causing the problems and not > some other process? top(1). powertop(1) > Hope this helps, Thank you for the information on tracker. I am not trying to "beat up" on tracker, it's just that my current usage of MeeGo doesn't seem to require it, and I don't understand it well enough to control it. So it was easier to just shut it off. Perhaps due to all the other parts of 1.2 that have been postponed or removed, it appears that tracker needs better integration into the current MeeGo 1.2 Netbook UX, and I was too busy getting other stuff working to notice tracker on the Handset. I do think that "semantic desktop" and "semantic search" support is a good idea and perhaps some ideas for "user experience" integration of semantic search/tracking into the netbo
[MeeGo-dev] Enable contour shuttlexpress or shuttlepro in MeeGo 1.2? (vs total wiimote success)
In http://www.linuxjournal.com/article/10935?page=0,2 Ibrahim Haddad writes: "Figure 9. The MeeGo IVI home screen with the taskbar as it appears on the left side of the screen. The taskbar, [...] can be controlled by a Contour ShuttleXpress scroll wheel, touchscreen or mouse, and it's designed to reflect the scroll-wheel usage, with the ability to spin through the menu options and make selections or go back, by pressing two buttons or tapping the touchscreen (photo credit: meego.com)." Seeing this, I plugged into my MeeGo 1.2 netbook my first generation countour shuttlepro (ca 2002, something I'd given up on having an interface written for Linux until I read the above) and lsusb(1) reports; "Bus 002 Device 002: ID 0b33:0010 Contour Design, Inc." But doesn't seem to recognize it. Any suggestions, or should I keep giving up? Chances are it needs a program to interpret events and translate them to keyboard&joystick events, much like wminput(1) does for the Wiimote (*). Is there any way of separating out the MeeGo IVI's ShuttleXpress code for use by other UX's, such as a custom input daemon which handles it? -- Niels http://nielsmayer.com PS: (*) one device not to give up on is the old "Wii" video game Wiimote. Trivial to pair and setup with wmgui(1): ( http://abstrakraft.org/cwiid/ ). The GUI looks like this in MeeGo 1.2 while pressing a few buttons and moving around: http://nielsmayer.com/meego/wmgui-for-wiimote-and-nunchuk-via-bluetooth-on-meegolem.png . You can also run another cwiid program wminput(1) and then it turns the Wiimote into a mouse control and the various buttons work as well. Turns the Wiimote into an xbmc(1) remote. Guess I know how I'll be controlling a future home-made MeeGo set-top box. :-) PPS: I guess a QtMobility sensors interface to the Wiimote accelerometers would be too much success for one experiment... wiining! ___ 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 -- prevent tracker or other services from starting up in MeeGo 1.2 netbook
Although I intend to investigate all the features tracker provides in MeeGo, I don't want to do it right now. And it was unpredictably taking up precious CPU cycles on this wee Atom N455, every drop of which is needed for processing multimedia happening "right now." In /etc/xdg/autostart/ note the following files which start up tracker and other services after the system reaches runlevel 5: ... -rw-r--r-- 1 root root 281 2011-04-14 04:30 anerley-account-starter.desktop -rw-r--r-- 1 root root 2619 2011-04-15 06:31 bluetooth-panel.desktop -rw-r--r-- 1 root root 2135 2011-02-25 05:05 carrick.desktop -rw-r--r-- 1 root root 4273 2011-04-27 04:55 evolution-alarm-notify.desktop -rw-r--r-- 1 root root 5078 2011-04-26 05:16 gnome-keyring-pkcs11.desktop -rw-r--r-- 1 root root 4785 2011-04-26 05:16 gnome-keyring-secrets.desktop -rw-r--r-- 1 root root 3892 2011-04-26 05:16 gnome-keyring-ssh.desktop -rw-r--r-- 1 root root 7372 2011-03-16 16:44 gnome-screensaver.desktop -rw-r--r-- 1 root root 2892 2011-04-14 04:43 gnome-settings-daemon.desktop -rw-r--r-- 1 root root 9052 2011-04-20 05:50 gpk-update-icon.desktop -rw-r--r-- 1 root root 365 2011-02-21 20:56 matchbox-panel.desktop -rw-r--r-- 1 root root 1180 2011-04-20 04:34 meego-panel-myzone.desktop -rw-r--r-- 1 root root 608 2011-04-12 13:13 meego-power-icon.desktop -rw-r--r-- 1 root root 88 2010-09-29 00:43 messageserver.desktop -rw-r--r-- 1 root root 82 2011-02-02 03:53 msyncd.desktop -rw-r--r-- 1 root root 69 2010-10-15 05:55 mthemedaemon.desktop -rw-r--r-- 1 root root 6296 2011-02-21 21:36 print-applet.desktop -rw-r--r-- 1 root root 3459 2011-04-22 04:46 pulseaudio.desktop -rw-r--r-- 1 root root 82 2011-02-16 18:46 sample-media-install.desktop -rw-r--r-- 1 root root 156 2011-04-27 07:03 syncevo-dbus-server.desktop -rw-r--r-- 1 root root 2466 2011-04-27 05:56 tracker-miner-fs.desktop -rw-r--r-- 1 root root 2256 2011-04-27 05:56 tracker-store.desktop -rw-r--r-- 1 root root 4006 2011-02-21 20:56 user-dirs-update-gtk.desktop ... To prevent these (or any other) global autostarts, place a small file in one's own autostart (see http://standards.freedesktop.org/autostart-spec/autostart-spec-latest.html#id2452149 ): ... $ cat ~/.config/autostart/tracker-miner-fs.desktop [Desktop Entry] Hidden=true Name=Tracker File System Miner $ cat ~/.config/autostart/tracker-store.desktop [Desktop Entry] Hidden=true Name=Tracker Store ... Then log out/in or reboot. Niels http://nielsmayer.com PS: So what can I expect to break with tracker not running on the netbook? Is it something that can run from a cron job or as a "screensaver" (so that it's busy when the desktop is idle, drawing pretty 3d-visualizations of the data it is collecting ). ___ 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
On Tue, Apr 26, 2011 at 1:02 PM, Brendan Le Foll wrote: > 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. Thank you for reminding me to look at what's going on at the playbin2 level, and also for mention of madeo-uplayer -- I'll have a look. Sometimes playbin2 has bugs that prevent proper streaming, however, per: https://bugzilla.gnome.org/show_bug.cgi?id=629506 . The bug does have good reminders on gst-launch options to set. Also, http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-base-plugins/html/gst-plugins-base-plugins-playbin2.html ,,, However, the general problem I'm getting at is "whither QtMultiMediaKit" for fully supporting the underlying Linux system provided by MeeGo. Isn't QtMultiMediaKit ultimately underlying the video functionality of meego-app-video as well? In addition to potential issues with streaming media, how would the suggestions in "Using GStreamer for hardware accelerated video decoding on Intel® Atom™ Processor E6xx series" ( http://download.intel.com/design/intarch/PAPERS/324294.pdf ) be applied or setup in meego-app-video, assuming the platform had capabilities for specific hardware acceleration?? : . An example of playing hardware accelerated VC-1 video clip using gst-launch: gst-launch filesrc location=./sample.wmv ! asfdemux ! queue ! MixVideoDecoder ! MixVideoSink An example of playing hardware accelerated H.264/MPEG-4 part 2 video clip using gst-launch: gst-launch filesrc location=./sample.mp4 ! qtdemux ! queue ! MixVideoDecoder ! MixVideoSink An example of playing hardware accelerated DivX video file using gst-launch: gst-launch filesrc location=./sample.avi ! avidemux! queue ! MixVideoDecoder ! MixVideoSink . Going the other way, how would a QML-based app like meego-app-video or meego-app-camera be able to invoke gstreamer options for hardware facilitated capture&conversion presented in "Video Encoding Accelerator Solution for Intel® Atom™ Processor E6xx Series" ( http://download.intel.com/design/intarch/PAPERS/324328.pdf ). Perhaps for the developer, QtGstreamer with a QML interface would be a better option?? http://gstreamer.freedesktop.org/wiki/QtGStreamer http://gkiagia.wordpress.com/2011/01/25/qtgstreamer-0-10-1/ http://piacentini.blog.br/2010/10/qtgstreamer-an-introduction/ Some issues are well summarized here: http://developer.qt.nokia.com/forums/viewthread/4235 ... "Same old story. QtMultimedia on the desktop with QML is not supported in the new SDK. This has been going on for quite a while now. I was once able to get mobility compiled separately and had a QML video element working on Linux. However, I was never able to get that to work on Windows. If you read the release notes carefully you will see that the mobility stuff is supported for Symbian but there is no mention of the desktop. [...] Our best hope for QML multimedia integration is QtGstreamer [gstreamer.freedesktop.org]. You can read more about it from the main developer here [gkiagia.wordpress.com]. Notice in the todo list on the QtGstreamer site that QML integration is listed. It is promising work and there is even mention (on gkiagia’s blog) that it was sponsored by Nokia. [...] They should probably be more clear in their documentation that it is not really supported [...] Still, the QtGstreamer stuff does look pretty promising and if you are impatient you might be able to get a standard QtGstreamer video player working from the example code provided on the site and integrate that player with your QML GUI." -===- Getting back to my attempts at playing a youtube mobile stream on MeeGo 1.2 Netbook: Using gst-launch and playbin2, I can watch a ytoutube video, but the audio is nearly unlistenable, even though it's pretty low res video: ... gst-launch -v playbin2 uri='rtsp://v8.cache4.c.youtube.com/CjYLENy73wIaLQn7vFsQWI6Q0BMYESARFEIJbXYtZ29vZ2xlSARSBXdhdGNoYJmHl8DDx9jPTQw=/0/0/0/video.3gp' ... In investigating getting rid of the audio dropouts I tried all manner of gst-launch parameters but the best advice came from http://labs.myigep.com/index.php/Example_GStreamer_Pipelines ... "The above example experienced dropped audio, please update pipeline when you get it working properly. I had the same problem using my IGEP WLAN interface. After direct connect with Ethernet cable the dropped audio problem was solved." ... Indeed, connecting the Lenovo s10-3t's hardwired network interface rather than the wireless
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
[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] meego-app-video to play live stream
On Tue, Apr 26, 2011 at 10:11 AM, Michelon, Philippe wrote: > Can I launch the qml application meego-app-video to playback a live stream > > (rtsp) and how ? > 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 In contrast my running Fedora's xbmc.org on on MeeGo handles all manner of streamed media from podcasts and internet sites w/ no problems, in any internet format I throw at it. But that's more because I have http://wiki.meego.com/MeeGo-Lem running and all manner of free/nonfree/proprietary codecs installed. For writing one's own apps from scratch, I' having having better luck with MLT: http://lists.meego.com/pipermail/meego-dev/2011-March/482110.html . It appears to have broad uptake by the open source community: http://www.mltframework.org/twiki/bin/view/MLT/Projects Some simple players using MLT in Gnome: http://users.telenet.be/acp/fireswamp/ and Qt: http://sourceforge.net/news/?group_id=96039&id=296772 (which I've built on MeeGo -- needs QML integration though -- anybody want to help?) 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] zypper: Public key is unavailabe problem
On Wed, Apr 20, 2011 at 10:05 PM, Zhao, Juan J wrote: >> $ rpm --import https://fedoraproject.org/static/97A1071F.txt >> > This looks like the root cause. > I install another image, but meet this problem again, sigh > Tried all the other solutions in this mail list, failed > I run "rpm --import file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego", and I can use > zypper again. Indeed. I'm quite glad I found the workaround, as otherwise it would have spelled "את" on the forehead of the proverbial http://wiki.meego.com/MeeGo-Lem (c.f. http://en.wikipedia.org/wiki/Golem ). Today I hit upon an install in a different repo which gave: . warning: /var/cache/zypp/packages/rpmfusion-free-updates/xbmc-10.1-1.fc14.i686.rpm: Header V3 RSA/SHA256 Signature, key ID 865cc9ea: NOKEY The package integrity check failed. This may be a problem with the repository or media. Try one of the following: - just retry previous command - refresh the repositories using 'zypper refresh' - use another installation medium (if e.g. damaged) - use another repository /var/cache/zypp/packages/rpmfusion-free-updates/xbmc-10.1-1.fc14.i686.rpm Public key is unavailable ... To fix, I did: ... $ rpm --import 'http://rpmfusion.org/keys?action=AttachFile&do=get&target=RPM-GPG-KEY-rpmfusion-free-fedora-14' ... Anybody know in what directory rpm is caching this info? That's what seems to have changed across the update that's been breaking this. Directory /etc/pki/rpm-gpg doesn't seem to be used. After the install, I was able to install and run Fedora/RPMFusion's xbmc.org on MeeGo 1.2 :-) Now I have MeeGo TV too :-) -- 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] zypper: Public key is unavailabe problem
I've finally seen and/or met this problem by upgrading today to the latest trunk RPMs libzypp seems to be the cause of the new problems, and the behavior seems to be present in http://download.meego.com/snapshots/1.1.99.2.20110408.2/repos/oss/ia32/packages/i586/libzypp-8.10.2-4.17.i586.rpm and http://download.meego.com/snapshots/1.1.99.0.20110330.3/repos/oss/ia32/packages/i586/libzypp-8.10.2-4.13.i586.rpm as well as the latest libzypp-8.12.1-1.2.i586. It can be fixed, for example, by installing a previous version of libzypp (zypper itself can be up-to-date, only libzypp needs rolling back): zypper in --force http://download.meego.com/snapshots/1.1.90.4.20110222.2/repos/oss/ia32/packages/i586/libzypp-8.10.2-1.35.i586.rpm The latest libzypp causes my http://wiki.meego.com/MeeGo-Lem installs to output warnings, and then die with: .. warning: /var/cache/zypp/packages/fedora/Packages/emacs-htmlize-1.34-4.fc12.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID 97a1071f: NOKEY The package integrity check failed. This may be a problem with the repository or media. Try one of the following: - just retry previous command - refresh the repositories using 'zypper refresh' - use another installation medium (if e.g. damaged) - use another repository /var/cache/zypp/packages/fedora/Packages/emacs-htmlize-1.34-4.fc12.noarch.rpm Public key is unavailable .. With the old libzypp, installs missing the correct key would just issue a warning but continue: .. $ zypper in jack-keyboard Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW package is going to be installed: jack-keyboard 1 new package to install. Overall download size: 34.0 KiB. After the operation, additional 65.0 KiB will be used. Continue? [y/n/?] (y): y Retrieving package jack-keyboard-2.5-5.fc13.i686 (1/1), 34.0 KiB (65.0 KiB unpacked) Retrieving: jack-keyboard-2.5-5.fc13.i686.rpm [done] Installing: jack-keyboard-2.5-5.fc13 [done] Additional rpm output: warning: /var/cache/zypp/packages/fedora/Packages/jack-keyboard-2.5-5.fc13.i686.rpm: Header V3 RSA/SHA256 Signature, key ID 97a1071f: NOKEY .. Because, in my case, I'm importing from Fedora/RPMFusion repositories, the *correct* solution is to prevent this warning by importing the missing "NOKEY" mentioned in the warning (you'll need to do similar for any external MeeGo repos you add to /etc/zypp/repos.d): $ rpm --import https://fedoraproject.org/static/97A1071F.txt After correcting any missing public keys, you can go back to the more stringent/secure/later version of zypper .. $ zypper up libzypp Loading repository data... Reading installed packages... Resolving package dependencies... The following package is going to be upgraded: libzypp 1 package to upgrade. Overall download size: 2.7 MiB. After the operation, additional 6.0 KiB will be used. Continue? [y/n/?] (y): y Retrieving package libzypp-8.12.1-1.2.i586 (1/1), 2.7 MiB (6.8 MiB unpacked) Retrieving: libzypp-8.12.1-1.2.i586.rpm [done (725.2 KiB/s)] Installing: libzypp-8.12.1-1.2 [done] ... Now things install as smoothly as they did before the 04/20/11 upgrade: ... $ zypper in qsynth Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW packages are going to be installed: fluid-soundfont-common fluid-soundfont-gm qsynth 3 new packages to install. Overall download size: 113.9 MiB. After the operation, additional 142.3 MiB will be used. Continue? [y/n/?] (y): y Retrieving package fluid-soundfont-common-3.1-4.fc12.noarch (1/3), 82.0 KiB (79.0 KiB unpacked) Retrieving: fluid-soundfont-common-3.1-4.fc12.noarch.rpm [done] Retrieving package fluid-soundfont-gm-3.1-4.fc12.noarch (2/3), 113.6 MiB (141.5 MiB unpacked) Retrieving: fluid-soundfont-gm-3.1-4.fc12.noarch.rpm [done (1.1 MiB/s)] Retrieving package qsynth-0.3.5-1.fc14.i686 (3/3), 220.0 KiB (712.0 KiB unpacked) Retrieving: qsynth-0.3.5-1.fc14.i686.rpm [done (62.9 KiB/s)] Installing: fluid-soundfont-common-3.1-4.fc12 [done] Installing: fluid-soundfont-gm-3.1-4.fc12 [done] Installing: qsynth-0.3.5-1.fc14 [done] ... 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] zypper: Public key is unavailabe problem
On Fri, Apr 8, 2011 at 4:02 AM, Zhao, Juan J wrote: > I meet a problem when using "zypper install xxx"command. zypper download > all the needed pakcages but do not install them and export one > note:"xxx.rpm Public key is unavailabe". Is there anybody meet the same > problem? You can work around this issue by adding the following to your .repo file ##NPM: prevent "Signature verification failed for file 'repomd.xml' from repository 'oss'." gpgcheck=0 This can also be specified on zypper command line: --no-gpg-checks Ignore GPG check failures and continue. If a GPG issue occurs when using this option zypper prints and logs a warning and automatically continues without interrupting the operation. Use this option with caution, as you can easily overlook security problems by using it. -- 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] meego tablet on viewpad 10
On Thu, Apr 7, 2011 at 6:43 PM, Niels Mayer wrote: > (1) I have that problem on lenovo s10-3t after upgrading to pinetrail > kernel. The tradeoff seems to be that the wired network works stably, > which is what i wanted in the first place, a simple, fast wired > network with static IP :-) (still testing to see if it's actually > stable). The problem is that "/lib/modules/2.6.38-7.1-adaptation-pinetrail/kernel/drivers/net/wireless/ath/ath9k//ath9k.ko is missing. Compare to previously installed kernel: ROOT-meegolem-8-~> find /lib/modules -name '*ath9k*' /lib/modules/2.6.37-7.28/kernel/drivers/net/wireless/ath/ath9k /lib/modules/2.6.37-7.28/kernel/drivers/net/wireless/ath/ath9k/ath9k.ko /lib/modules/2.6.37-7.28/kernel/drivers/net/wireless/ath/ath9k/ath9k_htc.ko /lib/modules/2.6.37-7.28/kernel/drivers/net/wireless/ath/ath9k/ath9k_common.ko /lib/modules/2.6.37-7.28/kernel/drivers/net/wireless/ath/ath9k/ath9k_hw.ko /lib/modules/2.6.38-7.1-adaptation-pinetrail/kernel/drivers/net/wireless/ath/ath9k /lib/modules/2.6.38-7.1-adaptation-pinetrail/kernel/drivers/net/wireless/ath/ath9k/ath9k_common.ko /lib/modules/2.6.38-7.1-adaptation-pinetrail/kernel/drivers/net/wireless/ath/ath9k/ath9k_htc.ko /lib/modules/2.6.38-7.1-adaptation-pinetrail/kernel/drivers/net/wireless/ath/ath9k/ath9k_hw.ko Which means the system comes up like this ROOT-meegolem-6-~> lsmod Module Size Used by iptable_nat13101 0 nf_nat 24681 1 iptable_nat uvcvideo 62814 0 serio_raw 12990 0 joydev 17378 0 ideapad_laptop 13262 0 battery14012 0 Whereas it used to come up with these loaded. ath9k 65616 0 ath9k_common 1977 1 ath9k ath9k_hw 243231 2 ath9k,ath9k_common Now, "modprobe ath9k" fails due to the missing .ko. Regarding the still working wired network... unfortunately, it's no more stable than previous... It loses ability to route to local network because the network will eventually disconnect and come back with a netmask of 255.255.255.255 ... of course, unless you're testing connections on the local /24 network you'll never see this issue; just firing up a web browser to an external site -- the networking will appear to work correctly. Except to any local services or networked disc servers, which will appear to go offline shortly after setting up the wired network and transferring some data... -- Niels http://nielsmayer.com PS: is there any reason why other modules are missing as well, e.g. snd-hrtimer.ko, snd-hwdep.ko, snd.ko, snd-page-alloc.ko, snd-pcm.ko, snd-timer.ko /lib/modules/2.6.38-7.1-adaptation-pinetrail/kernel/sound/core: drwxr-xr-x 1 root root72 2011-04-07 18:10 seq/ -rwxr--r-- 1 root root 24736 2011-04-06 09:34 snd-rawmidi.ko* ___ 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 tablet on viewpad 10
On Wed, Apr 6, 2011 at 5:53 PM, Stylianou, Costas wrote: > After the kernel upgrade WiFi has stopped working :(, any ideas anyone? > > @Baozi - did you see the same problem on the viewpad 10? (1) I have that problem on lenovo s10-3t after upgrading to pinetrail kernel. The tradeoff seems to be that the wired network works stably, which is what i wanted in the first place, a simple, fast wired network with static IP :-) (still testing to see if it's actually stable). Booting back to old kernel gives "working" wireless, with all the old bugs. (2) Why this: Apr 7 18:29:10 meegolem klogd: [0.00] Warning only 895MB will be used. Apr 7 18:29:10 meegolem klogd: [0.00] Use a HIGHMEM enabled kernel. Apr 7 18:29:10 meegolem klogd: [0.00] found SMP MP-table at [c00f7ca0] f7ca0 (3) still missing snd-hrtimer.ko, snd-hwdep.ko, snd.ko, snd-page-alloc.ko, snd-pcm.ko, snd-timer.ko /lib/modules/2.6.38-7.1-adaptation-pinetrail/kernel/sound/core: drwxr-xr-x 1 root root72 2011-04-07 18:10 seq/ -rwxr--r-- 1 root root 24736 2011-04-06 09:34 snd-rawmidi.ko* 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] meego tablet on viewpad 10
On Thu, Apr 7, 2011 at 12:54 AM, Stylianou, Costas wrote: > I did not need to build the RPM (this case) Kernel, I just added the repo > that contains the kernel-adaptation-pinetrail, like this: > Zypper ar http://download.meego.com/live/devel:/kernel/Trunk/devel:kernel.repo > And then zypper install kernel-adaptation-pinetrail. Thanks for the suggestion. Will that "do the right thing" and leave me with a bootable system, or will I need to do some specal recovery from a live-image afterwards? Will it overwrite the old kernel? Alternately, does it do like Grub on fedora where you can still boot into the old kernel in case there's a problem with the new? Also, are there other packages that need upgrade? syslinux-4.00-3.5.i586 syslinux-extlinux-4.00-3.5.i586 are in http://download.meego.com/live/devel:/base/Trunk/i586/ whereas I've got syslinux-4.00-1.9.i586 syslinux-extlinux-4.00-1.9.i586 installed. Should those be upgraded at the same time the new kernel is installed? Looks like this might be the answer I was looking for in See http://lists.meego.com/pipermail/meego-dev/2011-April/482503.html , where I asked "Does installing http://download.meego.com/live/devel:/kernel/Trunk/i586/kernel-2.6.37.2-256.2.i586.rpm via zypper actually do all the right stuff w/r/t updating the boot information for the new kernel? I also skipped updating syslinux-extlinux (& syslinux dependency) as it messes with /boot ...If I want to avoid a reinstall, what's the right way to upgrade a "live" meego system to the latest "trunk" kernel?" What happens if installing this "kernel-adaptation-pinetrail" kernel on the this now almost 1.2 "trunk" netbook -- will I still be able to run the existing netbook UX? Thanks, -- 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] how to run meego-ux's meego-app-camera on MeeGo 1.2 Netbook?
re: hint to do $ mv /usr/lib/gstreamer-0.10/libgstcamerabin.so /usr/lib/gstreamer-0.10/libgstcamerabin.so.bak WORKSFORME!! Thanks! ... meegolem-120-.../Pictures/Camera> td -rw-r--r-- 1 npm npm 230556 2011-04-05 17:39 Tue-Apr-5-17:39:58-2011.jpg -rw-r--r-- 1 npm npm 234552 2011-04-05 17:39 Tue-Apr-5-17:39:54-2011.jpg -rw-r--r-- 1 npm npm 231908 2011-04-05 17:39 Tue-Apr-5-17:39:53-2011.jpg -rw-r--r-- 1 npm npm 221608 2011-04-05 17:39 Tue-Apr-5-17:39:44-2011.jpg ... ## NB: recorded video is pretty lurchy/jerky but at least it's ## recognizable ## as video. Does the lurching happen each ## time the app checks for free space (see log below) which ## might be a bad idea on a uniprocessor/ht like this n455 meegolem-134-.../Videos/Camera> ffmpeg -i Tue-Apr-5-17:40:04-2011.ogg FFmpeg version SVN-r24044, Copyright (c) 2000-2010 the FFmpeg developers built on Jul 21 2010 15:07:15 with gcc 4.5.0 20100716 (Red Hat 4.5.0-3) [...] libavutil 50.20. 0 / 50.20. 0 libavcodec52.79. 1 / 52.79. 1 libavformat 52.73. 0 / 52.73. 0 libavdevice 52. 2. 0 / 52. 2. 0 libavfilter1.20. 1 / 1.20. 1 libswscale 0.11. 0 / 0.11. 0 libpostproc 51. 2. 0 / 51. 2. 0 [theora @ 0x96d4d00] 7 bits left in packet 82 Input #0, ogg, from 'Tue-Apr-5-17:40:04-2011.ogg': Duration: 00:00:35.60, start: 0.00, bitrate: 418 kb/s Stream #0.0: Video: theora, yuv420p, 1280x1024, 5 tbr, 5 tbn, 5 tbc Stream #0.1: Audio: vorbis, 44100 Hz, mono, s16, 120 kb/s ... meegolem-103-~> meego-qml-launcher --opengl --fullscreen --app meego-app-camera Adding Master Pointer: Virtual core pointer ( 2 ) Skipping non-Touch device: Virtual core XTEST pointer ( 4 ) Adding ATTACHED touch device: Cando Corporation Cando 10.1 Multi Touch Panel with Controller ( 11 ) Skipping non-Touch device: SynPS/2 Synaptics TouchPad ( 14 ) loaded the Generic plugin Loaded the MeeGo sensor plugin Request for interface not granted... Request for interface not granted... Warning: Object::connect: No such signal QXIMInputContext::inputMethodAreaChanged(QRect) Warning: Object::connect: No such signal LauncherApp::localeSettingsChanged() Warning: Object::connect: (sender name: 'meego-qml-launcher') Warning: Object::connect: No such signal LauncherApp::windowListUpdated(QList) Warning: Object::connect: (sender name: 'meego-qml-launcher') Debug: Instantiating VolumeControlPrivate Debug: Settings* Debug: Flash Mode: 2 Debug: Capture Mode: 1 Debug: "/dev/video0" "Lenovo EasyCamera" Debug: "/dev/video0" "Lenovo EasyCamera" Debug: Setting camera to "/dev/video0" Debug: Supported maximum optical zoom 1 Debug: Supported maximum digital zoom 1 Debug: Metadata is not available Debug: Audio input: "alsa:null" - "Discard all samples (playback) or generate zero samples (capture)" Debug: Audio input: "alsa:pulse" - "PulseAudio Sound Server" Debug: Audio input: "alsa:default" - "Default" Debug: Audio input: "alsa:front:CARD=Intel,DEV=0" - "HDA Intel, CONEXANT Analog Front speakers" Debug: Audio input: "alsa:surround40:CARD=Intel,DEV=0" - "HDA Intel, CONEXANT Analog 4.0 Surround output to Front and Rear speakers" Debug: Audio input: "alsa:surround41:CARD=Intel,DEV=0" - "HDA Intel, CONEXANT Analog 4.1 Surround output to Front, Rear and Subwoofer speakers" Debug: Audio input: "alsa:surround50:CARD=Intel,DEV=0" - "HDA Intel, CONEXANT Analog 5.0 Surround output to Front, Center and Rear speakers" Debug: Audio input: "alsa:surround51:CARD=Intel,DEV=0" - "HDA Intel, CONEXANT Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers" Debug: Audio input: "alsa:surround71:CARD=Intel,DEV=0" - "HDA Intel, CONEXANT Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers" Debug: Audio input: "pulseaudio:" - "PulseAudio device." Debug: Default source: "alsa:null" Debug: Using default resolution Debug: Frame rate: 5 Debug: Frame rate: 10 Debug: Frame rate: 15 Debug: Using default FPS Debug: Video resolution: 160 x 120 Debug: Video resolution: 320 x 240 Debug: Video resolution: 640 x 400 Debug: Video resolution: 640 x 480 Debug: Video resolution: 1280 x 720 Debug: Video resolution: 1280 x 800 Debug: Video resolution: 1280 x 1024 Debug: Codec: "video/h264" Debug: Codec: "video/xvid" Debug: Codec: "video/mpeg4" Debug: Codec: "video/mpeg1" Debug: Codec: "video/mpeg2" Debug: Codec: "video/theora" Debug: Container: "qtmux" Debug: Container: "matroska" Debug: Container: "ogg" Debug: Container: "mp4" Debug: Container: "wav" Debug: Container: "quicktime" Debug: Container: "avi" Debug: Container: "3gpp" Debug: Container: "flv" Debug: Container: "amr" Debug: Container: "asf" Debug: Container: "dv" Debug: Container: "mpeg" Debug: Container: "vob" Debug: Container: "mpegts" Debug: Container: "3g2" Debug: Container: "3gp" Debug: Container: "raw" Debug: Selected container: "ogg" Debug: Sorted resolution: 1280 x 1024 Debug: So
Re: [MeeGo-dev] how to run meego-ux's meego-app-camera on MeeGo 1.2 Netbook?
On Sun, Apr 3, 2011 at 4:33 PM, Arjan van de Ven wrote: > h wonder why you don't run the tablet/etc UX entirely The tablet-UX probably makes good sense on a compatible tablet, with larger surface, better edge-of-screen & button ergonomics, more memory, higher resolution, faster processors, etc. e.g., something like http://www.amazon.com/dp/B004HKIIFI/ (ASUS EEE Slate 12.1" tablet PC). A platform like that would be good incentive to use the tablet UX. (Now accepting all donations :-) ). A better reason is the latest 1.2 Netbook UX worksforme, whereas the Tablet-UX still has some issues that need to be worked out, e.g., http://lists.meego.com/pipermail/meego-dev/2011-April/482477.html where Costas Stylianou wrote: .. You are correct, the problem is once you boot to the MeeGo Tablet UX image you lose touch clicks, I believe that the touch driver has been tuned for the ExoPC only which probably has a different touch controller to your device. If you switch to the netbook build touch works very well. [...] ... My goal with the camera app is a codebase with portability to all MeeGo platforms (doesn't IVI need a touch-based QML camera app too?). Given the reprioritization of the handset, I still hope to work on some variant of http://code.google.com/p/ytd-meego/wiki/CitizenJournalismWithYoutubeDirectForMeego but want it to run on all platforms that its Qt-based infrastructure would target, not just the handset. Plus, it's a lot easier to develop on the netbook, snarfling up whatever tools and devel libs using http://wiki.meego.com/MeeGo-Lem , with the promise that eventually I'll be able to run the same code on multiple MeeGo targets. and more than just ia32 processors. I'm seeking to evaluate meego-app-camera versus http://code.google.com/p/ytd-meego/wiki/CitizenJournalismWithYoutubeDirectForMeego#Reusing_QtMobility_1.2%27s_%22declarative_camera%22_Exa ... the first step of which is getting meego-app-camera running on a generic MeeGo platform such as the Lenovo s10-3t. The second would be getting it running on the n900 when all the codecs and camera functionality support video recording. If that includes taking all the pieces apart and putting them back together again to understand the dependencies, then so be it... -- 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] how to run meego-ux's meego-app-camera on MeeGo 1.2 Netbook?
I got a little farther with bringing up meego-ux camera on Netbook 1.2
"alpha". After seeing various warnings regarding missing gstreamer
components and failures in meego-app-music and meego-app-video related
to dbus message parse failures, I decided to upgrade this highly
updated 2/22/11 image to the latest "base" packages from Trunk:
$ zypper ar http://download.meego.com/live/devel:/base/Trunk/devel:base.repo
$ zypper clean --all ; zypper --gpg-auto-import-keys refresh
## removed dangerous-to-upgrade packages via hand-edited from list
output by "zypper up"
$ zypper update -acl alsa-lib alsa-lib-devel alsa-plugins-pulseaudio
alsa-utils aspell atk atk-devel augeas-libs autoconf automake avahi
avahi-glib avahi-gobject avahi-ui basesystem bash binutils btrfs-progs
bzip2 bzip2-libs cairo cairo-devel chkconfig cmake connman
connman-test ConsoleKit ConsoleKit-libs ConsoleKit-x11 coreutils cpio
cpp cups cups-libs curl cvs db4 db4-utils deltarpm desktop-file-utils
device-mapper device-mapper-libs diffutils docbook-dtds
docbook-style-dsssl docbook-style-xsl docbook-utils dosfstools ed
elfutils-libelf expat fastinit file file-libs findutils flac
flac-devel fontconfig fontconfig-devel fontpackages-filesystem
foomatic freetype freetype-devel fuse fuse-libs gamin gawk gcc gcc-c++
gdb gdb-gdbserver gdbm geoclue geoclue-devel gettext-devel
gettext-libs ghostscript-fonts giflib glib2 glib2-devel gmp
gnome-doc-utils gnome-doc-utils-stylesheets gnome-mime-data gnupg2
grep groff grubby gzip hicolor-icon-theme hwdata icu info iproute
iptables iputils jasper jasper-libs kbd keyutils keyutils-libs lcms
lcms-libs less libacl libarchive libasyncns libattr libblkid libcap
libcroco libcurl libdaemon libdrm libexif libexif-devel libffi
libfontenc libgcc libgcrypt libglade2 libgnome-keyring
libgnome-keyring-devel libgomp libgpg-error libgudev1 libical
libical-devel libICE libICE-devel libicu libidn libjpeg libjpeg-devel
libksba liblua libmng libnl libnotify libpciaccess libpng libpng-devel
libpthread-stubs libsamplerate libsamplerate-devel libSM libSM-devel
libsndfile libsoup libsoup-devel libstdc++ libstdc++-devel libtasn1
libtasn1-devel libtheora libtheora-devel libtiff libtool libtool-ltdl
libudev libusb libuser libuser-python libutempter libuuid
libuuid-devel libva libvisual libxml2-python libxslt libzypp
linux-firmware logrotate m4 mailcap make MAKEDEV meego-app-music
meego-app-video meego-ux-components meego-ux-components-devel
mesa-dri-i915-driver mesa-dri-i965-driver mesa-dri-swrast-driver
mesa-libEGL mesa-libEGL-devel mesa-libGL mesa-libGL-devel
mesa-libGLESv2 mesa-libGLESv2-devel mesa-libGLU mesa-libGLU-devel
mesa-libOpenVG mesa-libOpenVG-devel mesa-libOSMesa
mesa-libOSMesa-devel mingetty minizip mkinitrd mtools ncurses
ncurses-base ncurses-libs net-tools nspr nss nss-mdns
nss-softokn-freebl nss-sysinit openjade opensp openssh openssh-clients
openssh-server pam pango pango-devel parted passwd patch pciutils
pixman pixman-devel pkgconfig pm-utils polkit popt prelink procps
psmisc pth pycairo pycairo-devel pygobject2 pygobject2-codegen
pygobject2-devel pygobject2-doc pyparted rarian rarian-compat rhpl
rootfiles rpm-python satsolver-tools sed sgml-common shadow-utils
shared-mime-info speex speex-devel sqlite sqlite-devel sreadahead
ssmtp startup-notification strace sudo swig sysklogd tar time tzdata
udev unzip upower urw-fonts usbutils usleep util-linux-ng uxlaunch
vim-minimal wget wireless-tools wpa_supplicant xcb-util xdg-utils
xkeyboard-config xml-common xorg-x11-drv-intel xorg-x11-server
xorg-x11-server-common xorg-x11-server-Xorg
xorg-x11-server-Xorg-setuid xterm xz xz-libs xz-lzma-compat yasm zip
zlib zlib-devel zypper linux-firmware sysvinit sysvinit-tools
## in case you want a working GUI after reboot.
$ zypper remove mce qmsystem
## ("your mileage may vary")
$ reboot
~300 package updates later ... now various things work better than
they did before, and nothing seems to work worse, although sreadahead
complains of 15 errors instead of 1 or 2 (?). More importantly, now
the wired network stays stable for up to 12 hours at a time --
amazing! And connman isn't constantly connecting and disconnecting on
the wireless.
Do I need to upgrade to the latest kernel in order to get the camera
to actually capture a photo or video? Does installing
http://download.meego.com/live/devel:/kernel/Trunk/i586/kernel-2.6.37.2-256.2.i586.rpm
via zypper actually do all the right stuff w/r/t updating the boot
information for the new kernel? I also skipped
updating syslinux-extlinux (& syslinux dependency) as it messes with
/boot ...If I want to avoid a reinstall, what's the right way to
upgrade a "live" meego system to the latest "trunk" kernel?
...
Unlike my previous attempt, now the camera application launches its
GUI; but, the video preview/viewfinder is "blank", and it cannot
capture any photos or videos.
The main problem now is:
"g_object_set_valist: object class `GstMcSrc' has no property named `device'"
Note I have the follow
[MeeGo-dev] how to run meego-ux's meego-app-camera on MeeGo 1.2 Netbook?
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-notes meego-app-im meego-app-email meego-app-conacts meego-app-calendar meego-app-calculator meego-app-browser meego-app-clocks meego-ux-panels meego-ux-panels-photos meego-ux-panels-friends meego-ux-panels-music meego-ux-panels-mytablet meego-ux-panels-video meego-ux-panels-web meego-ux-panels-meta-tablet meego-ux-appgrid meego-ux-content meego-ux-content-socialweb which also installs dependencies: meego-handset-sound-theme meegolabs-ux-components meego-qml-launcher meego-ux-media meego-ux-media-models meego-ux-theme mkcal mlite qtgst-qmlsink telepathy-farstream I attempt to launch these apps with $ meego-qml-launcher --app which looks for /usr/share//main.qml e.g. meego-qml-launcher --opengl --fullscreen --app meego-app-calculator meego-qml-launcher --opengl --fullscreen --app meego-app-calendar meego-qml-launcher --opengl --fullscreen --app meego-app-camera meego-qml-launcher --opengl --fullscreen --app meego-app-clocks meego-qml-launcher --opengl --fullscreen --app meego-app-contacts meego-qml-launcher --opengl --fullscreen --app meego-app-email meego-qml-launcher --fullscreen --opengl --app meego-app-im meego-qml-launcher --opengl --fullscreen --app meego-app-music meego-qml-launcher --opengl --fullscreen --app meego-app-notes meego-qml-launcher --opengl --fullscreen --app meego-app-photos meego-qml-launcher --opengl --fullscreen --app meego-app-tasks meego-qml-launcher --opengl --fullscreen --app meego-app-video meego-qml-launcher --opengl --fullscreen --app meego-ux-appgrid meego-qml-launcher --opengl --fullscreen --app meego-ux-app-photos meego-qml-launcher --opengl --fullscreen --app meego-ux-panels meego-qml-launcher --opengl --fullscreen --app meego-ux-settings Although many of the simple tablet-ux apps work on the Lenovo s10-3t running 1.2 netbook "alpha", the one I really want to re-use (for http://code.google.com/p/ytd-meego/wiki/CitizenJournalismWithYoutubeDirectForMeego ) is meego-app-camera. Unfortunately, when I run it, I get the following: -- is this a bug or am I dong something wrong ? ... $ meego-qml-launcher --opengl --fullscreen --app meego-app-camera Adding Master Pointer: Virtual core pointer ( 2 ) Skipping non-Touch device: Virtual core XTEST pointer ( 4 ) Adding ATTACHED touch device: Cando Corporation Cando 10.1 Multi Touch Panel with Controller ( 11 ) Skipping non-Touch device: SynPS/2 Synaptics TouchPad ( 14 ) loaded the Generic plugin Loaded the MeeGo sensor plugin Request for interface not granted... Request for interface not granted... Warning: Object::connect: No such signal QXIMInputContext::inputMethodAreaChanged(QRect) Warning: Object::connect: No such signal LauncherApp::localeSettingsChanged() Warning: Object::connect: (sender name: 'meego-qml-launcher') Warning: Object::connect: No such signal LauncherApp::windowListUpdated(QList) Warning: Object::connect: (sender name: 'meego-qml-launcher') Debug: Instantiating VolumeControlPrivate Debug: Settings* Debug: Flash Mode: 0 Debug: Capture Mode: 0 Debug: "/dev/video0" "Lenovo EasyCamera" Debug: "/dev/video0" "Lenovo EasyCamera" Debug: Setting camera to "/dev/video0" Debug: Camera caps: 64 Debug: Supported maximum optical zoom 1 Debug: Supported maximum digital zoom 10 Debug: Metadata is not available Debug: Audio input: "alsa:null" - "Discard all samples (playback) or generate zero samples (capture)" Debug: Audio input: "alsa:pulse" - "PulseAudio Sound Server" Debug: Audio input: "alsa:default" - "Default" Debug: Audio input: "alsa:front:CARD=Intel,DEV=0" - "HDA Intel, CONEXANT Analog Front speakers" Debug: Audio input: "alsa:surround40:CARD=Intel,DEV=0" - "HDA Intel, CONEXANT Analog 4.0 Surround output to Front and Rear speakers" Debug: Audio input: "alsa:surround41:CARD=Intel,DEV=0" - "HDA Intel, CONEXANT Analog 4.1 Surround output to Front, Rear and Subwoofer speakers" Debug: Audio input: "alsa:surround50:CARD=Intel,DEV=0" - "HDA Intel, CONEXANT Analog 5.0 Surround output to Front, Center and Rear speakers" Debug: Audio input: "alsa:surround51:CARD=Intel,DEV=0" - "HDA Intel, CONEXANT Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers" Debug: Audio input: "alsa:surround71:CARD=Intel,DEV=0" - "HDA Intel, CONEXANT Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers" Debug: Audio input: "pulseaudio:" - "PulseAudio device." Debug: Default source: "alsa:null" Debug: Using default resolution Debug: Using default FPS Debug: Codec: "video/theora" Debug: Codec: "video/mpeg2" Debug: Codec: "video/mpeg1" Debug: Codec: "video/mjpeg" Debug: Codec: "video/VP8" Debug: Codec: "video/h261" Debug: Container: "mp4" Debug: Container: "ogg" Debug: Container:
Re: [MeeGo-dev] Updating 1.2 Netbook to gain facebook, lose twitter, and fix a major gnome lib bug
The reason why the hack suggested in my previous mail used Fedora, was because I was using LEM ( http://wiki.meego.com/MeeGo-Lem ) repository hacks to get it from Fedora. Unfortunately the Fedora twitter key doesn't work, but the original one that worked on my (by now) highly modified 20110222.2 image did. So the trick is to install both the update and the original simultaneously: sudo rpm --force -ivh http://download.meego.com/live/devel:/ux:/netbook/Trunk/i586/libsocialweb-keys-1.2-5.1.i586.rpm sudo rpm --force -ivh http://repo.meego.com/MeeGo/builds/1.1.90/1.1.90.4.20110222.2/repos/oss/ia32/packages/i586/libsocialweb-keys-1- And then do (from console/remote term) sudo init 3 sudo init 5 to restart UX. Now Twitter works again, and so does Facebook. The installed keys: meegolem-123-~> ll -t /usr/share/libsocialweb/keys/ total 0 -rw-r--r-- 1 root root 66 2011-03-28 05:01 facebook -rw-r--r-- 1 root root 66 2011-03-28 05:01 smugmug -rw-r--r-- 1 root root 33 2011-03-28 05:01 twitpic -rw-r--r-- 1 root root 33 2011-01-06 21:01 lastfm -rw-r--r-- 1 root root 64 2011-01-06 21:01 twitter 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] Updating 1.2 Netbook to gain facebook, lose twitter, and fix a major gnome lib bug
On Fri, Apr 1, 2011 at 9:28 AM, James Ausmus wrote: > This is due to the new Twitter ToS - there's no code functionality > removed, we're just not currently allowed to ship an official MeeGo > Twitter API key, so the libsocialweb Twitter plugin, when it looks for > the key at /usr/share/libsocialweb/keys/twitter, doesn't find it, and > then unloads itself. Same kind of deal for Last.fm - both would work > fine if an API key existed at the proper location. Thanks for the suggestion. Attempting hack below, I now have Last.fm, SmugMug, Twitter, and Facebook listed in "my web accounts". I had to re-oauth in facebook again, but the twitter account will not allow login with valid user/pw .. The status app shows a "Twitter" column but when selected, says "Unable to update status. The service may be unavailable or your password could be wrong." So I guess the key I got from Fedora doesn't work, or got invalidated by Twitter. Or is something else wrong? So where is the unofficial MeeGO Twitter API key? Is a MeeGo twitter client no longer possible due to Twitter's ToS? .. $ rpm -ivh http://mirrors.servercentral.net/fedora/releases/14/Everything/i386/os/Packages/libsocialweb-keys-0.24.9-3.fc14.1.noarch.rpm $ rpm -ivh http://download.meego.com/live/devel:/ux:/netbook/Trunk/i586/libsocialweb-keys-1.2-5.1.i586.rpm meegolem-118-~> ll /usr/share/libsocialweb/keys/ total 12 -rw-r--r-- 1 root root 92 2010-10-08 14:40 digg -rw-r--r-- 1 root root 66 2011-03-28 05:01 facebook -rw-r--r-- 1 root root 50 2010-10-08 14:40 flickr -rw-r--r-- 1 root root 33 2010-10-08 14:40 lastfm -rw-r--r-- 1 root root 98 2010-10-08 14:40 myspace -rw-r--r-- 1 root root 66 2011-03-28 05:01 smugmug -rw-r--r-- 1 root root 33 2011-03-28 05:01 twitpic -rw-r--r-- 1 root root 65 2010-10-08 14:40 twitter ... -- Niels ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Updating 1.2 Netbook to gain facebook, lose twitter, and fix a major gnome lib bug
https://bugs.meego.com/show_bug.cgi?id=14852 .. corrected version of bug report comment I resolved this issue by installing meego-facebook-plugins-1.1.2-6.3.i586.rpm . Now meego 1.2 facebook works just like it did back in 1.0 $ zypper ar http://download.meego.com/live/devel:/ux:/netbook/Trunk/devel:ux:netbook.repo $ zypper clean --all ; zypper --gpg-auto-import-keys refresh $ zypper in meego-facebook-plugins Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW package is going to be installed: meego-facebook-plugins 1 new package to install. Overall download size: 39.0 KiB. After the operation, additional 86.0 KiB will be used. Continue? [y/n/?] (y): y Retrieving package meego-facebook-plugins-1.1.2-6.3.i586 (1/1), 39.0 KiB (86.0 KiB unpacked) Retrieving: meego-facebook-plugins-1.1.2-6.3.i586.rpm [done] Installing: meego-facebook-plugins-1.1.2-6.3 [done] $ zypper up Loading repository data... Reading installed packages... [...] The following packages are going to be upgraded: anerley bisho clutter clutter-gtk evolution evolution-data-server evolution-libs glib2 glib2-devel gnome-bluetooth gnome-bluetooth-libs gnome-bluetooth-meego gnome-control-center-netbook gnome-settings-daemon gtkhtml3 gvfs gvfs-fuse gvfs-gphoto2 gvfs-obexftp gvfs-smb gvfs-trash jana libchamplain libsocialweb libsocialweb-devel libsocialweb-keys meego-cursor-theme meego-menus meego-netbook-theme meego-panel-applications meego-panel-datetime meego-panel-devices meego-panel-myzone meego-panel-pasteboard meego-panel-people meego-panel-status meego-panel-web meego-panel-zones meego-sound-theme mutter mutter-netbook mutter-netbook-branding-upstream mx nautilus nautilus-extensions netbook-icon-theme pcre rest rest-devel 49 packages to upgrade. Overall download size: 58.7 MiB. After the operation, additional 378.0 KiB will be used. .. Running these updates didn't seem to harm much, and fixed a showstopper bug (*). I did have to reauth with facebook using a different auth scheme, and afterwards, I noticed no 'twitter' capability. Just a new service "SmugMug" and Last.FM removed Note that just updating 'meego-facebook-plugins' gives FB chat capability, but with the above updates (probably bisho + meego-panel-web and/or libsocialweb??) you also get the web panel updating w/ FB status. However, that seems to remove twitter from the web accounts Any suggestions on getting twitter back? Or is this part of Twitter's cracking down on third party apps? (*): Also fixed, https://bugs.meego.com/show_bug.cgi?id=12687#c7 probably by updating glib2-2.28.0-6.1.i586.rpm 21-Feb-2011 20:53 2.3M glib2-debuginfo-2.28.0-6.1.i586.rpm 21-Feb-2011 20:53 3.6M glib2-devel-2.28.0-6.1.i586.rpm 21-Feb-2011 20:53 2.0M from glib2-2.28.0-1.1.i586.rpm 21-Feb-2011 19:47 2.3M glib2-devel-2.28.0-1.1.i586.rpm 21-Feb-2011 19:47 2.0M glib2-static-2.28.0-1.1.i586.rpm 21-Feb-2011 19:47 1.5M Now applications containing tooltips launch quickly. https://bugs.meego.com/show_bug.cgi?id=12687 is miscategorized -- it affects all gnome apps -- and a major showstopper. With the updated glibs, all gnome based apps with tooltips now launch quickly, independent of which display they are rendered to. For example, the emacs editor can now launch to a remote display almost instantaneously. Without the updated libraries, emacs would take minutes to launch, unless the following settings in ~/.emacs is used to turn off tooltips: (tooltip-mode nil) (tool-bar-mode nil) (menu-bar-mode nil) Unlike emacs, gnome-terminal , libreoffice, and any other gnome app with tooltips has no easy way to turn off the feature, and thus can take a very long time to launch. Give the behavior seen on a remote X display with any gnome-based app, the analysis that this is a compositor/clutter/mutter issue in https://bugs.meego.com/show_bug.cgi?id=12687#c8 is not correct. See also http://forum.meego.com/showpost.php?p=18798&postcount=25 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] Insights into network flakyness in MeeGo 1.2 Netbook
On Wed, Feb 23, 2011 at 7:42 PM, Niels Mayer wrote: > https://bugs.meego.com/show_bug.cgi?id=13778 > Bug 13778 - Wireless connection loses "router" setting for Static-IP > https://bugs.meego.com/show_bug.cgi?id=13780 > Bug 13780 - Wired connection stops working when transferring lots of data Also: https://bugs.meego.com/show_bug.cgi?id=13653 Bug 13653 nor, Medium, 1.3, sameo, ASSI, ConnMan applet disconnect does not disconnect ipv6 https://bugs.meego.com/show_bug.cgi?id=5202 Bug 5202 - Connman deletes the (2nd) static IP while renewing DHCP lease https://bugs.meego.com/show_bug.cgi?id=11083 Bug 11083 - [REG] "Ethernet/Wifi is not available" in Control Panel https://bugs.meego.com/show_bug.cgi?id=9007 Bug 9007 - [REG]network notification pop up about every 5 minutes https://bugs.meego.com/show_bug.cgi?id=7529 Bug 7529 - [REG]network notification pop up about every 5 minutes etc. Clued by https://bugs.meego.com/show_bug.cgi?id=13778#c34 , I got tired of waiting to see connman 0.71 in the images, so googled for an RPM and found http://download.meego.com/live/devel:/connectivity:/latest/Trunk/i586/ Here's how I installed it and a few potential dependencies (?). > $ sudo zypper ar > http://download.meego.com/live/devel:/connectivity:/latest/Trunk > meego-latest-connectivity > Adding repository 'meego-latest-connectivity' [done] > Repository 'meego-latest-connectivity' successfully added > Enabled: Yes > Autorefresh: No > URI: http://download.meego.com/live/devel:/connectivity:/latest/Trunk/i586/ > $ ##following needed only if you've done, e.g., 'sudo zypper mr --priority 2 > oss' > $ sudo zypper mr --priority 1 meego-latest-connectivity > $ sudo zypper clean --all > $ sudo zypper --gpg-auto-import-keys --no-gpg-checks refresh > $ zypper up bluez bluez-libs connman connman-test ofono ofono-test The above update installs connman-0.72-1.1.i586 connman-test-0.72-1.1.i586 bluez-4.91.23.g6f7add5-1.1.i586 bluez-libs-4.91.23.g6f7add5-1.1.i586 ofono-0.45.134.gb2e3a47-1.1.i586 ofono-test-0.45.134.gb2e3a47-1.1.i586. At least connman-0.72 seems to fix a lot of problems with the networking -- I can actually use the wired network for the first time since I installed 1.2. My issues with static IP on both wired and wireless ipv4 networks seems to have been mostly resolved. I'm still seeing the wired connection disconnect from the local network after several hours, even though it can route to the internet. The GUI connection manager lists the subnet mask as being "255.255.255.255" in this condition. When it's corrected back to a /24 netmask, it'll either be uncorrectable until next reboot, or it manages to reconnect and just works. The original problem in connman 0.69 (in *all* meego 1.2 netbook/tablet releases) of garbage text (as if memory error) showing up in the static IP "Router" field doesn't happen anymore. Nor do some of the other disconnections and connection manager errors I've been experiencing. Unfortunately, even the latest release still includes the buggy connman 0.69: http://repo.meego.com/MeeGo/builds/1.1.90/1.1.99.0.20110330.3/repos/oss/ia32/packages/i586/ With the updated connman, a suspend/resume cycle (e.g. closing lid on lenovo s10-3t) allows the wired network to almos survive At least the workaround to accidentally closing the cover doesn't mean rebooting ... It only requires correcting the "subnet mask" field back to "255.255.255.0" from "255.255.255.255" ... The same thing seems to be required on each boot, requiring the network mask to be corrected from .255 to .0 . --- Any suggestions on keeping this fixed to the correct value?? Attempting to fix "the easy way" aka: $ sudo zypper in http://download.meego.com/live/devel:/ux:/netbook/Trunk/i586/meego-panel-networks-1.3.2-33.1.i586.rpm ... didn't fix the netmask resetting problem on suspend or reboot (not sure why it would, but wanted to replace as much of the buggy networking stuff w/ fixes). -- 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] Candidate specification for a generic video player from the TV list
FYI, I just proposed a BOF that will partially be on this topic from an app-developers pt-of-view: http://sf2011.meego.com/program/sessions/bof-developing-qml-youtube-api-and-internet-video BOF: Developing in QML for YouTube API and Internet video ... [...] demonstrate powerful techniques for working with YouTube feeds and for displaying YouTube videos in QML-based apps. Discussion on ideas, implementation strategies and applications of Internet video in MeeGo; focus will be on QML implementation, providing touch-interfaces for streaming media browsing, hybrid implementations involving Flash embedded in WebKit implementations, issues with using QtMultimediaKit Player, and discussion of alternatives. [...] e. Open discussion on media players including issues with using QtMultimediaKit Player in QML, and discussion of alternatives such as Grilo ( http://sf2011.meego.com/program/sessions/grilo-enhancing-multimedia-experience-meego ), MAFW ( http://www.grancanariadesktopsummit.org/node/219 ), gst123 ( http://space.twc.de/~stefan/gst123.php ) and the Media Lovin' Toolkit ( http://www.mltframework.org/ ) which is the basis of the amazing http://wiki.meego.com/MeeGo-Lem#The_OpenShot_Video_Editor . ... Any suggestions or changes? Let me know... it's not midnight yet! :-), especially from pt-of-view of using aforementioned playback/loop/clip tools from QML. 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
[MeeGo-dev] Will MeeGo get this RT feature? (Fwd: [LAD] linux-2.6.39 with force threaded irq-handlers: our new rt-kernel)
and will we be able to "just add "threadirqs" to the kernel boot params"? (good overview: http://www.cs.unc.edu/~anderson/meetings/ospert08/zijlstra.pdf http://lwn.net/Articles/324980/ ) -- Forwarded message -- From: torbenh Date: Sun, Mar 20, 2011 at 6:04 AM Subject: [LAD] linux-2.6.39 with force threaded irq-handlers: our new rt-kernel To: linux-audio-...@lists.linuxaudio.org hi... we are about a week in the merge window, and linus merged the force threaded irq handlers already. This means, that the most important feature of the -rt patches is now in mainline. we sould start testing it during the rc cycle, i think. (there will not be too many people turning force threaded handler on) i will try to write up somthing about kernel config and boot parameters once i have a kernel running in my kvm later this week. -- torben Hohn ___ Linux-audio-dev mailing list linux-audio-...@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev ___ 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 Video API's
On Fri, Mar 18, 2011 at 3:12 PM, Brendan Le Foll wrote: > MeeGo will never be a usable commercial OS that system vendors can > package and put on devices if our video APIs are based on a non DRM + > proprietary codec friendly system (never mind the other problems > mentioned by Dave). Gstreamer makes such integration fairly easy and > there is integration for various hardware acceleration. > > Anyways we can harnest most of the power of ffmpeg in gstreamer with > gst-ffmpeg, if you feel you're missing some codecs ;-) >From my perspective, every line of new code is a bug that hasn't been filed yet. So why throw out code that has learned to survive in so many environments, with so many different codecs, languages, encodings, etc. Furthermore given that the code is now "1.0" perhaps it will have better stability ongoing? MLT which I posted about in follow-on, is a another interesing ffmpeg derivative that's also seen a lot of use: http://www.mltframework.org/twiki/bin/view/MLT/Projects including OpenShot and Kdenlive . (Correction: previously, I may have implied MLT is qt-based -- I was referring to http://mltframework.org/BuildOnMe.git which is a template player based on MLT that can be built, portably, in qtcreator, with dependencies on mlt libraries). Re: mplayer -- doesn't it come with lots of proprietary codecs ( http://www.mplayerhq.hu/MPlayer/releases/codecs/ ) -- seems pretty friendly to supporting them. Furthermore, doesn't mplayer also support hardware acceleration: http://wiki.multimedia.cx/index.php?title=MPlayer_FAQ#Hardware_Acceleration_Patches Regarding codecs on MeeGo, http://wiki.meego.com/MeeGo-Lem#Be_able_to_watch.2Fhear_common_internet_media_formats gives me: meegolem-11-~/qt> zypper se ffmpeg Loading repository data... Reading installed packages... S | Name| Summary | Type --+-+--+ i | ffmpeg | Digital VCR and streaming server | package | ffmpeg-devel| Development package for ffmpeg | package i | ffmpeg-libs | Libraries for ffmpeg | package i | ffmpeg2dirac| Convert any file that ffmpeg can decod-> | package i | ffmpeg2theora | Convert any file that ffmpeg can decod-> | package i | ffmpegthumbnailer | Lightweight video thumbnailer that can-> | package | ffmpegthumbnailer-devel | Headers and libraries for building app-> | package | gallery2-ffmpeg | Ffmpeg module for Gallery 2 | package i | gstreamer-ffmpeg| GStreamer FFmpeg-based plug-ins | package | kffmpegthumbnailer | A video thumbnailer for kde based on f-> | package -- 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] Meego Video API's
On Fri, Mar 18, 2011 at 12:32 PM, Dave Neary wrote: > I would recommend building on libav instead http://libav.org/ which is > the continuation of FFMpeg as a library project, independent of mplayer.hu. I have, but in Vala: http://code.google.com/p/spekle/ . FYI: http://www.mltframework.org is based on Qt and is multi-platform. It may be of interest for any looking to build a player framework for MeeGo. I installed it on MeeGo 1.2 Netbook via sudo zypper in http://mib.pianetalinux.org/MIB/2010.2/32/basic/python-mlt-0.5.10-69mib2010.1.i686.rpm http://mib.pianetalinux.org/MIB/2010.2/32/basic/libmlt-devel-0.5.10-69mib2010.1.i686.rpm http://mib.pianetalinux.org/MIB/2010.2/32/basic/mlt-0.5.10-69mib2010.1.i686.rpm http://mib.pianetalinux.org/MIB/2010.2/32/basic/libmlt2-0.5.10-69mib2010.1.i686.rpm http://mib.pianetalinux.org/MIB/2010.2/32/basic/libmlt++3-0.5.10-69mib2010.1.i686.rpm I originally brought up MLT in order to run the latest python sources for OpenShot (it works: http://wiki.meego.com/MeeGo-Lem#The_OpenShot_Video_Editor ) since MLT and a compatible python-mlt are a few of many dependencies Are there advantages to MLT over a player built on QtMobility functionality, e.g. http://doc.qt.nokia.com/qt-mobility-snapshot/multimedia.html#video ? . http://sourceforge.net/news/?group_id=96039&id=296772 Since MLT is now working on Mac OS X, Windows, Linux, and BSD, I added a cross-platform C++ Qt starter project to the git repository: http://mltframework.org/BuildOnMe.git It is just a very simple media player with menu, toolbar, status bar, and video frame. The build system is qmake, which is very convenient to use with the cross-platform Qt Creator tool. The code includes the special OpenGL playout widget needed for Mac OS X. It is licensed under the liberal MIT open source license. On OS X, BSD, and Linux, it uses pkg-config to locate the MLT dependencies. Therefore, on OS X, the easiest way to get up and running is to use the macports.org mlt port. On Windows, a couple of extra steps are needed to copy files from the mlt build area to the Qt project build area. .. Note "-lmlt++ -lmlt" in compilation -- see http://mib.pianetalinux.org/MIB/2010.2/32/basic/libmlt-devel-0.5.10-69mib2010.1.i686.rpm http://mib.pianetalinux.org/MIB/2010.2/32/basic/mlt-0.5.10-69mib2010.1.i686.rpm http://mib.pianetalinux.org/MIB/2010.2/32/basic/libmlt2-0.5.10-69mib2010.1.i686.rpm http://mib.pianetalinux.org/MIB/2010.2/32/basic/libmlt++3-0.5.10-69mib2010.1.i686.rpm Running build steps for project BuildOnMe... Starting: "/opt/QtSDK/Desktop/Qt/472/gcc/bin/qmake" /home/npm/qt/BuildOnMe/BuildOnMe.pro -r -spec linux-g++ QMLJSDEBUGGER_PATH=/opt/QtSDK/QtCreator/share/qtcreator/qml/qmljsdebugger The process "/opt/QtSDK/Desktop/Qt/472/gcc/bin/qmake" exited normally. Starting: "/usr/bin/make" -w make: Entering directory `/home/npm/qt/BuildOnMe-build-desktop' /opt/QtSDK/Desktop/Qt/472/gcc/bin/uic ../BuildOnMe/mainwindow.ui -o ui_mainwindow.h g++ -c -pipe -O2 -D_REENTRANT -I/usr/include/mlt++ -I/usr/include/mlt -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -I/opt/QtSDK/Desktop/Qt/472/gcc/mkspecs/linux-g++ -I../BuildOnMe -I/opt/QtSDK/Desktop/Qt/472/gcc/include/QtCore -I/opt/QtSDK/Desktop/Qt/472/gcc/include/QtGui -I/opt/QtSDK/Desktop/Qt/472/gcc/include -I. -I. -I../BuildOnMe -I. -o main.o ../BuildOnMe/main.cpp g++ -c -pipe -O2 -D_REENTRANT -I/usr/include/mlt++ -I/usr/include/mlt -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -I/opt/QtSDK/Desktop/Qt/472/gcc/mkspecs/linux-g++ -I../BuildOnMe -I/opt/QtSDK/Desktop/Qt/472/gcc/include/QtCore -I/opt/QtSDK/Desktop/Qt/472/gcc/include/QtGui -I/opt/QtSDK/Desktop/Qt/472/gcc/include -I. -I. -I../BuildOnMe -I. -o mainwindow.o ../BuildOnMe/mainwindow.cpp /opt/QtSDK/Desktop/Qt/472/gcc/bin/moc -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -I/opt/QtSDK/Desktop/Qt/472/gcc/mkspecs/linux-g++ -I../BuildOnMe -I/opt/QtSDK/Desktop/Qt/472/gcc/include/QtCore -I/opt/QtSDK/Desktop/Qt/472/gcc/include/QtGui -I/opt/QtSDK/Desktop/Qt/472/gcc/include -I. -I. -I../BuildOnMe -I. ../BuildOnMe/mainwindow.h -o moc_mainwindow.cpp g++ -c -pipe -O2 -D_REENTRANT -I/usr/include/mlt++ -I/usr/include/mlt -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -I/opt/QtSDK/Desktop/Qt/472/gcc/mkspecs/linux-g++ -I../BuildOnMe -I/opt/QtSDK/Desktop/Qt/472/gcc/include/QtCore -I/opt/QtSDK/Desktop/Qt/472/gcc/include/QtGui -I/opt/QtSDK/Desktop/Qt/472/gcc/include -I. -I. -I../BuildOnMe -I. -o moc_mainwindow.o moc_mainwindow.cpp g++ -Wl,-O1 -Wl,-rpath,/opt/QtSDK/Desktop/Qt/472/gcc/lib -o BuildOnMe main.o mainwindow.o moc_mainwindow.o -L/opt/QtSDK/Desktop/Qt/472/gcc/lib -lmlt++ -lmlt -lQtGui -lQtCore -lpthread make: Leaving directory `/home/npm/qt/BuildOnMe-build-desktop' The process "/usr/bin/make" exited normally. . -- Niels http://nielsmayer.com ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/list
Re: [MeeGo-dev] Meego Video API's
On Fri, Mar 18, 2011 at 5:16 AM, Dominig ar Foll wrote: > in the TV project we have a serious need to treat video well and for > that reason we have started a tread discussion on the need for a unified > video player which can hide the complexity of sourcing the video and > managing special the hardware (including overlay). What about using http://www.mplayerhq.hu and various programs that wrap it effectively? I've found http://smplayer.sourceforge.net/ to be one such wrapper, and it's very much MeeGo compatible because it's based on Qt. For embedding a media player in the browser (so that when you click an internet MP3/MP4/etc link, the player embeds in the browser/QtWebKit) http://code.google.com/p/gecko-mediaplayer/ I'm beginning to document how to get these and all needed media playing plugins (for 1.2 Netbook UX, but probably usable on all ia32 based meegos): http://wiki.meego.com/MeeGo-Lem#Be_able_to_watch.2Fhear_common_internet_media_formats. -- 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] Post-installation security fix & question for Intel MeeGo Tablet developers release
On Tue, Mar 8, 2011 at 1:30 PM, Martin Grimme wrote: > I found out how to use the mute button on the Lenovo S10-3t for the > Super/Home Key on the Intel Tablet UX. The other two buttons are ACPI > buttons and generate no keycodes with this kernel. > > Run > > setkeycodes e020 125 > > as root. Thank you!! Works great on the Netbook UX as well, bringing up the popup bar at the top. This is normally difficult to bring up in "tablet" mode because you have to jam your pinky up against the bezel near the top of the display so as to get close to the pixels at the very top of the screen. Or use a capacitive "stylus" that is small enough to get at the screen right near the bezel. I'm more likely to reach under and find the "windows" key... but now I don't have to. I also updated http://forum.meego.com/showthread.php?p=19269 with this info. 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] Some architecture changes (MSSF / Buteo / PIM storage)
On Mon, Mar 7, 2011 at 8:09 AM, Arjan van de Ven wrote: > To be clear, this does not mean that "tracker" is completely removed; > tracker is still being used (together with tumbler) for indexing media > on the device. At this point we are seeing serious issues > (performance/stability) with this solution, but the first attempt will be to > fix the deficiencies rather than a replacement. Actually, where exactly are tracker's results used in the Netbook UX for indexing media? I thought banshee was independently indexing media as well... sometimes they even get into a fight about it: http://lists.meego.com/pipermail/meego-community/2011-February/003597.html At least on the 1.2 Netbook release, tracker does cause problems -- I've disabled its media scanning to prevent issues ongoing issues: http://lists.meego.com/pipermail/meego-community/2011-February/003605.html For Maemo issues with tracker -- and potential customizations to prevent performance issues: http://lists.meego.com/pipermail/meego-community/2011-February/003598.html There appears to be duplicated functionality between tracker and banshee's media indexing. If other tracker functionality has been removed for 1.2, and tracker's media indexing results seem to be unused by banshee, what about removing tracker entirely from the 1.2 Netbook UX? > there's a lot of impact from this currently, both in terms of just raw CPU > cycles to power impact to stability (we're seeing quite some crashes, which > worries me from a security pov) I'm glad this is being considered and I concur. One other issue for indexing: if a gstreamer codec needs to be invoked first, e..g. for indexing or thumbnailing media, then is that potentially untrusted or closed-source codec sandboxed, when executing? What of the security of the gstreamer pipeline against media-based attack vector? -- 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] Meego co-exist with Windows
On Fri, Feb 25, 2011 at 10:30 AM, Alistair Buxton wrote: > This is supposed to be fixed in 1.2, although I have not tested it > personally. It works fine -- unless you tell the install to overwrite your whole disk. However, on boot, the system will appear to go into meego right away. You need to QUICKLY use the up/down arrow keys while it's in "grub" phase before booting.. This will bring up the screen showing that you have multiple boot choices. Cursor to the "other" partition (what it labels the windows partition by default) and boot -- 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] Insights into network flakyness in MeeGo 1.2 Netbook
On Wed, Feb 23, 2011 at 7:42 PM, Niels Mayer wrote: > https://bugs.meego.com/show_bug.cgi?id=13778 > Bug 13778 - Wireless connection loses "router" setting for Static-IP > https://bugs.meego.com/show_bug.cgi?id=13780 > Bug 13780 - Wired connection stops working when transferring lots of data > ath9k 65616 0 > ath9k_common 1977 1 ath9k > ath9k_hw 243231 2 ath9k,ath9k_common This is probably really what's taking out the wireless and making the wired connection go up and down during heavy network transfers of media files: http://nielsmayer.com/meego/netbook-ia32-1.2/meego-networking-fails-syslog.txt It may be related to tracker doing stuff to the files during said heavy transfers of media files: http://lists.meego.com/pipermail/meego-community/2011-February/003597.html How do I turn off tracker without breaking other functionality in MeeGo, to see whether this is the case? Deinstall tracker and banshee? I hope this gets fixed before the 1.2 release... Seems like this is an old issue that's come up with tracker before -- in Maemo -- and it ought to be solved before the 1.2 release as the issues and problems are understood: http://talk.maemo.org/showthread.php?t=61960 . Flandry 09-09-2010 , 12:03 AM For those that don't know, tracker is the utility that watches for new media and makes thumbnails of new images on your N900. It has been widely cursed and hated for its poor behavior and can cause sluggish response time while doing its thing -- which it tends to do right when you want to use your N900, like when taking a bunch of photos. There is a configuration file for tracker in /home/user/.config/tracker/ called tracker.cfg. By default it has quite a few comments that can be helpful in deciphering the settings, but i find i'm still not really sure what the default behavior of tracker is. .. -- 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] Insights into network flakyness in MeeGo 1.2 Netbook
And it would seem the exact same behavior I'm seeing is also happening
in the N900-handset world:
https://bugs.meego.com/show_bug.cgi?id=13304
Bug 13304 - WLAN connection is lost when downloading a file in Fennec.
.
Tried to download a file from Terminal using wget command - same issue.
Attaching logs:
[root@localhost ~]# cd /usr/lib/connman/test
[root@localhost test]# ./test-connman services
HiddenOne { wifi_001fdfb4a544_48696464656e4f6e65_managed_psk
}
testing{ wifi_001fdfb4a544_74657374696e67_managed_psk }
[root@localhost test]# ./connect-service HiddenOne WER145HGH
Attempting to connect service HiddenOne
Service path is
/profile/default/wifi_001fdfb4a544_48696464656e4f6e65_managed_psk
[root@localhost test]# ping www.google.com
PING www.l.google.com (209.85.149.103) 56(84) bytes of data.
^C
--- www.l.google.com ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1794ms
[root@localhost test]# wget http://dynamo.dy.fi/dy/big/75MB.bin
--2000-01-01 00:16:04-- http://dynamo.dy.fi/dy/big/75MB.bin
Resolving dynamo.dy.fi... 217.30.188.169
Connecting to dynamo.dy.fi|217.30.188.169|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 78643200 (75M) [application/octet-stream]
Saving to: “75MB.bin”
0% [] 191,140 --.-K/s eta 42h 1m
^C
[root@localhost test]# ping www.google.com
ping: unknown host www.google.com
.
https://bugs.meego.com/show_bug.cgi?id=13304#c3
..
still re-prodeced in weekly image
http://repo.meego.com/MeeGo/builds/1.1.90/1.1.90.4.20110222.2/images/meego-handset-armv7l-n900/
..
The same weekly image against which the exact same behaviors were seen
on 1.2 Netbook UX transferring large files...
-- 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] [discuss]Should we grant the privilege of admin printer to default user?
On Wed, Feb 23, 2011 at 9:37 PM, Chengwei Yang wrote: > according to #BMC-9011, the default user hasn't the right to add a > printer, it will confuses the end user. > on meego, only users in group 'sys and root' have that privilege, can we > grant the privilege to user when it created by firstboot? This is already enabled and seems to be done by firstboot already in recent 1.1.90 releases. After firstboot sets up a new user (e.g. 'npm') note that /etc/shadow and /etc/passwd are setup with both 'root' and 'npm' (or whatever user you setup) with the same password. Additionally, note that /etc/sudoers has the following appended: ## Allow npm to run all commands npmALL=(ALL)ALL . This means that the default user could use 'sudo' to run things as root, but the way it is setup, a password will be required. The password prompting/response needs to be handled in any apps that may call sudo to increase the user's priviledge levels. Note that by changing to npmALL=(ALL) NOPASSWD: ALL Would allow sudo to be invoked without a password. (potentially dangerous since somebody nasty could walk up to your netbook and go "sudo rm -rf /" ...). However,it may simplify an interactive program's need to perform administrative work However it is also possible to use the syntax above and replace "ALL" with the specific program(s) the user needs to invoke for administrative purposes. Perhaps use this form of /etc/sudoers for the specific command needed to administer the printer? 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] Insights into network flakyness in MeeGo 1.2 Netbook
On Wed, Feb 23, 2011 at 7:42 PM, Niels Mayer wrote: > https://bugs.meego.com/show_bug.cgi?id=13778 > Bug 13778 - Wireless connection loses "router" setting for Static-IP > https://bugs.meego.com/show_bug.cgi?id=13780 > Bug 13780 - Wired connection stops working when transferring lots of data According to the comments in the bugs, these issues are "hardware specific" and people aren't seeing this issue on their netbooks. However, my understanding is that the Lenovo S10-3t is a "reference platform" for MeeGo; therefore, testing should be done on this specific reference platform with its specific wireless interfaces: ath9k 65616 0 ath9k_common1977 1 ath9k ath9k_hw 243231 2 ath9k,ath9k_common Anybody else having networking issues with the Lenovo S10-3t, or other netbooks with Atheros9K wireless drivers? I'm seeing the same kinds of problems in issues others have reported. This indicates the problem is more widespread than just a specific driver and points to some problems and instabilities in the applications and middleware layer: https://bugs.meego.com/show_bug.cgi?id=7529 https://bugs.meego.com/show_bug.cgi?id=11083 https://bugs.meego.com/show_bug.cgi?id=5202 Also, I set the issues I reported as "release blocker" because I don't think 1.2 should be released with networking not working correctly, unless we change the release name from "netbook" to "book" :-/ ; Alternately, if this isn't considered the "showstopper" that I believe it is, then the Lenovo S10-3t should be removed from the list of reference platforms for MeeGo 1.2, since the networking doesn't work correctly on the platform, either for wireless or wired connections. Niels http://nielsmayer.com PS: One hunch I have is that power-management is turning off the networking interfaces, even while they're being used. See, I rarely have a problem with a simple "outgoing connection" like browsing the web. The issue I'm seeing are with long-running connections, such as SSH sessions, SSH-based file transfers of 30gigs of media-files, etc. In fact, the network interface isn't visible to the outside world unless I make an outgoing conenction first (like browsing a web page). Then I can SSH in briefly before it appears like the network has disappeared again -- as if the networking hardware went to sleep between connections. Next time I reboot (which I don't like to do, because it's so iffy getting back online) I'll check the BIOS settings and see if the networking interfaces are being put to sleep to save power. At least on a desktop mobo (ASUS), such settings are available, I never even looked at the bios on the s10-3t to see if there's any obvious changes that need to be done before installing MeeGo. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Insights into network flakyness in MeeGo 1.2 Netbook
https://bugs.meego.com/show_bug.cgi?id=13778 Bug 13778 - Wireless connection loses "router" setting for Static-IP https://bugs.meego.com/show_bug.cgi?id=13780 Bug 13780 - Wired connection stops working when transferring lots of data Any idea when these will be fixed? IMHO they're showstoppers. 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
[MeeGo-dev] By the way audio actually works in MeeGo "1.2" netbook
http://qa-reports.meego.com/1.2/Netbook/Acceptance/Pinetrail/ indicates that audio is not working in ( https://bugs.meego.com/show_bug.cgi?id=13436 ). Worksforme :-) Seeing pulseaudio churning away like it does whenever audio is output, and events going into the audio device had me look at something a little simpler... You just have to remember to turn up "Master" volume at the ALSA level! This has nothing to do with pulseaudio per say, other than gettting in the way and hiding important device information ... The GUI volume control only changes "PCM" ; by default it seems "Master" is set to 0 and hidden. In KDE/phonon's 'kmix' this is handled more elegantly, IMHO -- you can choose which device the GUI and keyboard volume control actually changes -- e.g. PCM/Master/Headphone/etc -- or route your "media" audio to an external SPDIF or HDMI digital output, leaving the computer speakers for system sounds and other low-fi. On the MeeGo 1.2 netbook, running on Lenovo s10-3t reference platform, running "alsamixer -c 0" in a terminal will let you see what's going on and adjust the "Master" volume using the cursor keys. Here's how I got it adjusted currently: meegolem-156-~> amixer -c 0 Simple mixer control 'Master',0 Capabilities: pvolume pswitch pswitch-joined penum Playback channels: Front Left - Front Right Limits: Playback 0 - 74 Mono: Front Left: Playback 74 [100%] [0.00dB] [on] Front Right: Playback 74 [100%] [0.00dB] [on] Simple mixer control 'PCM',0 Capabilities: pvolume penum Playback channels: Front Left - Front Right Limits: Playback 0 - 255 Mono: Front Left: Playback 255 [100%] [0.00dB] Front Right: Playback 255 [100%] [0.00dB] Simple mixer control 'Capture',0 Capabilities: cvolume cswitch penum Capture channels: Front Left - Front Right Limits: Capture 0 - 80 Front Left: Capture 80 [100%] [6.00dB] [on] Front Right: Capture 80 [100%] [6.00dB] [on] Simple mixer control 'Analog Mic Boost',0 Capabilities: cenum Items: '0dB' '10dB' '20dB' '30dB' '40dB' Item0: '0dB' .. Now I have audio working on the internal card -- I have absolutely no reasons to upgrade beyond the hybrid release I've created... especially now that I've got Fedora 14/RPMFusion/PlanetCCRMA/Google repositories integrated :-). Oh wait the video isn't working yet. But then again how could it be given that v4l modules aren't installed? meegolem-162-~> lsmod Module Size Used by snd_usb_audio 81305 0 snd_usbmidi_lib15341 1 snd_usb_audio snd_rawmidi16190 1 snd_usbmidi_lib ath9k 65616 0 ath9k_common1977 1 ath9k ideapad_laptop 3517 0 joydev 8181 0 ath9k_hw 243231 2 ath9k,ath9k_common serio_raw 3797 0 battery 8850 0 So which of these do I 'modprobe' to get the Lenovo s10-3t camera working?? meegolem-160-~> modprobe -l | grep vid kernel/drivers/video/backlight/adp8860_bl.ko kernel/drivers/video/vgastate.ko kernel/drivers/video/sysfillrect.ko kernel/drivers/video/syscopyarea.ko kernel/drivers/video/sysimgblt.ko kernel/drivers/video/fb_sys_fops.ko kernel/drivers/media/video/tuner.ko kernel/drivers/media/video/tda9840.ko kernel/drivers/media/video/tea6415c.ko kernel/drivers/media/video/tea6420.ko kernel/drivers/media/video/saa7115.ko kernel/drivers/media/video/tveeprom.ko kernel/drivers/media/video/sr030pc30.ko kernel/drivers/media/video/cpia2/cpia2.ko kernel/drivers/media/video/mxb.ko kernel/drivers/media/video/videobuf-core.ko kernel/drivers/media/video/videobuf-dma-sg.ko kernel/drivers/media/video/videobuf-dma-contig.ko kernel/drivers/media/video/videobuf-vmalloc.ko kernel/drivers/media/video/videobuf-dvb.ko kernel/drivers/media/video/zr364xx.ko kernel/drivers/media/video/stkwebcam.ko kernel/drivers/media/video/sn9c102/sn9c102.ko kernel/drivers/media/video/et61x251/et61x251.ko kernel/drivers/media/video/pwc/pwc.ko kernel/drivers/media/video/gspca/gspca_main.ko kernel/drivers/media/video/gspca/gspca_jeilinj.ko kernel/drivers/media/video/gspca/gspca_konica.ko kernel/drivers/media/video/gspca/gspca_mr97310a.ko kernel/drivers/media/video/gspca/gspca_sn9c20x.ko kernel/drivers/media/video/gspca/gspca_spca1528.ko kernel/drivers/media/video/gspca/gspca_sq905.ko kernel/drivers/media/video/gspca/gspca_sq905c.ko kernel/drivers/media/video/gspca/gspca_sq930x.ko kernel/drivers/media/video/gspca/gspca_xirlink_cit.ko kernel/drivers/media/video/gspca/gl860/gspca_gl860.ko kernel/drivers/media/video/s2255drv.ko kernel/drivers/media/video/uvc/uvcvideo.ko kernel/drivers/media/video/saa7164/saa7164.ko kernel/drivers/video/i810/i810fb.ko Niels http://nielsmayer.com PS: (*) FYI snd_usbmidi_libsnd_usb_audio snd_rawmidi snd_usbmidi_lib all got loaded up because I was testing out the packages I'd just installed on this "1.2 MeeGolem" http://jackaudio.org and http://qjackctl.sourceforge.net and http://www.hydrogen-music.org/ I'd loaded up with a little install: ROO
[MeeGo-dev] Post-installation security fix & question for Intel MeeGo Tablet developers release
meego-netbook-ia32-1.1.90.3.20110215.10.img's installer prompts the
user to set a default user and password on first-boot, and sets the
root password to the same as the user's. Intel's
meego-tablet-ia32-pinetrail.iso
(http://appdeveloper.intel.com/en-us/meego-swype-esla ) doesn't.
Therefore be sure to consider the following warning before putting the
tablet on a public wifi network:
It boots up by default with an SSH port open, with accounts "root"
and "meego" set to the default password "meego."
> Not shown: 999 closed ports
> PORT STATE SERVICE VERSION
> 22/tcp open ssh OpenSSH 5.6 (protocol 2.0)
Therefore, bring up a terminal and su to root and do "passwd root" and
"passwd meego" to setup better passwords. Ideally you should also
modify SSH to not allow root logins, and even better setup SSH
public/private keypairs for login, and change sshd_config(5) with:
> PermitRootLogin no
> PasswordAuthentication no
> PermitEmptyPasswords no
.
On a non-security related question: I finally figured out how the
tablet UX is supposed to be used by watching a video -- there's an
"exit" key ("quickselect button" per
http://pycage.blogspot.com/2010/10/wetab-look-at-first-meego-tablet.html
) that takes you back to the main panel UI. Unfortunately, when the
S10-3t is in tablet configuration, the equivalent "windows key" that
brings you back to the panels is hidden under the display, and none of
the buttons on the lower left are active. You can work around it by
reaching under the display and finding the window or menu keys on the
keyboard, but it's tedious to use that way...
What is the correct way to bind these keys? xmodmap(1)?? I ran xev(1)
and when I press these keys, it reports the following:
"keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0"
Anybody have the key binding names for the "screen rotate" and
"natural touch" buttons near the display? Or better yet a .xmodmap
file? Or the right way to do this?
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] MeeGo Netbook "1.2" post installation crash
On Wed, Feb 16, 2011 at 11:22 AM, Michael Leibowitz wrote: > Please see BMC#12655, and see if it is the same. It is: https://bugs.meego.com/show_bug.cgi?id=12655#c3 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
[MeeGo-dev] MeeGo Netbook "1.2" post installation crash
I'm seeing a consistent crash on post-install of the 1.2 testing releases, including meego-netbook-ia32-1.1.90.2.20110208.4.img or meego-netbook-ia32-1.1.90.3.20110215.10.img from http://repo.meego.com/MeeGo/builds/1.1.90/ and also meego-tablet-ia32-pinetrail.iso from http://appdeveloper.intel.com/en-us/meego-swype-esla (which looks and feels like giant-sized version of the handset UX and isn't like the netbook UX). On all three, the install completes successfully, but crashes on exit -- requiring a manual power cycle to complete the reboot into the installed OS. This is on a Lenovo S10-3t which should be compatible with MeeGo Netbook UX. The installation image resides on a SD card plugged into the front slot. Since there wasn't a trace of the crash in the logs, the best I could do is capture a screenshot with a camera: http://nielsmayer.com/meego/photo2011.02.16_09.15.05.37.jpg http://nielsmayer.com/meego/photo2011.02.16_09.15.16.84.jpg (had to capture two images so as to be able to read the text and see most of the backtrace). As I notice the crash occurred during an unmount -- perhaps it doesn't like installing the image from the SD card slot? Also, this is clearly a bug which I should file, if I could figure out what category this bug belongs in. Are such installer issues considered "core" since it's ultimately a problem with umount? Would it go under "Netbook UX" since it's specific to the netbook install (but has nothing to do with user experience and also happens on Intel's "Tablet UX"). And shouldn't there be a specific category for installation bugs like this? 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
[MeeGo-dev] Fwd: GTk+ (and Hildon?) on Meego Handset
Just curious at what level this is being "ported" or "integrated" -- X windows, OpenGL ES, or both? ... http://blogs.gnome.org/foundation/2011/01/17/gtk-meego-handset-bidders-selected/ Gtk+/MeeGo Handset bidders selected The GNOME Foundation Board is happy to announce that following the call for bids for MeeGo/GTK+ integration work, Igalia was selected as the preferred bidder to perform the work set out. We received a number of very interesting bids for the project, but Igalia’s bid was the one that focused the most on integrating elements of Hildon into GTK+ upstream. This should mean easier porting of older Hildon/Maemo applications to the new MeeGo Handset platform, as well as easier porting of existing desktop GTK+ applications to the handset. Claudio Saavedra and Carlos García Campos will be the main developers working on the project, so expect regular updates on the advancement of the project on their respective blogs. The GNOME Foundation Board would like to thank the bidders again for their interest in the project. Special thanks to Danielle Madeley, Murray Cumming, and Robert McQueen for their technical knowledge of the MeeGo Handset platform. . Niels http://nielsmayer.com ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] [MeeGo-SDK] [Security part of the meego1.1]
On Wed, Jan 19, 2011 at 8:36 PM, Rudolf Streif wrote: > What other information/documentation on the security framework besides the > MeeGo conference slides and the basic SMACK documentation is available? In trying to understand Meego 1.2 security, I placed all the links I found of interest at the end of this message: http://lists.meego.com/pipermail/meego-security-discussion/2011-January/19.html An interesting counterpoint: http://ols.fedoraproject.org/OLS/Reprints-2008/nakamura-reprint.pdf is suggested in http://lwn.net/Articles/293075/ > What I am looking for is how can I test the security framework by writing a > simple application that tries to > do an open/iotcl on a device it does not have access to? Is there any > documentation that outlines the steps > for application developers? Hmm... not having used such a system, I would imagine you'd write a special unique SMACK label on any protected devices; then access only from processes with a matching label. CAP_MKNOD_POSIX also needs to be disabled per http://www.docstoc.com/docs/68013153/Digital-TV-and-application-store_-solving-security-problems http://www.embeddedalley.com/pdfs/Smack_for_DigitalTV.pdf suggests a test preparation script which among other things, does: Label protected device nodes with 'prot_dev' label Devices labeled as protected are /dev/mem and /dev/hdc Label open device nodes with 'open_dev' label Devices labeled as open are /dev/zero and /dev/null . https://help.ubuntu.com/community/SmackConfiguration#The%20System%20Separation%20Configuration shows how to setup wildcard labels on shared devices: ... /usr/bin/attr -S -s SMACK64 -V '*' /dev/null /usr/bin/attr -S -s SMACK64 -V '*' /dev/zero -- Niels http://nielsmayer.com PS: I noticed some new security packages in meego-handset-armv7l-n900-devel-1.1.80.15.20110118.5-mmcblk0p.raw.bz2 -- would this version give a handset image with a "system separation configuration" ; is there a special script to run or package to intstall to have it come up with "MeeGo 1.2 Security" or is it not ready for use/testing yet? ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Audio stack question
On Tue, Jan 18, 2011 at 1:04 AM, Counihan, Tom wrote: > http://conference2010.meego.com/session/policy-framework-flexible-way-orchestrate-multiple-functionalities-meego-devices See also: http://wiki.meego.com/images/Meego-policy-framework-developer-guide.pdf Meego really needs an overview document of the Multimedia subsystems similar to this one from Maemo: http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Architecture/Multimedia_Domain ... Regarding the ALSA layer, there is the potential overlap between ALSA "use case manager" and the aforementioned MeeGo policy framework: See: http://conference2010.meego.com/session/audio-hardware-use-case-management-mobile-devices .. AUDIO HARDWARE USE CASE MANAGEMENT FOR MOBILE DEVICES Session Summary: Simplified audio hardware management with emphasis on performance, power consumption and audio use case flexibility. This session will explore the problems faced in abstracting complex audio hardware into simple portable use cases and how to overcome these problem areas with ALSA UCM. Session Abstract: Todays modern mobile devices must provide users with feature rich audio hardware functionality that must be seamlessly integrated with applications, optimized for power and provide excellent performance. The ALSA Use Case Manager (UCM) is designed to achieve the above and provide clients (like Pulseaudio) with a portable means of controlling audio hardware without any underlying hardware knowledge. The intention of UCM is to make audio applications portable between different Meego based devices and to simplify audio driver development by off loading complex routing sequences to UCM. This session will describe how to leverage the benefits of UCM into real devices. ALSA UCM is open source software and is in the process of being merged into alsa-lib. . https://wiki.ubuntu.com/Specs/N/ARM/AlsaScenarioManager http://opensource.wolfsonmicro.com/node/14 // The ALSA scenario manager is a LGPL library designed to allow high level control of audio scenarios or use cases in sound device hardware. It is intended to be used by applications to change the hardware audio scenario of a device in a generic and portable manner. e.g. a dialer application may want to set a "GSM phone call" scenario or a media player may want to set a "playback via headphones" scenario. This library is not meant to replace gstreamer, PulseAudio or a sound server, but is meant to work in tandem with such audio software. Features Simple API and standard scenario types for changing device hardware scenario. Scenarios are stored in standard ALSA alsactl file format and can be very quickly generated using alsamixer. Ability for applications to identify controls relevant to the current scenario. // http://www.slimlogic.co.uk/?page_id=7 The ALSA scenario manager provides the following features. Consistent and simple C API. The library provides simple and consistent methods to change scenario or use case and thus make applications more portable across different devices. Ability to change any ALSA audio control type. This includes signal gain and signal routing (through mixers and muxes). Gain and mixer aliasing. Different scenarios may use different hardware gain controls (e.g. some hardware has different hardware gain controls for headphone and speaker volumes) . The library can alias controls so that the correct volume control is updated no matter what use case is in operation. // -- Niels http://nielsmayer.com PS: some of the above came from researching and writing http://code.google.com/p/ytd-meego/wiki/CitizenJournalismWithYoutubeDirectForMeego And also from previous discussions on Meego lists: http://lists.meego.com/pipermail/meego-handset/2010-December/74.html http://lists.meego.com/pipermail/meego-handset/2010-December/90.html ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Fwd: Qtest Mobile App Port Contest for Qt and KDE applications
If you need something to push you over the edge and port your existing Qt/KDE music-making or multimedia app to the N900 running Symbian, Maemo, or Meego: http://qt-apps.org/news/?id=340 (see below). Some ideas (please?): http://sv1.sourceforge.net/ == http://www.sonicvisualiser.org/ http://kmid2.sourceforge.net http://kmetronome.sourceforge.net http://kmidimon.sourceforge.net http://vmpk.sourceforge.net/ http://qtractor.sourceforge.net http://qmidictl.sourceforge.net http://qmidinet.sourceforge.net http://qjackctl.sourceforge.net/ Win 10.000,- EUR at the "Qtest Mobile App Port" Published: Dec 20 2010 Qtest Mobile App Port Contest for Qt and KDE applications Welcome to the Qtest Mobile App Port! As developers of applications using Qt, you already know how great it is to work with - but how about on mobile platforms, such as Symbian and MeeGo? How would you like to take that step you have been wanting to take, but not been able to justify: Take your application from the desktop and bring it into the hand-held world via the Ovi store. Let this contest be the justification, with the possibility of a new phone or even 10,000 euros waiting at the end. Dates: The contest starts on 20th of December, 2010, and runs till 28th of February. The 31st of December is important for you if you wish to take part in the Early Bird competition. If you do no win, you will still take part in the main competition, and will be allowed to continue your work and submit new versions to the Ovi Store. The 28th of February is the deadline for taking part in the main competition. Developer Sprint: There will be a sponsored developer sprint organized together with the KDE e.V. during the competition. The travel and stay can be paid for if you do not have the budget yourself. Further details will be made public at a later time, and all participants will be notified of this information via email. Judging and prizes: The Qtest Mobile App Port is evaluated by a panel of judges which will be announced in the next few days. The jury will pic 5 winners at 31th of December as the early bird winners. Every winner gets a free N900 phone. The main competition first prize is EUR 10,000, which will be awarded to the application which the judges find to be the best ported application. The second to sixth price will be another 5 N900 phones. And, finally: Everybody who takes part in the competition will be awarded a gift bag, with a T-shirt and other merchandise. Eligibility: To be able to take part in the contest, the ported application must be submitted for Ovi Store signing by one of the two deadlines: - Early bird entries must be submitted by December 31st - Standard entries must be submitted by February 28th You also have to submit your application to the "Mobile Contest" category on Qt-Apps.org or MeeGo-Central.org You can submit your application to the Ovi Store as many times as you wish during the competition. This allows you to get feedback from the public on your software. It´s possible to submit new or existing KDE/Qt applications So have fun and good luck everybody! ... Niels http://nielsmayer.com ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Audio problem when connecting to internet in IVI
On Fri, Dec 3, 2010 at 7:36 PM, Manoj Cr wrote: > Am working on Meego IVI on Intel Atom. > We have been developing an application which has an audio playback using > ALSA.I works well initaillay but the moment i connect my board to internet , > audio gets automatically disabled.Has anybody faced this issue ??Is it > because some update happens to alsa drivers when i connect to internet and > it gets corrupted. Just a random thought: What happens if you turn off frequency scaling so that the processor is always running at the same clockrate. I'm mentioning this because I've seen linux audio apps, especially when they're talking directly to ALSA, have problems with CPU frequency scaling. A random google search, for example, turned up this: http://www.linuxquestions.org/questions/linux-software-2/alsa-troubles-triggered-by-cpu-usage-453796/ -- Niels http://nielsmayer.com ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] meego 1.1 handset more efficient&performant from n900's fast internal memory?
A note regarding dual-booting Nitdroid (*) from Maemo n900 (unfortunately incompatible w/ uboot and therefore meego) suggests why Meego 1.1 performance and battery life seems significantly lower when compared to latest production Maemo on n900. http://talk.maemo.org/showthread.php?p=887394#post887394 . Some things you'll notice after installing it on the internal memory: 1. Runs 10 times faster, even faster than a class 8 card. 2. The battery doesn't drain fast. Had it off charger all day playing games and surfing the internet and got it to only use 40% of the battery. 3. Pretty good given now you can use it without it draining the battery! . Is there a way a similar "dual boot" technique could be developed to run Meego 1.1 in a fashion closer to it's intended "product" state -- running on the n900's internal memory? Seems like this would solve some of the performance (e.g. slow app launch) and battery-life problems. Note that I'm not complaining, I am absolutely jazzed to be able to run a recent linux kernel on a hand-held device and cross-develop with qt-creator and madde; soon enough, I'm sure Meego's performance on OMAP4-class processors will be better than Maemo's. Niels http://nielsmayer.com PS: (*): I was looking into http://www.nitdroid.com/ in order to test/use http://ytd-android.googlecode.com for developing Meego youtube-direct client http://ytd-meego.googlecode.com . ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] YTD-Meego on Googlecode - Planning Youttube direct uploading app
I've created http://code.google.com/p/ytd-meego/ for the port of ytd-android to Meego using QtQuick/QML. YTD-Meego is to be a feature-equivalent port of the Youtube-direct application for Android ( http://ytd-android.googlecode.com/ ). Initially, the purpose of the googlecode project will be for issue-tracking and planning features and their implementation in QtQuick. The subversion repository will eventually contain working snippets of QtQuick test code that will evolve into an application with the help of the community. Please send mail if you want to be added as a project contributor for contributing these working code snippets and developing this application. I have platform-related QtQuick deveveloper questions, but for some reason, they haven't yet appeared in the Meego archives/lists of "Announcing Youttube-API project for Meego // Vote on googlecode project name": http://lists.trolltech.com/pipermail/qt-qml/2010-November/001553.html http://lists.trolltech.com/pipermail/qt-qml/2010-November/001556.html -- Niels http://nielsmayer.com ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] [MeeGo-community] Announcing Youttube-API project for Meego // Vote on googlecode project name
I found two useful apps for study, which although not directly related to the youtube-direct app, cover aspects of programming needed for the task and give examples of this style of application using QtQuick: (1) "Simple Qt Quick based Flickr client for N900." http://zchydem.enume.net/2010/09/07/quickflickr-available-at-extras-testing/ http://maemo.org/packages/view/quickflickr/ http://www.gitorious.org/quickflickr (2) "IcecastRadio - Qt widget/Qt Quick example Icecast player" http://pysnippet.blogspot.com/2010/09/icecastradio-qt-widgetqt-quick-example.html http://gitorious.org/icecastradio However, I'm having trouble building these using meego-sdk-qt-creator-2.0.1-24.1.x86_64 . I've previously built/modified"qthello" per http://wiki.meego.com/SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Linux#Configuring_Qt_Creator_to_use_the_MeeGo_toolchain.28s.29 -- at least simple programs build and run. With these examples, despite choosing builds for the handset using "/usr/lib64/madde/linux-x86_64/targets/meego-core-armv7l/bin/qmake" , I get the following errors: (1) For quickflickr: :: error: cannot find -lQtWebKit :: error: collect2: ld returned 1 exit status Question: how can I get QtWebKit within a QtQuick project built for the handset? Although the meego yt-direct may not need a visual browser, I other components of QtWebKit may be needed for this task. (2) For IcecastRadio: icecastradio-build-meego/model/../../icecastradio/model/streaming/streaming.cpp:23: error: phonon/MediaObject: No such file or directory Question: What's the approved way of doing streaming sound playback if phonon isn't present? Corollary: How about video playback in a QtQuick app? Examples? The real reason for looking at icecastradio was to see how QtQuick handled setting up a streaming media connection; in the meego yt-direct, one may want to both upload, and playback captured audio or video. Any QtQuick examples showing how to do streaming video playback? (Easy enough in a standard Qt app, http://wiki.forum.nokia.com/index.php/QtMobilityYouPlayer but that example is not QtQtuick.). Is there a way of integrating the functionality of http://space.twc.de/~stefan/gst123.php . Gst123 helps setup the appropriate gstreamer pipeline for appropriate decoding of internet audio or video: "mplayer can play any file gst123 can, but gst123 is just a fraction of the code size, since the real work is done by GStreamer. That way the codecs are shared with many other projects which hopefully will lead to better quality decoding code." ( http://download.famouswhy.com/publisher/stefan_westerfeld ) -- Niels http://nielsmayer.com ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] [MeeGo-community] Announcing Youttube-API project for Meego // Vote on googlecode project name
> On Wed, Nov 3, 2010 at 4:28 PM, Jarek Wilkiewicz wrote: > Hi Niels, > thank you for getting the discussion started! > Couple of initial thoughts : > 1. I think that ytd-meego uploader/client (2) could interface with the > existing youtube-direct implementation. This will make it attractive for > folks in the community who have already deployed YouTube Direct and want to > use it with MeeGo devices, this page has some examples (scroll to the bottom > of the page) : www.youtube.com/direct . Therefore, form my perspective the > near-term prio of meetube (1) as a replacement/port of youtube-direct is not > clear, unless I misunderstood the purpose of meetube. Hi Jarek -- thanks for the helpful response! Part of getting this discussion started was to help understand what the task is in the first place. Your reply and some further study helps me understand the "why" better. As a developer using the Youtube API, my first take on this task was that it would represent additional complication for integrating into an existing platform -- I'd probably just use the API directly. However, now that I've seen some of the examples and press-releases and role/deployment of YT-direct, I better understand the purpose of "meetube" as enabling easier access for existing YT-direct-enabled websites sites with the Meego platform, e.g. : http://gigaom.com/video/youtube-direct-abc7/ http://www.digitaltrends.com/computing/youtube-direct-is-helping-media-find-free-videos/ . Given the media capabilities of the Nokia N8 platform, having a capture and uploading application that makes them easy to use is a compelling "platform story" for Meego. Given the example yt-direct apps for Android and Iphone, the purpose of yt-direct for meego would be the development of a platform-integrated media capture, uploading and management tool. This would allow a single app to record audio or video and upload it to a yt-direct site without needing to separately capture media and manually upload it via the web interface. The meego yt-direct app would automatically authenticate to the chosen submission site based on stored account information, automatically geotags captured media, tracks the YouTube Direct JSON assignment feed, and tracks status of media considered for submission. > 2. Wrt the YouTube API itself, we currently have multiple language bindings > (see the list here : http://code.google.com/apis/youtube/code.html), but I'm > not sure if they're adequate for MeeGo developers. The good news is that the > APIs can be accessed using straight REST/HTTP, and this is, in fact, what > ytd-android currently does. Now that I better understand the original task and the underlying goal, the task really is a direct port of the existing ytd-android app to Meego. I saw all the code in project "youtube-direct" and saw much browser-specific Javascript, and thought that was a necessary part of the application. I now understand that a custom upload client wouldn't need an embedded web-browser in which to run JavaScript. The existing AJAX code is just for uploading from the browser. Therefore, the task is a port of the existing ytd-android functionality from Java to Qt, without the need for "hybrid application development" and an embedded browser based on QtWebKit. The android app provides the following main functionality/implementation: * http://code.google.com/p/ytd-android/source/browse/trunk/src/com/google/ytd/SubmitActivity.java ** appears to be the core of the upload part of the application. ** http://code.google.com/apis/youtube/2.0/developers_guide_java.html#Uploading_Videos * http://code.google.com/p/ytd-android/source/browse/trunk/src/com/google/ytd/GlsAuthorizer.java ** This handles authorization and subscription: ** http://code.google.com/apis/youtube/2.0/developers_guide_protocol.html#Authentication ** http://code.google.com/apis/accounts/docs/AuthSub.html From the above, it appears there's nothing here that couldn't be achieved in other languages or platforms. This could be handled by a standard C++ Qt application that makes and responds to web requests -- basically a modified version of http://wiki.forum.nokia.com/index.php/QtMobilityYouPlayer with capture, uploading, and geotagging functionality added. Even easier would be to implement with QtQuick. The following gives programming examples for doing the web authentication for twitter: http://gitorious.org/qt-qml-demo-playground/qt-qml-demo-playground/trees/master/twitter-oauth http://gitorious.org/qt-qml-demo-playground/qt-qml-demo-playground/blobs/master/twitter-oauth/TwitterCore/OAuth.js Any other related Qt/QML example apps people can point me to? In addition to creating a custom UI backed by HTTP transactions, other functionality needed includes: (1) Using QtQuick to access geotagging locations when media captured. (2) Using QtQuick to capture, compress, and store media from camera and/or microphone. (3) Using QtQuick to access system-stored authentication information.
Re: [MeeGo-dev] Announcing Youttube-API project for Meego // Vote on googlecode project name
[I forgot to send this to meego-dev -- as this is developer related,
please post replies to meego-dev]
On Wed, Nov 3, 2010 at 11:26 AM, Niels Mayer wrote:
> A few weeks ago, Quim Gil posted a request to port Youtube-direct to
> some meego lists and IRC:
>> Qt Quick developer wanted to develop openly a port of
>> http://code.google.com/p/youtube-direct/ - documenting the experience
>> dealing with YouTube APIs and Android code. The prize will be an N900 to
>> test and a dose of fame in the MeeGo, YouTube and Google developer
>> communities.
>
> As I lack a N900, and can apply my experience in the myriad divergent
> underlying technoligies employed in the youtube-direct, I'm putting
> forward my intention to lead this project, which is clearly more than
> a "one person" project in scope. In return, I'm hoping to gain some
> practical experience in using QtQuick/QML and developing "hybrid"
> web/media handheld apps on Meego. I'm working on a java-based
> web-application which will eventually make use of Youtube API's (
> http://nielsmayer.com/trainspodder-prototype.jpg
> http://nielsmayer.com/ts-episode-timeline.png ) and for which I intend
> to build a handheld interface in Meego employing both AJAX-style
> JavaScript Browser-Based UIs, combined with native linux
> functionality, to enable tightly-synchronized audio/video&hypermedia
> -- both for playback and upload.
>
> My initial analysis is that porting
> http://youtube-direct.googlecode.com for Meego will be more complex
> than necessary if we take a direct path in creating something
> competitive with http://ytd-android.googlecode.com and
> http://ytd-iphone.googlecode.com . There's a certain
> Rube-Goldbergification that happens when you split up your apps AJAX
> style -- see the considerable amount of setup needed to get the
> google-app-engine part working (
> http://groups.google.com/group/youtube-api-gdata/browse_thread/thread/a67cd4a41692a6ec/f9f40268137bc742
> ). Additionally, there's the dependency on Eclipse IDE, which becomes
> impractical given that QtCreator is Meego's IDE. Ultimately, all the
> "java cloud" gives you for this app is performance problems that
> cannot easily be resolved:
> ( http://groups.google.com/group/youtube-api-gdata/msg/ada27fc26a08b78e
> ). And the "cloud" is totally unnecessary, since Java is performing
> computations that could easily be carried out by a Qt4 app running on
> a handheld using traditional REST web programming style.
>
> The first question to ask in such a project is whether youtube-direct
> is even solving the right problem given the strength of the client
> platform provided by Linux and Qt?
>
> Is this "java cloud" approach even necessary, or is it a "wart"
> associated with AJAX style UIs? IMHO simple REST (
> http://en.wikipedia.org/wiki/Representational_State_Transfer ) should
> handle it. For example
> http://wiki.forum.nokia.com/index.php/QtMobilityYouPlayer makes use of
> the Youtube API, but doesn't require a app-engine back-end to host the
> application. Unlike AJAX-style programming, the decision of how much
> processing can be done locally versus "in the cloud" isn't already
> pre-chosen for you and the application architecture doesn't end up
> being twisted to suit the security limitations of the client. Other,
> much-simpler implementations of Youtube-direct exist which don't need
> google-app-engine at all, e.g.:
> http://groups.google.com/group/youtube-api-gdata/browse_thread/thread/670c6a0867ca3852/45e97f0feb2e7244
> ("Youtube Direct Upload with clientlogin :: PHP without client library")
> http://groups.google.com/group/youtube-api-gdata/browse_thread/thread/280115751a3ba86/cd76b66db7e797ce
> ("Delete a playlist with PHP (You must specify an URI to which to
> post) Options").
>
> If we do go with the approach of a "direct" port employing all the
> browser-based AJAX code, then does it make sense to use
> http://wiki.forum.nokia.com/index.php/Hybrid_Application_Generator ?
> It's clear this kind of AJAX-based application needs an integrated
> javascript-enabled browser (QtWeb) and additional code support for
> "platform natitve" audio/video uploading, audio/video playback,
> GPS/geotagging etc. Alternately, I've also been told to investigate
> the QML bindings for QtMobility Media APIs.
>
> For "baseline functionality" lets consider what "Android YTD mobile
> uploader" does:
> (
> http://groups.google.com/group/youtube-api-gdata/browse_thread/thread/17020651ef1aa52b/64a0a0a9031766d2
> )
> * Integration with Android's Account
