[MeeGo-dev] Device Management

[Clark, Joel]

Is any work being done in MeeGo to define a standardized framework and APIs for 
device management?

regards
Joel

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Geoclue and Qt Mobility on MeeGo

[Arjan van de Ven]

On 10/28/2010 6:10 PM, Sivan Greenberg wrote:

Re reading about MeeGo's  architecture, is Geoclue the engine or the
"backend" for Qt's Mobility location and positioning APIs?

If not, what is the relationship ?



geoclue is the reference back end. Geoclue however is not a manadatory 
component.
It's very likely that some commercial implementations of MeeGo will have 
their own custom back end,
especially to tie into location services (maps etc) that service 
providers provide for a fee.



___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] DVB support on MeeGo

[vijay singh]

Hi,
Currently it is not getting detected with MeeGo1.0 release.

I am testing below DVB-t device.

CINERGY DT USB XS.
//http://www.terratec.net/en/products/tv/dvbt.html

Please let me know if any one tested DVB-t on MeeGo or any plan to
provide support for all DVB device in MeeGo.

Cheers--

On Thu, 2010-10-28 at 13:29 -0700, Rudolf Streif wrote:
> I am afraid we are losing the focus in regards to Vijay's original
> question. Vijay did not say for what type of device he is looking for
> DVB support from MeeGo.
> 
> 
> Digital television, DVB-T and ATSC, requires different antennae then
> analog TV for UHF/VHF. For those the aerials had to be pointed to the
> transmitter. For DTV that is typically not necessary. It is possible
> to receive the signals with simple "rabbit ears" even from inside a
> home. However, that is as usual dependent on environmental and other
> factors.
> 
> 
> Rudi
> 
> On Thu, Oct 28, 2010 at 1:05 PM, Ross Burton 
> wrote:
> On Thu, 2010-10-28 at 21:40 +0200, Randolph Dohm wrote:
> > Hi Ross,
> > no, it is not about DVB-H, that is dead born, it is about
> DVB-T.
> > So users can watch TV without payment like in any TV.
> > That makes the success, if it is default in. Nokias Key.
> 
> 
> If I want to watch DVB-T at home I need a rather large aerial
> that is
> aimed at the transmitter.  How does that work on a mobile
> device?
> 
> 
> Ross
> --
> Intel Open Source Technology Centre
> http://oss.intel.com/
> 
> 
> 
> 
> 
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Geoclue and Qt Mobility on MeeGo

[Juha.Vuolle]

Yes,

There is a draft implementation:
http://qt.gitorious.org/~juhvu/qt-mobility/meego-location-qt-mobility

Juha

-Original Message-
From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On 
Behalf Of ext Sivan Greenberg
Sent: Friday, October 29, 2010 11:11 AM
To: meego-dev
Subject: [MeeGo-dev] Geoclue and Qt Mobility on MeeGo

Re reading about MeeGo's  architecture, is Geoclue the engine or the
"backend" for Qt's Mobility location and positioning APIs?

If not, what is the relationship ?

Thanks

-Sivan

(Since these subjects appear to be part of the core stack, I felt
comfortable to discuss this here and not on meego-sdk)
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] Geoclue and Qt Mobility on MeeGo

[Sivan Greenberg]

Re reading about MeeGo's  architecture, is Geoclue the engine or the
"backend" for Qt's Mobility location and positioning APIs?

If not, what is the relationship ?

Thanks

-Sivan

(Since these subjects appear to be part of the core stack, I felt
comfortable to discuss this here and not on meego-sdk)
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Has the new kernel process been established?

[Eugene Seah]

On 10/28/10 15:05, Carsten Munk wrote:

http://wiki.meego.com/MeeGo_kernel_documentation_for_contributors
seems up to date, as well as subscribe to meego-kernel mailing list,
it's very active.

General contribution guidelines at
http://meego.com/about/contribution-guidelines

BR
Carsten Munk

   

Thanks!

2010/10/28 Eugene Seah:
   

Bumping this question, would be interested in whether the new kernel process
has been finalized/documented.

From: http://wiki.meego.com/Kernel_Process_Obsolete

"UPDATE: 2010-05-27 - Per discussion on the meego-dev mailing list, Arjan
van de Ven has indicated that he's the Intel employee responsible for the
kernel, and that procedures Intel said would be put into place are being
finalized/documented right now."

On 08/03/10 20:19, Liu, Haibo wrote:

Hi MeeGoers,

According to MeeGo Wiki, a new kernel process is being finalized now. Just
wonder if there is still any general process I should follow if I want to
make the newest kernel version work on my netbook? And where should I find
the news about this new kernel process, will it be posted on Wiki page?

P.S. I’ve checked out the newest version of kernel source and followed the
obsolete process to compile it and failed. The scripts failed to mkdir for
linux-2.6.33-{tags}.orig. I’m trying to make this work now. Hope anybody
tells me it’s unnecessary.

Best  Regards,

Liu Haibo  (Lewis)
Technical Marketing Engineer, ATPS/SMG
E-mail:  haibo@intel.com
Office:  8610-8507-1310
iNet:8751-1310
Cell:138-103-20201




___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev


 


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Has the new kernel process been established?

[Carsten Munk]

http://wiki.meego.com/MeeGo_kernel_documentation_for_contributors
seems up to date, as well as subscribe to meego-kernel mailing list,
it's very active.

General contribution guidelines at
http://meego.com/about/contribution-guidelines

BR
Carsten Munk

