Re: Hildon 2.0 Release
We are very close to v2.0 already and I don't think the merge will be too bad. I haven't seen any new features that would be too significant, and moving to 2.0 would be a good idea. Bill On Jan 17, 2008, at 1:22 PM, Spencer, Bob wrote: > We are already at a version very close to v2.0 I'm not sure if the > magic isn't already there. Or do you know that they added significant > features very late? I mean we updated just 6 weeks ago. > > Bob > > Adilson Oliveira wrote: >> Spencer, Bob escreveu: >>> Perhaps we should review the differences and see how invasive they >>> are and if we should move to this latest release. >> >> If I want to make the alarm clock work the way we were discussing >> yesterday, yes. >> >> []s >> >> Adilson. > > > -- > Ubuntu-mobile mailing list > Ubuntu-mobile@lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/ > listinfo/ubuntu-mobile -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
RE: Patch for Moblin Image Creator -- add / entry in fstab
Michael, Thanks for the patch. Initial test shows although the system's real root is unionfs containing ro squashfs plus rw ext3 /dev/sda2, adding the line does no harm to system. System shows a /dev/sda2 mount to /, but according to /proc/mounts, there is no such mount. It seems an ideal workaround. JohnV, Rob, Any thoughts regarding to the patch? Thanks, Alek -Original Message- From: Michael Frey [mailto:[EMAIL PROTECTED] Sent: 2008年1月18日 5:57 To: Du, Alek Cc: Rhoads, Rob; Villalovos, John L; Karur Mohan, Prajwal; ubuntu-mobile@lists.ubuntu.com Subject: Patch for Moblin Image Creator -- add / entry in fstab Alek, Attached is a patch to Moblin Image Creator that adds an entry to fstab for the / ext3 partition. This fixes a bug where GnomeVFS will not work properly without such an entry. Thanks, Michael -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
RE: Fix for -psb X issue
I will forward to TG for this issue. Thanks! Calvin -Original Message- From: Bryce Harrington [mailto:[EMAIL PROTECTED] Sent: Thursday, January 17, 2008 1:34 PM To: Bastian, Waldo Cc: Amit Kucheria; ubuntu-mobile@lists.ubuntu.com; Zhao, Chunfeng Subject: Re: Fix for -psb X issue See amit's comment: http://bryceharrington.org/drupal/node/31 On Thu, Jan 17, 2008 at 01:29:06PM -0800, Bastian, Waldo wrote: > Can you see where (e.g. with a calltrace) the first lock happens and > where the second lock happens? > > Cheers, > Waldo > > Intel Corporation - Platform Software Engineering, UMG - Hillsboro, > Oregon > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Bryce > Harrington > Sent: Thursday, January 17, 2008 12:53 PM > To: Amit Kucheria > Cc: ubuntu-mobile@lists.ubuntu.com > Subject: Fix for -psb X issue > > I've uploaded a fix for the -psb X issue to PPA. [1] > > Yesterday, Amit and I found that a psbDRILock() routine was being called > twice; this routine requests a lock in the kernel, which works the first > time, but not the second. > > So this morning, I disabled the second lock/unlock in -psb[2], and sure > enough, X came up and seems to be working as expected now[3]. > > Bryce > > 1: https://launchpad.net/~ubuntu-mobile/+archive > 2: http://people.ubuntu.com/~bryce/UME/103_psb_debugs.patch > 3: http://bryceharrington.org/drupal/ume-psb-fix > > -- > Ubuntu-mobile mailing list > Ubuntu-mobile@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
RE: Fix for -psb X issue
According feedback from TG, it is not a bug for xserver 1.3, it might be compatibility issue for 1.4, currently they are not supporting 1.4 and they are not going to integrate patch into their source code. Calvin -Original Message- From: Bryce Harrington [mailto:[EMAIL PROTECTED] Sent: Thursday, January 17, 2008 1:34 PM To: Bastian, Waldo Cc: Amit Kucheria; ubuntu-mobile@lists.ubuntu.com; Zhao, Chunfeng Subject: Re: Fix for -psb X issue See amit's comment: http://bryceharrington.org/drupal/node/31 On Thu, Jan 17, 2008 at 01:29:06PM -0800, Bastian, Waldo wrote: > Can you see where (e.g. with a calltrace) the first lock happens and > where the second lock happens? > > Cheers, > Waldo > > Intel Corporation - Platform Software Engineering, UMG - Hillsboro, > Oregon > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Bryce > Harrington > Sent: Thursday, January 17, 2008 12:53 PM > To: Amit Kucheria > Cc: ubuntu-mobile@lists.ubuntu.com > Subject: Fix for -psb X issue > > I've uploaded a fix for the -psb X issue to PPA. [1] > > Yesterday, Amit and I found that a psbDRILock() routine was being called > twice; this routine requests a lock in the kernel, which works the first > time, but not the second. > > So this morning, I disabled the second lock/unlock in -psb[2], and sure > enough, X came up and seems to be working as expected now[3]. > > Bryce > > 1: https://launchpad.net/~ubuntu-mobile/+archive > 2: http://people.ubuntu.com/~bryce/UME/103_psb_debugs.patch > 3: http://bryceharrington.org/drupal/ume-psb-fix > > -- > Ubuntu-mobile mailing list > Ubuntu-mobile@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: Fix for -psb X issue
Odd, I would have thought that since they have added requirements for xserver 1.4 features (EXA 2.2), that the code would have been tested against and supported on xserver 1.4 as well. But thanks, this seems to explain the origin of the problem. Bryce On Thu, Jan 17, 2008 at 03:13:20PM -0800, Zhao, Chunfeng wrote: > According feedback from TG, it is not a bug for xserver 1.3, it might be > compatibility issue for 1.4, currently they are not supporting 1.4 and > they are not going to integrate patch into their source code. > > Calvin > > -Original Message- > From: Bryce Harrington [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 17, 2008 1:34 PM > To: Bastian, Waldo > Cc: Amit Kucheria; ubuntu-mobile@lists.ubuntu.com; Zhao, Chunfeng > Subject: Re: Fix for -psb X issue > > See amit's comment: http://bryceharrington.org/drupal/node/31 > > On Thu, Jan 17, 2008 at 01:29:06PM -0800, Bastian, Waldo wrote: > > Can you see where (e.g. with a calltrace) the first lock happens and > > where the second lock happens? > > > > Cheers, > > Waldo > > > > Intel Corporation - Platform Software Engineering, UMG - Hillsboro, > > Oregon > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Bryce > > Harrington > > Sent: Thursday, January 17, 2008 12:53 PM > > To: Amit Kucheria > > Cc: ubuntu-mobile@lists.ubuntu.com > > Subject: Fix for -psb X issue > > > > I've uploaded a fix for the -psb X issue to PPA. [1] > > > > Yesterday, Amit and I found that a psbDRILock() routine was being > called > > twice; this routine requests a lock in the kernel, which works the > first > > time, but not the second. > > > > So this morning, I disabled the second lock/unlock in -psb[2], and > sure > > enough, X came up and seems to be working as expected now[3]. > > > > Bryce > > > > 1: https://launchpad.net/~ubuntu-mobile/+archive > > 2: http://people.ubuntu.com/~bryce/UME/103_psb_debugs.patch > > 3: http://bryceharrington.org/drupal/ume-psb-fix > > > > -- > > Ubuntu-mobile mailing list > > Ubuntu-mobile@lists.ubuntu.com > > Modify settings or unsubscribe at: > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Patch for Moblin Image Creator -- add / entry in fstab
Alek, Attached is a patch to Moblin Image Creator that adds an entry to fstab for the / ext3 partition. This fixes a bug where GnomeVFS will not work properly without such an entry. Thanks, Michael diff --git a/libs/InstallImage.py b/libs/InstallImage.py index 8be7649..b8f044e 100755 --- a/libs/InstallImage.py +++ b/libs/InstallImage.py @@ -198,6 +198,7 @@ class InstallImage(object): def create_fstab(self, swap = True): fstab_file = open(os.path.join(self.target.fs_path, 'etc/fstab'), 'w') +print >> fstab_file, "/dev/sda2 / ext3defaults,noatime0 0" print >> fstab_file, "proc /proc proc defaults 0 0" if swap: print >> fstab_file, "/dev/sda3 none swap sw 0 0" -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
RE: how to run as ume user in Xephyr?
I requested this change some time ago, and I think the reason that John was against it was that the ume user is not guaranteed to exist when Image Creator is used for other versions of Linux. This could be an option--the user could select the default user for a particular project or target. Aaron >-Original Message- >From: [EMAIL PROTECTED] [mailto:ubuntu-mobile- >[EMAIL PROTECTED] On Behalf Of Villalovos, John L >Sent: Thursday, January 17, 2008 1:30 PM >To: Spencer, Bob; Kyle Nitzsche; Loïc Minier >Cc: ubuntu-mobile@lists.ubuntu.com; Karur Mohan, Prajwal >Subject: RE: how to run as ume user in Xephyr? > >Spencer, Bob wrote: >> Do you think defaulting to user "ume" is OK? It has an >> advantage for me in that I can setup my home environment >> including adding media content and it will be the same on the >> Q1. I think we talked about this once and decided against it, but I >> can't remember why. Bob > >I don't see a problem with it. Not sure if anybody else has an option. > >If you want to commit a fix or send me a patch, then we can do it. > >John > >-- >Ubuntu-mobile mailing list >Ubuntu-mobile@lists.ubuntu.com >Modify settings or unsubscribe at: >https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: Fix for -psb X issue
See amit's comment: http://bryceharrington.org/drupal/node/31 On Thu, Jan 17, 2008 at 01:29:06PM -0800, Bastian, Waldo wrote: > Can you see where (e.g. with a calltrace) the first lock happens and > where the second lock happens? > > Cheers, > Waldo > > Intel Corporation - Platform Software Engineering, UMG - Hillsboro, > Oregon > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Bryce > Harrington > Sent: Thursday, January 17, 2008 12:53 PM > To: Amit Kucheria > Cc: ubuntu-mobile@lists.ubuntu.com > Subject: Fix for -psb X issue > > I've uploaded a fix for the -psb X issue to PPA. [1] > > Yesterday, Amit and I found that a psbDRILock() routine was being called > twice; this routine requests a lock in the kernel, which works the first > time, but not the second. > > So this morning, I disabled the second lock/unlock in -psb[2], and sure > enough, X came up and seems to be working as expected now[3]. > > Bryce > > 1: https://launchpad.net/~ubuntu-mobile/+archive > 2: http://people.ubuntu.com/~bryce/UME/103_psb_debugs.patch > 3: http://bryceharrington.org/drupal/ume-psb-fix > > -- > Ubuntu-mobile mailing list > Ubuntu-mobile@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
RE: how to run as ume user in Xephyr?
Spencer, Bob wrote: > Do you think defaulting to user "ume" is OK? It has an > advantage for me in that I can setup my home environment > including adding media content and it will be the same on the > Q1. I think we talked about this once and decided against it, but I > can't remember why. Bob I don't see a problem with it. Not sure if anybody else has an option. If you want to commit a fix or send me a patch, then we can do it. John -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
RE: Fix for -psb X issue
Can you see where (e.g. with a calltrace) the first lock happens and where the second lock happens? Cheers, Waldo Intel Corporation - Platform Software Engineering, UMG - Hillsboro, Oregon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bryce Harrington Sent: Thursday, January 17, 2008 12:53 PM To: Amit Kucheria Cc: ubuntu-mobile@lists.ubuntu.com Subject: Fix for -psb X issue I've uploaded a fix for the -psb X issue to PPA. [1] Yesterday, Amit and I found that a psbDRILock() routine was being called twice; this routine requests a lock in the kernel, which works the first time, but not the second. So this morning, I disabled the second lock/unlock in -psb[2], and sure enough, X came up and seems to be working as expected now[3]. Bryce 1: https://launchpad.net/~ubuntu-mobile/+archive 2: http://people.ubuntu.com/~bryce/UME/103_psb_debugs.patch 3: http://bryceharrington.org/drupal/ume-psb-fix -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: New -psb package
On Thu, Jan 17, 2008 at 06:23:36PM +, Matt Zimmerman wrote: > On Wed, Jan 16, 2008 at 11:00:31AM -0500, Tony Espy wrote: > > The only way I know how to build 'lpia' packages is to use debuild > > within an image-creator project chroot. > > > > This requires you to either build a menlow image from scratch and use > > it's project chroot, or import a saved project into image-creator and > > use it's chroot. > > "debuild -alpia" in an Ubuntu/i386 environment should work for simple > cases, exploiting the fact that i386 binaries will run on LPIA. Ahh, that sounds like a useful approach, I'll try that next time. The approach I ended up taking was to just install everything necessary to development on the menlow box itself, then logged into it and ran debuild there locally. Was time consuming to set up, but after it was working, hacking and testing the code went quite smoothly. I did notice that I could not specify deb-src locations in /etc/apt/sources.list, so couldn't just do apt-get build-dep xserver-xorg-video-psb but I was able to manually apt-get install all the required bits and pieces by hand. Bryce -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Fix for -psb X issue
I've uploaded a fix for the -psb X issue to PPA. [1] Yesterday, Amit and I found that a psbDRILock() routine was being called twice; this routine requests a lock in the kernel, which works the first time, but not the second. So this morning, I disabled the second lock/unlock in -psb[2], and sure enough, X came up and seems to be working as expected now[3]. Bryce 1: https://launchpad.net/~ubuntu-mobile/+archive 2: http://people.ubuntu.com/~bryce/UME/103_psb_debugs.patch 3: http://bryceharrington.org/drupal/ume-psb-fix -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: Midbrowser status update (1-10-08 -> 1-17-08)
On Thu, Jan 17, 2008 at 10:26:35AM -0800, Spencer, Bob wrote: > Alexander Sack wrote: > > We should switch to use system xulrunner-1.9 everywhere in mobile. > > Once the home screen (and midbrowser) use xulrunner-1.9, the > > important libs will already be loaded when starting midbrowser for > > the first time. > > - Alexander > > That sounds exciting. Startup has been a challenge since the beginnig. > While this will increase the MID first-time startup time, I wonder what > the hit will be on subsequent fast-boot startup times. > how is fast-boot startup done? is that hibernate? - Alexander -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
RE: Midbrowser status update (1-10-08 -> 1-17-08)
Alexander Sack wrote: > We should switch to use system xulrunner-1.9 everywhere in mobile. > Once the home screen (and midbrowser) use xulrunner-1.9, the > important libs will already be loaded when starting midbrowser for > the first time. > - Alexander That sounds exciting. Startup has been a challenge since the beginnig. While this will increase the MID first-time startup time, I wonder what the hit will be on subsequent fast-boot startup times. Bob -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
RE: how to run as ume user in Xephyr?
John, Do you think defaulting to user "ume" is OK? It has an advantage for me in that I can setup my home environment including adding media content and it will be the same on the Q1. I think we talked about this once and decided against it, but I can't remember why. Bob Kyle Nitzsche wrote: > Thanks for the info, Loic. > > If it were made more straightforward (maybe even the default), folks > would be more likely to run as ume user in Xephyr target, which might > help unearth bugs. > > Kyle > > > > On Jan 17, 2008, at 7:16 AM, Loïc Minier wrote: > >>Hi Kyle, >> >> On Wed, Jan 16, 2008, Kyle Nitzsche wrote: >>> Anyone know how to launch target in Xephyr as ume user, not root? >> >> This is something I do regularly, but which is very hackish. >> >> First, I have an ume user on my host; it has uid 1001. >> >> Second, the ume user is usually created by ume-config-common in the >> targets but with first available uid of 1000. I change this uid in >> /etc/passwd and /etc/group in the /targets//fs chroot. >> >> Third, I'm fixing the Xephyr startup to run as ume: >> - I install xserver-xephyr manually as root >> - I start dbus manually in the chroot as root and comment this out >> of the ume-xephyr-start script >> - I make sure that /tmp is bind mounted (image-creator does this >> automatically I think) as well as /home (for Xauthority) >> >> CAUTION: if you bind mount /home, make sure you unmount it before >> removing your target, or you could cause image-creator to rm -rf >> your home >> >> This works well for me, but should be made more easy. Also, this >> doesn't plug the current hole that Xephyr is run with -ac in the >> script, but that's not an issue on single user systems. >> >> -- >> Loïc Minier >> >> -- >> Ubuntu-mobile mailing list >> Ubuntu-mobile@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: New -psb package
On Wed, Jan 16, 2008 at 11:00:31AM -0500, Tony Espy wrote: > Bryce Harrington wrote: > > On Tue, Jan 15, 2008 at 09:08:54PM -0800, Bryce Harrington wrote: > >> In investigating the X issues I noticed things appear to be failing in > >> the memory manager. Looking closer at my -psb package, I noticed a > >> patch was not getting included, and consequently libmm was not being > >> properly built. Here's a package with this fixed (I think): > >> > >> http://people.ubuntu.com/~bryce/Testing/xserver-xorg-video-psb/ > >> > >> I also added a patch that adds more debugging code in the area where > >> things seem to be failing, to hopefully pinpoint where the failure > >> occurs. > >> > >> Bryce > > > > Btw, all the gory details of today's work... > > http://bryceharrington.org/drupal/node/31 > > > > I'm not sure how to build lpia packages, but the next step is to build > > a new lpia deb and test it against a recent img. > > Bryce -- > > The only way I know how to build 'lpia' packages is to use debuild > within an image-creator project chroot. > > This requires you to either build a menlow image from scratch and use > it's project chroot, or import a saved project into image-creator and > use it's chroot. "debuild -alpia" in an Ubuntu/i386 environment should work for simple cases, exploiting the fact that i386 binaries will run on LPIA. -- - mdz -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
RE: FW: Hildon 2.0 Release
We are already at a version very close to v2.0 I'm not sure if the magic isn't already there. Or do you know that they added significant features very late? I mean we updated just 6 weeks ago. Bob Adilson Oliveira wrote: > Spencer, Bob escreveu: >> Perhaps we should review the differences and see how invasive they >> are and if we should move to this latest release. > > If I want to make the alarm clock work the way we were discussing > yesterday, yes. > > []s > > Adilson. -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: Midbrowser status update (1-10-08 -> 1-17-08)
On Thu, Jan 17, 2008 at 07:36:01AM -0800, Wong, Carl wrote: > > * Team is busy working on moving from FF 3.0 beta 1 to beta 2 code base. the merge is finished and available on the WORKING branch [1]. Once we have fixed the icons we can go ahead and QA for other blockers and if nothing seriously pops up make midbrowser 0.3 the default imo. > > * Looking into why bookmark not working in FF3.0 based Midbrowser. fixed in WORKING as well > > * Got some good performance numbers from QA on FF3.0 base Midbrowser. > The average page rendering is close to 50% faster with the FF3.0 beta1 > based code. However the startup time appears to be slower. We should switch to use system xulrunner-1.9 everywhere in mobile. Once the home screen (and midbrowser) use xulrunner-1.9, the important libs will already be loaded when starting midbrowser for the first time. > > * We have got permission from the owner of the grabanddrag addon to use > in Midbrowser to provide finger scrolling. Isn't that code tri-licensed anyway? [1] - http://www.moblin.org/repos/?p=projects/mobile-browser.git;a=shortlog;h=WORKING - Alexander -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: FW: Hildon 2.0 Release
Spencer, Bob escreveu: > Perhaps we should review the differences and see how invasive they > are and if we should move to this latest release. If I want to make the alarm clock work the way we were discussing yesterday, yes. []s Adilson. -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Moblin Applets update
* BUGS FIXED * BUG: "Make default for this ..." checkbox on screen resolution dialog doesn't take effect BUGLINK: https://bugs.launchpad.net/moblin-applets/+bug/179795 FIX: That checkbox just affected where the settings were stored in the gconf tree. It was pretty much useless for MID so I completely removed it from the dialog. * BUG: "Cannot save resolution change after restart hildon-desktop or system" BUGLINK: https://bugs.launchpad.net/moblin-applets/+bug/179792 FIX: The fix is in 0.25, basically I changed the gconf keys over to moblin specific settings. Then I added a reader into moblin-settings-daemon which picks up the last resolution and rotation settings and applies them during moblin-settings-daemon launch. * BUG: "Cannot show battery life status by clicking Battery life icon on status bar" BUGLINK: https://bugs.launchpad.net/moblin-applets/+bug/176829 FIX: I added a pulldown which shows the percent charged, and if the device supports the battery.charge_level.rate ACPI event and corresponding HAL property, the remaining charge time or remaining battery time. * BUG: "Usability: can edit keyboard shortcut with symbol such as : ," BUGLINK: https://bugs.launchpad.net/moblin-applets/+bug/179004 FIX: I don't want to filter on what a user *can* use, since there may be unknown hardware buttons mapped into part of the ascii range of the keycode space, but I think it may be prudent to filter out the whole range of printable ascii characters. i.e. whatever passes g_ascii_isprint can't be bound. * BUG: "Usability: Suggest to change Background dialog "Finish" button to "Close" to be consistent with other applets dialog" BUGLINK: https://bugs.launchpad.net/moblin-applets/+bug/179788 FIX: Done - | Todd Brandt - Intel Oregon | |Linux for Mobile Internet Devices (MID)| | 2111 W NE 25th Ave| |Hillsboro, OR 97124 JF1-235| |---| | "Of all the things I've lost, I miss | |my mind the most" - Mark Twain | - -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
IRC meeting Thursday 2008-01-17 at 1700 UTC
Standard Time notice. Every Thursday at 17:00 UTC. Hi, The minutes for the IRC meeting held Thursday 2008-01-10 at 1700UTC are up at: https://wiki.ubuntu.com/MobileAndEmbedded/Meeting/20080110. We'll be having the next IRC meeting on #ubuntu-mobile, as usual, on Thursday 2008-01-17 at 1700 UTC. The new meeting page for this weeks meeting is at: https://wiki.ubuntu.com/MobileAndEmbedded/Meeting/20080117 Please add any topics of conversation that need to be covered at: Please make sure to post status reports to this list before 1400 UTC on Thursday, and if you have agenda items, please add them to the page on https://wiki.ubuntu.com/MobileAndEmbedded/Meeting/20080117 before the meeting. It will also greatly help if you tag your agenda items with your name. The meeting history page with links to prior meetings is at: https://wiki.ubuntu.com/MobileAndEmbedded/Meeting Thank you, David -- David Mandala http://www.canonical.com/ Public Key id: 45B2D952 Murphy TX, 75094 +1.214.774.2569 O +1.972.693.4007 C -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
FW: Hildon 2.0 Release
Perhaps we should review the differences and see how invasive they are and if we should move to this latest release. Suggestions welcome. Bob Xan López wrote: > = > Hildon 2.0 Stable Release > = > > The latest stable release of the Hildon Application Framework > (shipped on the latest OS2008 Maemo Release) is now available for > public consumption for hackers everywhere. > > A small start page for the release, including module overview, > porting instructions, changes since the latest version, etc. can be > found at http://live.gnome.org/Hildon/TwoPointZero/ > > The release is composed of: > > hildon-1 - > https://stage.maemo.org/svn/maemo/projects/haf/tags/hildon-1/2.0.1-1/ > > hail - > https://stage.maemo.org/svn/maemo/projects/haf/tags/hail/2.0.0-1/ > > sapwood - > https://stage.maemo.org/svn/maemo/projects/haf/tags/sapwood/3.0.0-1/ > > hildon-control-panel - > https://stage.maemo.org/svn/maemo/projects/haf/tags/hildon-control-panel/1:2.0.1-1/ > > hildon-desktop - > https://stage.maemo.org/svn/maemo/projects/haf/tags/hildon-desktop/2.0.6-1/ > > hildon-notify - > https://stage.maemo.org/svn/maemo/projects/haf/tags/hildon-notify/2.0.0-1/ > > hildon-fm - > https://stage.maemo.org/svn/maemo/projects/haf/tags/hildon-fm/1_2.0.0/ > > hildon-thumbnail - > https://stage.maemo.org/svn/maemo/projects/haf/tags/hildon-thumbnail/2.0.0/ > > libhildonmime - > https://stage.maemo.org/svn/maemo/projects/haf/tags/libhildonmime/2.0.0-1/ > > hildon-theme-layout-4 - > https://stage.maemo.org/svn/maemo/projects/haf/tags/hildon-theme-layout-4/0.14.8-1/ > > hildon-theme-plankton - > https://stage.maemo.org/svn/maemo/projects/haf/tags/hildon-theme-plankton/4.14.4-1/ > > The version number for the theme packages has not been 'bumped' > because it carries extra meaning: The major version number for the > plankton theme refers to the 'revision' of the theme-layout system > (4). The minor version numbers, being in sync (14), indicate that > both packages are compatible and should work ok together. > > hildon-theme-tools - > https://stage.maemo.org/svn/maemo/projects/haf/tags/hildon-theme-tools/0.5.2-1/ > > hildon-help - > https://stage.maemo.org/svn/maemo/projects/haf/tags/hildon-help/2.0.0-1/ > > hildon-input-method - > https://stage.maemo.org/svn/maemo/projects/haf/tags/hildon-input-method/1_2.0.0-1/ > > hildon-input-method-framework - > https://stage.maemo.org/svn/maemo/projects/haf/tags/hildon-input-method-framework/1_2.0.0-1/ > > hildon-input-method-plugins-example - > https://stage.maemo.org/svn/maemo/projects/haf/tags/hildon-input-method-plugins-example/2.0.0-1/ > > > On behalf of the Hildon team, happy hacking! > > > ___ > hildon-list mailing list > [EMAIL PROTECTED] > http://mail.gnome.org/mailman/listinfo/hildon-list -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: Backtrace
Hi, # echo 1 > /sys/module/drm/parameters/debug gives us more insight of what is happening inside the kernel... [drm:drm_stub_open] [drm:drm_open_helper] pid = 4753, minor = 0 [drm:drm_addmap_core] offset = 0x, size = 0x2000, type = 2 [drm:drm_addmap_core] 8192 13 f8a37000 [drm:drm_setup] [drm:drm_unlocked_ioctl] pid=4753, cmd=0xc0246400, nr=0x00, dev 0xe200, auth=1 [drm:drm_unlocked_ioctl] pid=4753, cmd=0xc0246400, nr=0x00, dev 0xe200, auth=1 [drm:drm_release] open_count = 1 [drm:drm_release] pid = 4753, device = 0xe200, open_count = 1 [drm:drm_fasync] fd = -1, device = 0xe200 [drm:drm_lastclose] [drm:drm_lastclose] driver lastclose completed [drm:drm_lastclose] lastclose completed [drm:drm_stub_open] [drm:drm_open_helper] pid = 4753, minor = 0 [drm:drm_addmap_core] offset = 0x, size = 0x2000, type = 2 [drm:drm_addmap_core] 8192 13 f8a37000 [drm:drm_setup] [drm:drm_unlocked_ioctl] pid=4753, cmd=0xc0246400, nr=0x00, dev 0xe200, auth=1 [drm:drm_unlocked_ioctl] pid=4753, cmd=0xc0246400, nr=0x00, dev 0xe200, auth=1 [drm:drm_release] open_count = 1 [drm:drm_release] pid = 4753, device = 0xe200, open_count = 1 [drm:drm_fasync] fd = -1, device = 0xe200 [drm:drm_lastclose] [drm:drm_lastclose] driver lastclose completed [drm:drm_lastclose] lastclose completed [drm:drm_stub_open] [drm:drm_open_helper] pid = 4753, minor = 0 [drm:drm_addmap_core] offset = 0x, size = 0x2000, type = 2 [drm:drm_addmap_core] 8192 13 f8a37000 [drm:drm_setup] [drm:drm_unlocked_ioctl] pid=4753, cmd=0xc0106407, nr=0x07, dev 0xe200, auth=1 [drm:drm_unlocked_ioctl] pid=4753, cmd=0xc0086401, nr=0x01, dev 0xe200, auth=1 [drm:drm_unlocked_ioctl] pid=4753, cmd=0xc0086401, nr=0x01, dev 0xe200, auth=1 [drm:drm_unlocked_ioctl] pid=4753, cmd=0xc0106407, nr=0x07, dev 0xe200, auth=1 [drm:drm_unlocked_ioctl] pid=4753, cmd=0xc0186415, nr=0x15, dev 0xe200, auth=1 [drm:drm_addmap_core] offset = 0x, size = 0x2000, type = 2 [drm:drm_mmap_locked] start = 0xb7b39000, end = 0xb7b3b000, page offset = 0xf8a37 [drm:drm_vm_open_locked] 0xb7b39000,0x2000 [drm:drm_do_vm_shm_nopage] shm_nopage 0xb7b39000 [drm:drm_do_vm_shm_nopage] shm_nopage 0xb7b3a000 [drm:drm_unlocked_ioctl] pid=4753, cmd=0xc0186415, nr=0x15, dev 0xe200, auth=1 [drm:drm_addmap_core] offset = 0x3fc0, size = 0x1000, type = 0 [drm:drm_unlocked_ioctl] pid=4753, cmd=0xc0086426, nr=0x26, dev 0xe200, auth=1 [drm:drm_unlocked_ioctl] pid=4753, cmd=0xc0086426, nr=0x26, dev 0xe200, auth=1 [drm:drm_unlocked_ioctl] pid=4753, cmd=0xc0086420, nr=0x20, dev 0xe200, auth=1 [drm:drm_addctx] 1 [drm:drm_unlocked_ioctl] pid=4753, cmd=0x40086422, nr=0x22, dev 0xe200, auth=1 [drm:drm_unlocked_ioctl] pid=4753, cmd=0x4008642a, nr=0x2a, dev 0xe200, auth=1 [drm:drm_lock] 1 (pid 4753) requests lock (0x), flags = 0x [drm:drm_lock] 1 has lock This first context (whatever it is) has a successful lock here. [drm:drm_fasync] fd = 10, device = 0xe200 [drm:drm_unlocked_ioctl] pid=4753, cmd=0xc0246400, nr=0x00, dev 0xe200, auth=1 [drm:drm_unlocked_ioctl] pid=4753, cmd=0xc0246400, nr=0x00, dev 0xe200, auth=1 [drm:drm_unlocked_ioctl] pid=4753, cmd=0x800c64d6, nr=0xd6, dev 0xe200, auth=1 [drm:drm_unlocked_ioctl] pid=4753, cmd=0xc0086420, nr=0x20, dev 0xe200, auth=1 [drm:drm_addctx] 2 [drm:drm_unlocked_ioctl] pid=4753, cmd=0xc0106403, nr=0x03, dev 0xe200, auth=1 [drm:drm_irq_by_busid] 0:2:0 => IRQ 17 [drm:drm_unlocked_ioctl] pid=4753, cmd=0x40086414, nr=0x14, dev 0xe200, auth=1 [drm:drm_irq_install] drm_irq_install: irq=17 [psb:0x01:psb_irq_postinstall] Setting up MSVDX IRQs. [drm:drm_unlocked_ioctl] pid=4753, cmd=0x4008642a, nr=0x2a, dev 0xe200, auth=1 [drm:drm_lock] 2 (pid 4753) requests lock (0x8001), flags = 0x [drm:drm_lock] 2 interrupted This second lock failed here. This is where we Ctrl-C'ed the X server running under gdb. Now to figure out what this second lock is [drm:drm_unlocked_ioctl] ret = -512 [drm:drm_vm_shm_close] 0xb7b39000,0x2000 [drm:drm_release] open_count = 1 [drm:drm_release] pid = 4753, device = 0xe200, open_count = 1 [drm:drm_release] File f7762a80 released, freeing lock for context 1 [drm:drm_fasync] fd = -1, device = 0xe200 [drm:drm_lastclose] [drm:drm_lastclose] driver lastclose completed [drm:drm_irq_uninstall] drm_irq_uninstall: irq=17 [drm:drm_lastclose] lastclose completed Regards, Amit On Jan 17, 2008 1:21 AM, Amit Kucheria <[EMAIL PROTECTED]> wrote: > I am currently reading through that part of the code to make sure that > some Kconfig options are not responsible for this behaviour. If you > can think of any, it would be a help. > > Regards, > Amit > > > On Jan 17, 2008 1:17 AM, Bastian, Waldo <[EMAIL PROTECTED]> wrote: > > DRM_IOCTL_LOCK ends up with drm_lock() in drm_lock.c part of drm.ko > > > > Cheers, > > Waldo > > > > Intel Corporation - Platform Software Engineering, UMG - Hillsboro, > > Oregon > > > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On
Midbrowser status update (1-10-08 -> 1-17-08)
* Team is busy working on moving from FF 3.0 beta 1 to beta 2 code base. * Looking into why bookmark not working in FF3.0 based Midbrowser. * Got some good performance numbers from QA on FF3.0 base Midbrowser. The average page rendering is close to 50% faster with the FF3.0 beta1 based code. However the startup time appears to be slower. * We have got permission from the owner of the grabanddrag addon to use in Midbrowser to provide finger scrolling. Carl -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: how to run as ume user in Xephyr?
Thanks for the info, Loic. If it were made more straightforward (maybe even the default), folks would be more likely to run as ume user in Xephyr target, which might help unearth bugs. Kyle On Jan 17, 2008, at 7:16 AM, Loïc Minier wrote: >Hi Kyle, > > On Wed, Jan 16, 2008, Kyle Nitzsche wrote: >> Anyone know how to launch target in Xephyr as ume user, not root? > > This is something I do regularly, but which is very hackish. > > First, I have an ume user on my host; it has uid 1001. > > Second, the ume user is usually created by ume-config-common in the > targets but with first available uid of 1000. I change this uid in > /etc/passwd and /etc/group in the /targets//fs chroot. > > Third, I'm fixing the Xephyr startup to run as ume: > - I install xserver-xephyr manually as root > - I start dbus manually in the chroot as root and comment this out of > the ume-xephyr-start script > - I make sure that /tmp is bind mounted (image-creator does this > automatically I think) as well as /home (for Xauthority) > > CAUTION: if you bind mount /home, make sure you unmount it before > removing your target, or you could cause image-creator to rm -rf > your > home > > This works well for me, but should be made more easy. Also, this > doesn't plug the current hole that Xephyr is run with -ac in the > script, but that's not an issue on single user systems. > > -- > Loïc Minier > > -- > Ubuntu-mobile mailing list > Ubuntu-mobile@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: how to run as ume user in Xephyr?
Hi Kyle, On Wed, Jan 16, 2008, Kyle Nitzsche wrote: > Anyone know how to launch target in Xephyr as ume user, not root? This is something I do regularly, but which is very hackish. First, I have an ume user on my host; it has uid 1001. Second, the ume user is usually created by ume-config-common in the targets but with first available uid of 1000. I change this uid in /etc/passwd and /etc/group in the /targets//fs chroot. Third, I'm fixing the Xephyr startup to run as ume: - I install xserver-xephyr manually as root - I start dbus manually in the chroot as root and comment this out of the ume-xephyr-start script - I make sure that /tmp is bind mounted (image-creator does this automatically I think) as well as /home (for Xauthority) CAUTION: if you bind mount /home, make sure you unmount it before removing your target, or you could cause image-creator to rm -rf your home This works well for me, but should be made more easy. Also, this doesn't plug the current hole that Xephyr is run with -ac in the script, but that's not an issue on single user systems. -- Loïc Minier -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
