Hi,
I wanted to know what is the difference between 1.1(not released yet) and
1.1.80 release.
Is 1.1.80 an extension to 1.1 ?.
Since I am looking forward to 1.1 release for time being can I use 1.1.80
Regards,
PP
___
MeeGo-dev mailing list
2010/10/21 praveen pandey praveen.pan...@gmail.com:
Hi,
I wanted to know what is the difference between 1.1(not released yet) and
1.1.80 release.
Is 1.1.80 an extension to 1.1 ?.
Since I am looking forward to 1.1 release for time being can I use 1.1.80
You'll want to take a look at
My comment was relevant to the graphics driver. I have no idea if there is a
dependency for the evdev driver
-Original Message-
From: Tomasz Sterna [mailto:to...@xiaoka.com]
Sent: Wednesday, October 20, 2010 9:03 PM
To: Clark, Joel
Cc: Aloisio Almeida; meego-dev@meego.com
Subject: RE:
Hello,
I wrote this in a non-list email earlier today and realised it might be
useful for a wider audience:
I've been working on the Netbook UX parts related to power management
and have realized that we have a QA communication problem in areas that
do not conform to the bugzilla product
Hi,
We are trying to debug a problem using 'gdb' on the device, but it is currently
not letting us see the state of the various threads ( get the following
message: warning: unable to find libthread_db matching inferior's thread
library, thread debugging will not be available).
Do you happen
Dear mcompositor developers,
Yongsheng and I have a question on mcompositor, why does the compositing
functionality depend on the type of the topmost window?
The function MCompositeManagerPrivate::possiblyUnredirectTopmostWindow() will
judge whether the topmost root window isAppWindow(true), if
It's a typical example - when a bug does not seem to have a clear component to
assign, it is easily neglected at the corner. Are we kind of lacking bug triage
efforts on the ambiguous bugs?
- Bingwei
-Original Message-
From: meego-dev-boun...@meego.com
Hi,
I just got this message:
---
Welcome! It looks like you are sending this message from an
unsubscribed email address. All of the MeeGo lists require that you
must be a subscriber in order to send email to our lists.
Please subscribe to the list or make sure that you are sending from a
Sorry people on meego-qa, You did not get the original mail because it
was automatically discarded. I hope you don't get utterly confused with
the different posting styles -- this conversation seems to be a good
example of why top-posting is bad. You will find the original post at
the bottom.
Hi,
Felipe Contreras wrote:
One way to achieve this is to only require a subscription to _one_
list, in order to allow sending messages to all of them. I have never
seen anybody doing this though.
GNOME has a post-only email list, which anyone can subscribe to. If
they're subscribed to that
Hello Haitao!
You might have a better chance getting an answer to the email below on
the MTF mailing list. On CC and Reply-To set.
On Do, 2010-10-21 at 11:29 +0100, Feng, Haitao wrote:
Dear mcompositor developers,
Yongsheng and I have a question on mcompositor, why does the compositing
Hi,
On Thursday 21 October 2010 01:29:08 pm ext Feng, Haitao wrote:
Yongsheng and I have a question on mcompositor, why does the compositing
functionality depend on the type of the topmost window?
The function MCompositeManagerPrivate::possiblyUnredirectTopmostWindow()
will judge whether
Comparing the below two alternative coding logics:
1. If it is AppWindow, draw the AppWindow's texture
on compositor's GL
window. This means mcompositor's GL window will be
always mapped.
2. If it is not AppWindow, combine it with decorator
directly and do not touch
texture
Am Donnerstag, den 21.10.2010, 14:10 +0300 schrieb Jussi Kukkonen:
Question: Is there a bugzilla best practice that makes sure
developers-interested-in-power-management get email notifications
of bugs that reporters or QA think might be related to power
management, regardless of their
On Thursday 21 October 2010 04:30:25 pm ext Zhu, Yongsheng wrote:
Comparing the below two alternative coding logics:
1. If it is AppWindow, draw the AppWindow's texture
on compositor's GL
window. This means mcompositor's GL window will be
always mapped.
2. If it is
On 10/20/10 23:35, Clark, Joel wrote:
My comment was relevant to the graphics driver. I have no idea if there is a
dependency for the evdev driver
I couldn't find in the original thread what graphics hardware this is
for, but in general, non-suid root X only works when kernel-modesetting
On 10/21/10 03:24, Stylianou, Costas wrote:
Hi,
We are trying to debug a problem using ‘gdb’ on the device, but it is currently not
letting us see the state of the various threads ( get the following message:
warning: unable to find libthread_db matching inferior's thread library, thread
On 10/21/10 10:16, Tomasz Sterna wrote:
Dnia 2010-10-21, czw o godzinie 10:03 -0700, Auke Kok pisze:
On 10/20/10 23:35, Clark, Joel wrote:
My comment was relevant to the graphics driver. I have no idea if there is a
dependency for the evdev driver
I couldn't find in the original thread
Dnia 2010-10-21, czw o godzinie 10:34 -0700, Auke Kok pisze:
: At the end of my .log I noticed the following lines:
: [ 465.418] config/udev: failed to bind the udev monitor
: [ 465.456] [config] failed to initialise udev
sounds like dbus failed on you at startup
udev process is there.
Dnia 2010-10-21, czw o godzinie 10:34 -0700, Auke Kok pisze:
which MeeGo image is this?
It's MeeGo_current build.
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
On 10/21/10 11:00, Tomasz Sterna wrote:
Dnia 2010-10-21, czw o godzinie 10:34 -0700, Auke Kok pisze:
which MeeGo image is this?
It's MeeGo_current build.
that does not compute. can you e.g. give me the release number, or the
download URL where this image comes from?
Auke
2010/10/21 Auke Kok auke-jan.h@intel.com:
On 10/21/10 11:00, Tomasz Sterna wrote:
Dnia 2010-10-21, czw o godzinie 10:34 -0700, Auke Kok pisze:
which MeeGo image is this?
It's MeeGo_current build.
that does not compute. can you e.g. give me the release number, or the
download URL
Dnia 2010-10-21, czw o godzinie 11:05 -0700, Auke Kok pisze:
which MeeGo image is this?
It's MeeGo_current build.
that does not compute. can you e.g. give me the release number, or
the
download URL where this image comes from?
I am building my own MeeGo Core images using
Dnia 2010-10-16, sob o godzinie 12:35 +0200, Tomasz Sterna pisze:
[r...@localhost ~]# su meego -c 'udevadm monitor'
monitor will print the received events for:
bind failed: Operation not permitted
error: unable to subscribe to udev events
I just tested on my Ubuntu workstation and I can run
On 10/21/10 11:35, Tomasz Sterna wrote:
Dnia 2010-10-16, sob o godzinie 12:35 +0200, Tomasz Sterna pisze:
[r...@localhost ~]# su meego -c 'udevadm monitor'
monitor will print the received events for:
bind failed: Operation not permitted
error: unable to subscribe to udev events
I just tested
Hi Abdiel,
Thank you very much for your reply!
I get the mcompositor source code by zypper si meegotouch-compositor after
extracting the MeeGo 10-15 handset image and chrooting into it. The version is
0.5.8 and the mcompositemanager.cpp is attached. This is the code base I will be
working for. I
On 10/21/2010 8:27 PM, Zhao, Halley wrote:
When HDMI is connected, the information can be queried from xrandr;
But instead of query, is there notification on MeeGo to detect HDMI
connection?
Does contextkit provide such information?
I think the question is slightly different
it's not
When HDMI is connected, the information can be queried from xrandr;
But instead of query, is there notification on MeeGo to detect HDMI connection?
Does contextkit provide such information?
I think there are some similar information like: Bluetooth earphone connected,
USB disk connected, etc.
App needs this information in case of some visual design.
Do you think contextkit is the right place to do it?
-Original Message-
From: Arjan van de Ven [mailto:ar...@linux.intel.com]
Sent: Friday, October 22, 2010 11:39 AM
To: Zhao, Halley
Cc: meego-dev@meego.com;
29 matches
Mail list logo