2010/10/28 Eugene Seah :
> Bumping this question, would be interested in whether the new kernel process
> has been finalized/documented.
>
> From: http://wiki.meego.com/Kernel_Process_Obsolete
>
> "UPDATE: 2010-05-27 - Per discussion on the meego-dev mailing list, Arjan
> van de Ven has indicated that he's the Intel employee responsible for the
> kernel, and that procedures Intel said would be put into place are being
> finalized/documented right now."
>
> On 08/03/10 20:19, Liu, Haibo wrote:
>
> Hi MeeGoers,
>
> According to MeeGo Wiki, a new kernel process is being finalized now. Just
> wonder if there is still any general process I should follow if I want to
> make the newest kernel version work on my netbook? And where should I find
> the news about this new kernel process, will it be posted on Wiki page?
>
> P.S. I’ve checked out the newest version of kernel source and followed the
> obsolete process to compile it and failed. The scripts failed to mkdir for
> linux-2.6.33-{tags}.orig. I’m trying to make this work now. Hope anybody
> tells me it’s unnecessary.
>
> Best  Regards,
>
> Liu Haibo  (Lewis)
> Technical Marketing Engineer, ATPS/SMG
> E-mail:  haibo@intel.com
> Office:  8610-8507-1310
> iNet:    8751-1310
> Cell:    138-103-20201
>
>
>
>
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev
>
>
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev
>
>
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Has the new kernel process been established?

[Eugene Seah]

Bumping this question, would be interested in whether the new kernel 
process has been finalized/documented.


From: http://wiki.meego.com/Kernel_Process_Obsolete

"UPDATE: 2010-05-27 - /Per discussion on the meego-dev 
 
mailing list, Arjan van de Ven has indicated that he's the Intel 
employee responsible for the kernel, and that procedures Intel said 
would be put into place are being finalized/documented right now."


/On 08/03/10 20:19, Liu, Haibo wrote:

Hi MeeGoers,
According to MeeGo Wiki, a new kernel process is being finalized now. 
Just wonder if there is still any general process I should follow if I 
want to make the newest kernel version work on my netbook? And where 
should I find the news about this new kernel process, will it be 
posted on Wiki page?
P.S. I've checked out the newest version of kernel source and followed 
the obsolete process to compile it and failed. The scripts failed to 
mkdir for linux-2.6.33-{tags}.orig. I'm trying to make this work now. 
Hope anybody tells me it's unnecessary.

Best  Regards,
Liu Haibo  (Lewis)
Technical Marketing Engineer, ATPS/SMG
E-mail:  haibo@intel.com
Office:  8610-8507-1310
iNet:8751-1310
Cell:138-103-20201


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
   


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] DVB support on MeeGo

[Rudolf Streif]

I am afraid we are losing the focus in regards to Vijay's original question.
Vijay did not say for what type of device he is looking for DVB support from
MeeGo.

Digital television, DVB-T and ATSC, requires different antennae then analog
TV for UHF/VHF. For those the aerials had to be pointed to the transmitter.
For DTV that is typically not necessary. It is possible to receive the
signals with simple "rabbit ears" even from inside a home. However, that is
as usual dependent on environmental and other factors.

Rudi

On Thu, Oct 28, 2010 at 1:05 PM, Ross Burton  wrote:

> On Thu, 2010-10-28 at 21:40 +0200, Randolph Dohm wrote:
> > Hi Ross,
> > no, it is not about DVB-H, that is dead born, it is about DVB-T.
> > So users can watch TV without payment like in any TV.
> > That makes the success, if it is default in. Nokias Key.
>
> If I want to watch DVB-T at home I need a rather large aerial that is
> aimed at the transmitter.  How does that work on a mobile device?
>
> Ross
> --
> Intel Open Source Technology Centre
> http://oss.intel.com/
>
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] DVB support on MeeGo

[Randolph Dohm]

2010/10/28 Ross Burton :
> If I want to watch DVB-T at home I need a rather large aerial that is
> aimed at the transmitter.  How does that work on a mobile device?

ask, Gigabyte T 600
http://www.gigabytecm.com/Eng/ProductOview.aspx?pid=40
if you are from intel, I wounder why you haven´t minituarized that chip already.
That is why politicians say to buy japanese instead of german, because
the technical engineers here sleep over the hybrid cars.
Maybe Intel, the MOTHER of small chips, does not know how gigabyte
makes small DVB-T chips?
Honey, this is the REAL link between Nokia and Intel, you should
explore after nokia announced to use ARM chips only.
N9 with DVB-T on Meego would be a worldwide successfactor against
android and google/apple TV.
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Meego Bugs Access Denied

[Ryan Ware]

On Thu, Oct 28, 2010 at 12:37 PM, Warren Baird
wrote:

> On Thu, Oct 28, 2010 at 2:17 PM, Ryan Ware  wrote:
> >
> >
> > There are a number of bugs in the MeeGo Bugzilla that are restricted
> > specifically to the security group.
>
> I suspect everyone understands the need to limit access to security
> bugs - I certainly do.   However, the OP and the immediate follow up
> made no mention of security issues...
>
> If the only issues with restricted access are security issues, that's
> great - but Eric's follow seems to imply that there are non-security
> bugs that will be restricted, and that we can expect more until some
> non-described problem is sorted out...
>
> If some bugs are being restricted without a good reason - I'd agree
> with Bradley that it's a pretty serious issue.
>
>
>
Thanks for the understanding on security issues.  I know that this
discussion wasn't really kicked off because of a bug with security concerns,
but I wanted to put my position on that out to the community because it was
subsequently brought up.  I also agree that if there is not a good reason
that is broadly accepted by the community as to why a bug or class of bugs
is closed to the community, there is a significant issue that needs to be
addressed.

Ryan
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] DVB support on MeeGo

[Ross Burton]

On Thu, 2010-10-28 at 21:40 +0200, Randolph Dohm wrote:
> Hi Ross,
> no, it is not about DVB-H, that is dead born, it is about DVB-T.
> So users can watch TV without payment like in any TV.
> That makes the success, if it is default in. Nokias Key.

If I want to watch DVB-T at home I need a rather large aerial that is
aimed at the transmitter.  How does that work on a mobile device?

Ross
-- 
Intel Open Source Technology Centre
http://oss.intel.com/
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] DVB support on MeeGo

[Randolph Dohm]

Hi Ross,
no, it is not about DVB-H, that is dead born, it is about DVB-T.
So users can watch TV without payment like in any TV.
That makes the success, if it is default in. Nokias Key.

2010/10/28 Ross Burton :
> On Thu, 2010-10-28 at 19:35 +0200, Randolph Dohm wrote:
>> DVB-T Support needs a connector to the antenna?
>> there was only ONE phone having DBV-T in the phone:
>> Gigabyte T 600
>> http://www.gigabytecm.com/Eng/ProductOview.aspx?pid=40
>>
>> that would be a selling success, if any nokia hardware would allow
>> with meego to watch terrestrial tv on the phone...
>
> Several Nokia phones support DVB-H though I don't know where that is
> transmitted...
>
> Personally I've dubious that proper TV-in-a-phone is that useful.  On
> demand playback with the ability to pause and so on for when I have to
> get off a train, sure.
>
> Ross
> --
> Intel Open Source Technology Centre
> http://oss.intel.com/
>
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Meego Bugs Access Denied

[Warren Baird]

On Thu, Oct 28, 2010 at 2:17 PM, Ryan Ware  wrote:
>
>
> There are a number of bugs in the MeeGo Bugzilla that are restricted
> specifically to the security group.

I suspect everyone understands the need to limit access to security
bugs - I certainly do.   However, the OP and the immediate follow up
made no mention of security issues...

If the only issues with restricted access are security issues, that's
great - but Eric's follow seems to imply that there are non-security
bugs that will be restricted, and that we can expect more until some
non-described problem is sorted out...

If some bugs are being restricted without a good reason - I'd agree
with Bradley that it's a pretty serious issue.

Warren


-- 
Warren Baird - Photographer and Digital Artist
http://www.synergisticimages.ca
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] DVB support on MeeGo

[Ross Burton]

On Thu, 2010-10-28 at 19:35 +0200, Randolph Dohm wrote:
> DVB-T Support needs a connector to the antenna?
> there was only ONE phone having DBV-T in the phone:
> Gigabyte T 600
> http://www.gigabytecm.com/Eng/ProductOview.aspx?pid=40
> 
> that would be a selling success, if any nokia hardware would allow
> with meego to watch terrestrial tv on the phone...

Several Nokia phones support DVB-H though I don't know where that is
transmitted...

Personally I've dubious that proper TV-in-a-phone is that useful.  On
demand playback with the ability to pause and so on for when I have to
get off a train, sure.

Ross
-- 
Intel Open Source Technology Centre
http://oss.intel.com/


signature.asc
Description: This is a digitally signed message part
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] Updated broadcom wireless instructions for 1.1

[Glen Gray]

Hey folks, I pushed out some updates the other day in preparation for the 1.1 
release. Updated to use zypper and to pull the latest broadcom source.

http://slaine.org/_slaine/Meego_1.1_Wifi.html

Let me know if you have any problems with the instructions.
--
Glen Gray
sla...@slaine.org




___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] MeeGo 1.1 Handset Calrendar name bug ?

[Quim Gil]

On Thu, 2010-10-28 at 20:27 +0200, ext Pain Chung wrote:
> Calendar app shows wrong name. It shows 'meego-handset-calendar'
> instead of 'Calendar'.
> I found this wrong name below file.
> 
> 
>   '/usr/share/applications/meego-handset-calendar.desktop'
> "Name[en_US]=meego-handset-calendar.desktop"
> 
> 
> Is it any reason ?

Please check if there is a bug filed for this at http://bugs.meego.com
and if not you are encouraged to file it yourself. The same goes for
other localization issues and any bugs you find in the 1.1 release.

This is a high traffic mailing list and actually Bugzilla is a much more
efficient way to report the problems to the people that can actually fix
them.

Thank you!

--
Quim

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] OBS, MeeGo and the social desktop : Application information, feedback and rating

[Ville M. Vainio]

On Thu, Oct 28, 2010 at 2:03 PM, David Greaves  wrote:

> MeeGo community does provide a community build system.. the OBS ... which,
> as you say, needs to support rating/feedback somehow. The OBS has a rating
> system... no-brainer (well, at least as a potential solution).

I stand corrected. Yes, this would make sense.

-- 
Ville M. Vainio @@ Forum Nokia
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] MeeGo 1.1 Handset Calrendar name bug ?

[Pain Chung]

Calendar app shows wrong name. It shows 'meego-handset-calendar' instead of
'Calendar'.
I found this wrong name below file.

  '/usr/share/applications/meego-handset-calendar.desktop'
"Name[en_US]=meego-handset-calendar.desktop"

Is it any reason ?

thanks,
Pain
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Meego Bugs Access Denied

[Ryan Ware]

On Thu, Oct 28, 2010 at 6:18 AM, Thiago Macieira  wrote:

> On Thursday, 28 de October de 2010 05:44:09 Bradley Smith wrote:
> > You need to be presenting a darn good reason why bugs are not being
> > shown to everyone.
>
> Usually that reason is "security issue" or "customer sensitive
> information".
>
> But like you said, there should be a way to request access for people who
> need
> to know.
>
>
There are a number of bugs in the MeeGo Bugzilla that are restricted
specifically to the security group.  They remain closed to only the security
group, the bug submitter and the cc list until a fix for the security issue
is available.  Once a fix is available, the bug is made public.  The reason
for this is that until a fix is in place, the bug is essentially a map on
how to exploit a MeeGo system.  We also have commitments to keep certain
bugs embargoed until a fix is available for the majority of Linux
distributions.

While I strongly appreciate the need for access of information in an open
project like this (and I try to error on the side of the community), this is
also best practices as followed by all the leading Linux distributions.

If anyone here feels that they need access to a specific security related
bug, please send me an email and I will evaluate and see what we can do.

Thanks,

Ryan
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Meego Bugs Access Denied

[Auke Kok]

On 10/28/10 02:28, Gary Birkett wrote:

Hey,

I have encountered a number of bugs this morning as part of my work on
the meego bug tracker which are giving an error:
"You are not authorized to access bug #[bugid]"
(related to something I expected to read and digest)

This issue effects people in other areas too

A specific example this morning was stskeeps could not access
http://bugs.meego.com/show_bug.cgi?id=8474


I just removed this restriction on this bug, there's no reason why it 
ever should have been restricted to begin with.


Auke
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] DVB support on MeeGo

[Randolph Dohm]

DVB-T Support needs a connector to the antenna?
there was only ONE phone having DBV-T in the phone:
Gigabyte T 600
http://www.gigabytecm.com/Eng/ProductOview.aspx?pid=40

that would be a selling success, if any nokia hardware would allow
with meego to watch terrestrial tv on the phone...

2010/10/28 Rudolf Streif :
 DVB-T
> and DVB-T2 for terrestrial transmission,
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] DVB support on MeeGo

[Rudolf Streif]

Vijay,

There is actually no simple and straightforward answer to any system
supporting Digital Video Broadcasting because it is a multilayer
architecture.

DVB uses MPEG-2 Transport Streams (MP2TS) as defined by ISO/IEC 13818-1
Systems with DVB-specific Service Information (SI) as specified in ETSI EN
300 468.

For transmission these streams are modulated onto a bearer. What the bearer
is depends on the transmission system. Hence, DVB specifies multiple
standards: DVB-S and DVB-S2 for satellite transmission, DVB-SH for satellite
transmission to handhelds, DVB-C and DVB-C2 for cable transmission, DVB-T
and DVB-T2 for terrestrial transmission, and DVB-H for terrestrial
transmission to handhelds. The standards use different modulation and
modulation schemes such as QAM, PSK, QPSK, APSK, etc. Most recently
DVB-compliant MP2TS are also used in IPTV and there the transmission is an
IP network using UDP unicast/multicast and/or TCP dependent on the
application. Sometimes for IPTV the streams are RTP-encapsulated and may
also use Quality of Experience (QE) technologies such as Cisco's VQE or
Alcatel-Lucent's FCC/RET.

Here starts the first layer of the problem. Dependent on how your MeeGo
system will receive the DVB MP2TS you will need hardware to do the
demodulation. For that you will obviously a driver, typically a character
device driver as kernel module. If your system receives the stream via IP
you are all set.

Once you got to MP2TS you will have to demultiplex it. MeeGo uses gstreamer
and one of the container formats it supports is MP2TS. After that the
elementary streams need to be decoded. Most importantly video and audio and
for that gsteamer supports a variety of codecs. If you need to be able to
decode the SI for EPG etc. in the DVB MP2TS then you will probably need a
plugin for gstreamer to decode it.

DVB television programs may be encrypted with a CA system. That adds another
layer of complexity since you wont be able to decode the elementary streams
unless they are decrypted. DVB systems mostly use transport scrambling
control meaning the payload of the MP2TS packets is encrypted. What packets
are encrypted is indicated by the 2 TSC (transport scrambling control) bits
in the MP2TS header.

Best regards,
Rudi



On Wed, Oct 27, 2010 at 10:43 PM, vijay singh  wrote:

> Hello,
> I want to know do we have support for DVB under MeeGo 1.0 or planned
> MeeGo 1.1 release.
>
> Bye--
>
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev
>
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Captive portals detection

[Amit Bapat]

On Thu, Oct 28, 2010 at 1:59 AM, punit bisht  wrote:

> Hi,
>
> Does anyone know how to detect a guest network as a captive portal.
>

I don't know how it's done, but here's an idea: When inside captive portal
and in login mode, DNS responds with same IP address for any query. So that
the browser will first hit the login page. So try may be a couple of
completely different known host name searches which should yield different
IP address answers, if they give same answer, you're in login mode.

-- 
Amit Bapat
System Software Marketing
Intel Corporation
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] Problem running Meego on iMX51

[Sah, Shitij SISPL]

Hi,

I have built the Meego file system using the .ks attached. Built X11 
(X11R6.9.0) separately. Copied the built files into respective folder in the 
rootfile. Changed /etc/sysconfig/desktop which is attached. Every time mingetty 
respwans. uxlaunch and Xorg log files are attached. Where is the problem?

There is one error  xf86EnableIOPorts: failed to set IOPL for I/O. I don't know 
how to resolve it.

Regards,
Shitij




Important notice: This e-mail and any attachment there to contains corporate 
proprietary information. If you have received it by mistake, please notify us 
immediately by reply e-mail and delete this e-mail and its attachments from 
your system.
Thank You.


Xorg.0.root.log
Description: Xorg.0.root.log


desktop
Description: desktop


N900HandsetwithXrootlogin26-10-10.ks
Description: N900HandsetwithXrootlogin26-10-10.ks


uxlaunch.log
Description: uxlaunch.log
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] Multi-point touch and gestures plan for MeeGo 1.2 & 1.3

[Thiago Macieira]

Hello all

This week, I met with James Ketrenos from Intel and some Canonical developers 
at their summit and we discussed how we should approach the subject of 
standardising touch and gestures events in the Linux / X11 world.

Premises:

1) MeeGo 1.2 does not want to upgrade to X.org 1.10

2) X.org maintainers have said that they do not want to rush the feature and 
they would most likely not accept it even if it were ready and tested by 
December 1st this year.

With that in mind, we propose that MeeGo 1.2 implements a temporary solution 
based on the existing XInput 2.0 work that Nokia has done for Harmattan.

Details:

MeeGo 1.2:


Use the mtev X.org driver from Nokia

Apply the matching XInput 2.0 patch on Qt to deliver QTouchEvents and thus 
enable the gesture recogniser.

Do not use the solutions being developed by Ubuntu at this time (geis, grail, 
utouch).

System-level gestures will be implemented in a platform-specific way (using 
XInput 2 facilities not designed for this purpose), by making the Window 
Manager use passive X grabs on the XInput 2 events and transforming them into 
active grabs when the gesture is detected.

Qt will consider re-developing the XInput 2.0 complete-mouse-system-rewrite 
patch and make it smaller, given the direction that XInput 2.1 is going. This 
should reduce the maintenance load. James has a patch for this already and Qt 
developers will analyse.

If the grab mechanism doesn't work in XInput 2.0, the mtev driver should be 
modified to deliver the events first to the WM via some out-of-band 
communication mechanism.

No API compatibility is guaranteed at this point beyond Qt's existing API 
(QTouchEvent, the gesture system). The configuration of system gestures and the 
details of XEvent protocol for multiple points in a touch are not guaranteed 
API or ABI stability. More strongly: it will break, so applications can *only* 
use Qt's API, if they want to transition to MeeGo 1.3 without rewrite.


MeeGo 1.3:


For MeeGo 1.3, we must upgrade to X.org 1.11, to be released around August / 
2011.

This release should include the touch and gestures standardised subsystem in 
X, developed in close cooperation with Canonical and other partners.

XInput 2.1 will be the method of delivery of touch events in X11. The 
recognition of common gestures (global configuration of gestures that all 
applications react to) will be provided by a separate library that is fed 
events and provides reactions similar to Qt's gesture system.

System-wide gestures will probably use passive grabs using XInput 2.1.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
  PGP/GPG: 0x6EF45358; fingerprint:
  E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358


signature.asc
Description: This is a digitally signed message part.
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Meego Bugs Access Denied

[eric.le-roux]

Hi,

>-Original Message-
>From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com]
>On Behalf Of ext Thiago Macieira
>Sent: 28 October, 2010 16:18
>To: meego-dev@meego.com
>Subject: Re: [MeeGo-dev] Meego Bugs Access Denied
>
>On Thursday, 28 de October de 2010 05:44:09 Bradley Smith wrote:
>> You need to be presenting a darn good reason why bugs are not being
>> shown to everyone.
>
>Usually that reason is "security issue" or "customer sensitive
>information".
>
This seems to fall under the "csi" category probably.

>But like you said, there should be a way to request access for people
>who need to know.
>
As far as I can tell, this situation is exceptional and we should return to 
normal very soon.
I completely understand the frustration and actually share it...

>--
>Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
>  Senior Product Manager - Nokia, Qt Development Frameworks
>  PGP/GPG: 0x6EF45358; fingerprint:
>  E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

Cheers,
Eric Le Roux
MeeGo error management lead
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Meego Bugs Access Denied

[Thiago Macieira]

On Thursday, 28 de October de 2010 05:44:09 Bradley Smith wrote:
> You need to be presenting a darn good reason why bugs are not being
> shown to everyone.

Usually that reason is "security issue" or "customer sensitive information".

But like you said, there should be a way to request access for people who need 
to know.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
  PGP/GPG: 0x6EF45358; fingerprint:
  E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358


signature.asc
Description: This is a digitally signed message part.
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Meego Bugs Access Denied

[Bradley Smith]

I don't want to be rude here, but I feel that I need to interject. (So
no rudeness or just shooting messengers intended)

On Thu, Oct 28, 2010 at 8:31 PM,   wrote:
> We are working on making these defects visible again as soon as possible.
> There's a chance that the number still grows in the coming days yet the 
> situation should come back to normal quite soon.

No, just no. This is an open project. You cannot just say that you
will open them up (basically) when you feel like doing it and then
furthermore say that more bugs will happen like this - closed off from
the open.

You need to be presenting a darn good reason why bugs are not being
shown to everyone. This is not Nokia where things are closed first,
opened on a case-by-case basis. This is an open project, where things
should be open unless there are extreme circumstances and reasoning
that would allow that bug to be closed (eg. major security bug).

Even if there are closed off bugs, there should be a process in order
to be able to view these bugs. People are trying to do the best job
they can within the MeeGo project, without them getting access to
these bugs, they will get blamed for it being missed out on - but they
can't even view it! It is hindering their progress.

Now you mention that more unexplained closed off bugs will come. Unacceptable.

Seriously, sometimes I need to slap myself across the face a couple of
times to remember whether this is an open project or a marketing
scheme with Nokia and Intel puppeteers. But then I remember it is an
open project, with a lot of people acting in the manner they should
but it seems like not everyone has crossed the bridge yet to realizing
and remembering to participate in the open.

> BR,
> Eric

Cheers,
Bradley Smith
IRC: Termana
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] new category names in mcontrolpanel

[Juhasz Gabor]

Hi,

Sorry, something was wrong in my previous mail.

Br,
Gabor Juhasz, Maintainer of mcontrolpanel

--


Hi,

due to ui changes, the categories in controlpanel are about to change
drastically in the next 0.9.0 version. We are planning to release this
version in a few days to staging. After it appeared, applet developers
will need to change the category where their applet belongs to in the
.desktop file of the applet the usual way:

[DCP]
Category=qtn_sett_main_personalize

As usual, applets which specify itself being in an unknown category (in
the old categories) will appear in the Applications category.

Applet developers are encouraged to use the id of the category,
allthough the category name is also working. You can find the new
category ids, names, and brief descriptions in the attached .txt

Best regards,

Manner Robert
from duicontrolpanel



Category ID Category name Category description

qtn_sett_main_connections Connections  (Internet, Bluetooth, 
Network)
qtn_sett_main_phone   Phone(Call, SIM card)
qtn_sett_main_applicationsApplications (Installations, Application 
settings)
qtn_sett_main_notifications   Notifications(Home screen feed, Alerts)
qtn_sett_main_personalize Personalize  (Wallpaper, Theme, Sounds)
qtn_sett_main_battery Battery  (Display, battery)
qtn_sett_main_securitySecurity (Lock code, Passwords & 
Certificates)
qtn_sett_main_timedateTime & Date  (Time, Date, Region)
qtn_sett_main_languageLanguage & Keyboard  (Language, Text input)
qtn_sett_main_accessories Accessories  (USB, TV-out, Tele coil)
qtn_sett_main_backup  Sync & Backup(Device synchronization, 
Backup)
qtn_sett_main_about   About my N9  (Warranty, About product)


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] [Fwd: [Harmattan-changes] new category names in mcontrolpanel]

[Juhasz Gabor]

Hi,

There will be some changes in mcontrolpanel soon.
Please, read bellow.

Br,
Gabor Juhasz, Maintainer of mcontrolpanel

--- Begin Message ---
MIME-Version: 1.0
Received: from owa.nokia.com [65.54.30.197]
by T61 with IMAP (fetchmail-6.3.9-rc2)
for  (single-drop); Tue, 26 Oct 2010 12:39:26 +0300 
(EEST)
Received: from vaebh102.NOE.Nokia.com (10.160.244.23) by
 NOK-AM1MHUB-03.mgdnok.nokia.com (65.54.30.7) with Microsoft SMTP Server id
 8.2.254.0; Tue, 26 Oct 2010 11:37:39 +0200
Received: from vaebh105.NOE.Nokia.com ([10.160.244.31]) by
 vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.4675);   Tue, 26 Oct
 2010 12:37:33 +0300
Received: from mx-sa02.nokia.com ([147.243.177.58]) by vaebh105.NOE.Nokia.com
 over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 
26 Oct
 2010 12:37:33 +0300
Received: from projects.maemo.org (projects.maemo.org [62.61.85.36])by
 mx-sa02.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id o9Q9bTHN016501
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); 
Tue, 26
 Oct 2010 12:37:30 +0300
Received: from eevee.dmz (localhost [127.0.0.1])by projects.maemo.org
 (Postfix) with ESMTP id 09A50264ED6;   Tue, 26 Oct 2010 12:37:29 +0300 (EEST)
Received: from mail.blumsoft.eu (unknown [195.70.35.16])(using TLSv1 
with
 cipher ADH-AES256-SHA (256/256 bits))  (No client certificate requested)   
by
 projects.maemo.org (Postfix) with ESMTP id 2EEA6264ED6 for
 ;Tue, 26 Oct 2010 12:37:28 +0300
 (EEST)
Received: from mail.blumsoft.eu (localhost [127.0.0.1]) by mail.blumsoft.eu
 (Postfix) with ESMTP id CEE482485D for
 ;Tue, 26 Oct 2010 11:37:26 +0200
 (CEST)
Received: from [192.168.2.12] (unknown [192.168.2.12])  (using TLSv1 with
 cipher AES256-SHA (256/256 bits))  (Client CN "mail.blumsoft.eu", Issuer
 "mail.blumsoft.eu" (verified OK))  by mail.blumsoft.eu (Postfix) with 
ESMTPSA
 id B585E247F3  for ; Tue, 26 Oct 2010
 11:37:26 +0200 (CEST)
From: ext Manner Robert 
To: "harmattan-chan...@projects.maemo.org"

Sender: "harmattan-changes-boun...@projects.maemo.org"

Date: Tue, 26 Oct 2010 11:37:50 +0200
Subject: [Harmattan-changes] new category names in duicontrolpanel
Thread-Topic: [Harmattan-changes] new category names in duicontrolpanel
Thread-Index: Act08XhfUeE+wFxoQgKFfS/NFhDwAg==
Message-ID: <4cc6a16e.9070...@blumsoft.eu>
List-Help: 
List-Subscribe:
 ,

List-Unsubscribe:
 ,


Accept-Language: en-US
Content-Language: en-US
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Organization-AuthSource: nok-am1mhub-03.mgdnok.nokia.com
X-MS-Has-Attach: yes
X-Auto-Response-Suppress: All
X-MS-Exchange-Organization-SCL: 0
X-MS-TNEF-Correlator:
x-nokia-av: Clean
x-pstn-spam: N
x-spam-score: 0.00%
x-originalarrivaltime: 26 Oct 2010 09:37:33.0153 (UTC)
 FILETIME=[6A6B0510:01CB74F1]
user-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;   rv:1.9.1.12)
 Gecko/20100917 Lightning/1.0b1 Icedove/3.0.8
x-virus-scanned: ClamAV using ClamSMTP
x-beenthere: harmattan-chan...@projects.maemo.org
x-mailman-version: 2.1.9
list-id: Harmattan change announcements
 
errors-to: harmattan-changes-boun...@projects.maemo.org
x-original-to: harmattan-chan...@projects.maemo.org
delivered-to: harmattan-chan...@projects.maemo.org
x-enigmail-version: 1.0.1
list-archive: 
list-post: 
x-dkim: Sendmail DKIM Filter v2.8.4 mx-sa02.nokia.com o9Q9bTHN016501
openpgp: id=61BECC2D
Content-Type: multipart/mixed; boundary="_004_4CC6A16E9070309blumsofteu_"

--_004_4CC6A16E9070309blumsofteu_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

due to ui changes, the categories in controlpanel are about to change
drastically in the next 0.9.0 version. We are planning to release this
version in a few days to staging. After it appeared, applet developers
will need to change the category where their applet belongs to in the
.desktop file of the applet the usual way:

[DCP]
Category=3Dqtn_sett_main_personalize

As usual, applets which specify itself being in an unknown category (in
the old categories) will appear in the Applications category.

Applet developers are encouraged to use the id of the category,
allthough the category name is also working. You can find the new
category ids, names, and brief descriptions in the attached .txt

Best regards,

Manner Robert
from duicontrolpanel

--_004_4CC6A16E9070309blumsofteu_
Content-Type: text/plain; name="categoryNames.txt"
Content-Description: category

Re: [MeeGo-dev] OBS, MeeGo and the social desktop : Application information, feedback and rating

[David Greaves]

On 28/10/10 11:46, Ville M. Vainio wrote:

On Thu, Oct 28, 2010 at 1:41 PM, David Greaves  wrote:


As I say, the use-case is something around providing feedback from the
application launcher on the device; maybe an on-device popup that allows a
star rating, comment etc that is linked back to the appropriate OBS package
and team.


It seems like it combines two separate things:

- Application
- How/where it gets built

Not quite.
It requires that the installation of an application provides an optional 
OCS-compliant url for feedback.



I'd rather see an entity separate from OBS as the starting point of a
rating/comment system.
Why? I'm talking about making the OBS support a standard API, not the other way 
around. This idea would allow the OBS to be replaced as "keeper of ratings" but 
in the meantime may also allow us some efficiency in reducing the number of 
systems we have to develop and support.


The OBS already provides:
* PPA -like repos
* Extras-devel -like projects
* Extras -like projects
* per-package file storage (think screenshots)
* ratings system
* integration with MeeGo user account system

It doesn't provide a comment system.


Applications built with any system would reside
there (including proprietary applications built in someones basement).
This doesn't preclude that at all; provided the basement builder provides an OCS 
API somewhere.


MeeGo community does provide a community build system.. the OBS ... which, as 
you say, needs to support rating/feedback somehow. The OBS has a rating 
system... no-brainer (well, at least as a potential solution).


David

--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] OBS, MeeGo and the social desktop : Application information, feedback and rating

[Ville M. Vainio]

On Thu, Oct 28, 2010 at 1:41 PM, David Greaves  wrote:

> As I say, the use-case is something around providing feedback from the
> application launcher on the device; maybe an on-device popup that allows a
> star rating, comment etc that is linked back to the appropriate OBS package
> and team.

It seems like it combines two separate things:

- Application
- How/where it gets built

I'd rather see an entity separate from OBS as the starting point of a
rating/comment system. Applications built with any system would reside
there (including proprietary applications built in someones basement).

-- 
Ville M. Vainio @@ Forum Nokia
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] OBS, MeeGo and the social desktop : Application information, feedback and rating

[David Greaves]

This is more of an initial exploration than a concrete proposal :)

I'll post this to both the opensuse-buildserv...@opensuse.org and 
meego-dev@meego.com lists.


MeeGo is going to be using the Open Collaboration Services (OCS) API.
  http://www.socialdesktop.org/ocs/
  http://www.freedesktop.org/wiki/Specifications/open-collaboration-services

One of the features of this is to provide feedback and ratings from the 
device/desktop to the application development team.


MeeGo's community OBS will be used for developers to manage their applications 
and I was interested in the concept of using the OBS API to support this. The 
api already provides some rating services so it seems to fit in somewhere.


  https://api.obs.maemo.org/apidocs/#107

As I say, the use-case is something around providing feedback from the 
application launcher on the device; maybe an on-device popup that allows a star 
rating, comment etc that is linked back to the appropriate OBS package and team.


So does this fit with the intended usage around the 'rating' type services 
already in the OBS?


David

--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Meego Bugs Access Denied

[eric.le-roux]

Hi Gary,

We are working on making these defects visible again as soon as possible.
There's a chance that the number still grows in the coming days yet the 
situation should come back to normal quite soon.
Sorry for the inconvenience!

BR,
Eric



>-Original Message-
>From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com]
>On Behalf Of ext Gary Birkett
>Sent: 28 October, 2010 12:29
>To: Development for the MeeGo Project
>Subject: [MeeGo-dev] Meego Bugs Access Denied
>
>Hey,
>
>I have encountered a number of bugs this morning as part of my work on
>the meego bug tracker which are giving an error:
>"You are not authorized to access bug #[bugid]"
>(related to something I expected to read and digest)
>
>This issue effects people in other areas too
>
>A specific example this morning was stskeeps could not access
>http://bugs.meego.com/show_bug.cgi?id=8474
>
>this bug is highlighted multiple times in the acceptance report
>http://wiki.meego.com/Quality/HandsetTestReport/1.2_N900Acceptance201010
>28
>
>Is there a general documented mechanism to follow to get access to
>these bugs or to generally unlock them?
>(going through team leaders based on requirements is normal)
>
>Gary
>___
>MeeGo-dev mailing list
>MeeGo-dev@meego.com
>http://lists.meego.com/listinfo/meego-dev
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] Meego Bugs Access Denied

[Gary Birkett]

Hey,

I have encountered a number of bugs this morning as part of my work on
the meego bug tracker which are giving an error:
"You are not authorized to access bug #[bugid]"
(related to something I expected to read and digest)

This issue effects people in other areas too

A specific example this morning was stskeeps could not access
http://bugs.meego.com/show_bug.cgi?id=8474

this bug is highlighted multiple times in the acceptance report
http://wiki.meego.com/Quality/HandsetTestReport/1.2_N900Acceptance20101028

Is there a general documented mechanism to follow to get access to
these bugs or to generally unlock them?
(going through team leaders based on requirements is normal)

Gary
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] How does the mutter-moblin support auto fitting resolution changing?

[danny]

Hi all,

I found that the Meego Netbook UX could auto resize to fit the resolution 
changing, how does it implement?  in the sources of mutter-moblin? which part I 
could try to find?

Any  information to me?  Thanks in advanced.



--

 Best Regards,

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] libglx.so for virtualbox

[Leonko]

Please anybody add this to wiki page

Leonid S. Batizhevsky



On Thu, Oct 28, 2010 at 13:09, Feng, Haitao  wrote:
> Hi CSJ,
>
> You need to modify and build the Xorg code to get libglx.so.
>
> The modification is in:
>    xserver/glx/glxdriswrast.c:__glXDRIscreenProbe,
> change from
>    screen->base.GLXmajor = 1;
>    screen->base.GLXminor = 4;
> to
>    screen->base.GLXmajor = 1;
>    screen->base.GLXminor = 2;
>
> This is only for MeeGo 05-24 image. Currently the issue has been fixed and
> clutter could be started up by software rendering, so for latest MeeGo netbook
> image, you do not need this step any more. However, you still need to set the
> suid for guest Xorg.
>
> Thanks
> -Haitao
>
> On Thu, Oct 28, 2010 at 02:08:46PM +0800, CSJ wrote:
>> Hi, all
>>
>> In Meego wiki:
>> http://wiki.meego.com/MeeGo_1.0_Netbook_VirtualBox
>>
>> mentioned Download Libglx.so.gz
>>   Replace libglx.so for an X issue, this libglx.so will put glx version to 
>> 1.2,
>> instead of 1.4.
>>
>> is there any source code of this libglx.so?
>> Or say, where does this libglx.so com from?
>>
>> Thanks,
>> CSJ
>>
>
>> ___
>> MeeGo-dev mailing list
>> MeeGo-dev@meego.com
>> http://lists.meego.com/listinfo/meego-dev
>
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev
>
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] libglx.so for virtualbox

[Feng, Haitao]

Hi CSJ,

You need to modify and build the Xorg code to get libglx.so.

The modification is in:
xserver/glx/glxdriswrast.c:__glXDRIscreenProbe,
change from 
screen->base.GLXmajor = 1;
screen->base.GLXminor = 4;
to 
screen->base.GLXmajor = 1;
screen->base.GLXminor = 2;

This is only for MeeGo 05-24 image. Currently the issue has been fixed and
clutter could be started up by software rendering, so for latest MeeGo netbook
image, you do not need this step any more. However, you still need to set the
suid for guest Xorg.

Thanks
-Haitao 

On Thu, Oct 28, 2010 at 02:08:46PM +0800, CSJ wrote:
> Hi, all
> 
> In Meego wiki:
> http://wiki.meego.com/MeeGo_1.0_Netbook_VirtualBox
> 
> mentioned Download Libglx.so.gz
>   Replace libglx.so for an X issue, this libglx.so will put glx version to 
> 1.2,
> instead of 1.4.
> 
> is there any source code of this libglx.so?
> Or say, where does this libglx.so com from?
> 
> Thanks,
> CSJ
> 

> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] Captive portals detection

[punit bisht]

Hi,

Does anyone know how to detect a guest network as a captive portal.
I mean can i detect a network as a CAPTIVE PORTAL through connman
interfaces? So that i can fire a browser for html login authentication.
I found a link
http://bugs.meego.com/show_bug.cgi?id=1578#c0

but i need more detailed information on it.

Thanks in Advance
Puneet Bisht
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Does Meego well support internationalization/localization?

[Aleksander Morgado]

> >In Tracker we will be using ICU directly to support Chinese Pinyin
> >collations. We'll be getting /meegotouch/i18n/lc_collate from gconf and
> >pass it directly to libicu. This work is already on-going and will be
> >available in the next 2-3 weeks (currently we're assuming en_US.utf8
> >locale always in collation).
> 
> Thanks for update. 
> For some app, locale is temporary changed, not saved to gconf. 
> 
> Does tracker have interface to query with a given collation from input? 
> 

Not right now. There's a branch which implements a "COLLATE" keyword in
SPARQL, but wasn't merged because we didn't find it useful at that time,
we preferred to have a single collation implicitly stated in the text
columns inside the database, as that would give us the proper orders
already in the indexes of the indexed properties. Anyway, if there are
real use cases of temporary locales applied in applications, or just
different locale needs for different collations, we may end up doing it.

> 
> >Tracker's FTS, if enabled in meego (which I'm not really sure 
> >if it is),
> >should already support it. We currently use libicu word-breaking
> >algorithm to properly separate words during FTS parsing.
> 
> FTS is enabled in MeeGo Tracker. But it uses glib as the default parser.
> I will submit a patch to enable libicu as default. 
> 

Oh please, yes, enable libicu.

> BTW: For the input of tracker-search-tool, its length (g_utf8_strlen) must >= 
> 3.
> But the length of lots lots of Chinese words is 2. 
> 
> Can we make it configurable for different languages?  
> 

It actually should be configurable in the tracker-fts.cfg configuration
file, isn't it?
[Indexing]
# Set the minimum length of words to index (0->30, default=3)
MinWordLength=3

Oh, maybe you mean directly in the t-s-t text input? I'd suggest you
drop an email to tracker mailing list about this or fill a bug in
bugzilla. We're currently replacing t-s-t with a new tool called
"needle", still not in the master branch.

-- 
Aleksander

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev