Re: [MeeGo-dev] Getting the address of the session dbus daemon
On Tuesday 21. September 2010 23.46.35 you wrote:
DBUS_SESSION_BUS_WINDOWID=2097153
this method works in MeeGo
Even:
~ $ DISPLAY=:0 xprop -id 2097153
_DBUS_SESSION_BUS_PID(CARDINAL) = 2240
_DBUS_SESSION_BUS_ADDRESS(STRING) = unix:abstract=/var/tmp/dbus-
Q0hEx2EutZ,guid=bf3858a278afe694d3e5716f000d
this doesn't...
Well, the window ID might change. Did you use the ID that you got from dbus-
launch?
Getting the ID without dbus-launch is quite hard.
The address is also stored in a file in the user's home directory:
~ $ cat ~/.dbus/session-bus/`cat /var/lib/dbus/machine-id `-${DISPLAY#:}
# This file allows processes on the machine with id
34c4eb0b08ea6c20b83bef9c0006 using
# display :0 to find the D-Bus session bus with the below address.
# If the DBUS_SESSION_BUS_ADDRESS environment variable is set, it will
# be used rather than this file.
# See man dbus-launch for more details.
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/var/tmp/dbus-
Q0hEx2EutZ,guid=bf3858a278afe694d3e5716f000d
DBUS_SESSION_BUS_PID=2240
DBUS_SESSION_BUS_WINDOWID=2097153
This also doesnt work, not sure why, but I'm not too worried unless I
see a bugreport :)
Probably my shell-fu in ${DISPLAY#:}. I don't think it's correct.
For DISPLAY=:x.y, the file contains just x. You have to drop the colon and
the screen number.
--
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] Trademark compliance, name usage, etc.
Hi, Peter Robinson wrote: If so, great, what's happening with a few distros that are shipping MeeGo without using ConMan? Fedora is planning on stripping the MeeGo logos and just using the UX as if it was gnome/kde. Just wondering, what do the UI developers call the MeeGo desktop environment? There is more than Mutter, right? meego-panel-myzone, meego-panel-people, etc (collectively called meego-panel, I guess?) If the UX layer had a name other than MeeGo or MeeGo Netbook UX then presumably there'd be less of an issue. But if that's called MeeGo Netbook UX (breaking MeeGo's own trademark guidelines) then calling it that without the entire MeeGo stack there doesn't seem to me to be a problem. Cheers, Dave. -- maemo.org docsmaster Email: dne...@maemo.org Jabber: bo...@jabber.org ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Trademark compliance, name usage, etc.
On Wed, Sep 22, 2010 at 1:08 AM, Greg KH gre...@suse.de wrote: On Tue, Sep 21, 2010 at 09:29:43PM +0100, Peter Robinson wrote: On Mon, Sep 20, 2010 at 9:25 PM, Greg KH gre...@suse.de wrote: On Mon, Sep 20, 2010 at 01:16:40PM -0700, Auke Kok wrote: On 09/20/10 12:42, Andrew Wafaa wrote: Firstly sorry if this is the wrong list to send this question to, please advise on the best one if it isn't here. I have been spending my time trying to get the MeeGo UX into reasonable shape on my preferred distro of choice - openSUSE. Now before I make any form of release/spin/$WHATEVER I would just like to get clarification on what I can/can't use. My understanding is that to use the word MeeGo in any direct naming is a no-no unless I pass compliance, of which part of that would mean taking on Connman and other parts of the MeeGo stack that just aren't in my preferred distro and to be honest, we wouldn't want them in there as we have a well tried tested stack. So my simple question is, if I use the MeeGo UX can I say $RELEASE is based on MeeGo's User eXperience, sitting ontop of $DISTRO. Complimenting the other Desktop Environments that are on offer, and offering some additional components (listing components). When things were Moblin, there was a clearly defined usage of UX. This seems to have disappeared under MeeGo so things aren't as simple as they used to be. I hate to say it, but for all cases where legal issues are involved, please consult your lawyer. Hey, that's totally not fair here. This is being done by a community project, for which there are no lawyers. And does this mean that some lawyer is going to come after any developer who doesn't abide by the mythical MeeGo compliance rules? If so, great, what's happening with a few distros that are shipping MeeGo without using ConMan? Fedora is planning on stripping the MeeGo logos and just using the UX as if it was gnome/kde. I think that's the goal here for Smeegol as well. By doing that, you don't have to mess with any of the crap that people are trying to claim here, which is a very good idea. If nothing, then fine, we'll just ignore the empty lawyer threats. If something, then great, what exactly are the rules that need to be followed here? We've asked and got very little response so with discussion amongst ourselves we've decided on the above. Currently we're planning to initially do the Netbook UX but there is interest in some of the others. Thanks for letting me know. So, that makes at least 2 community-based respins of the MeeGo netbook UX code. I guess if we don't even refer to the MeeGo stuff at all here, we should be fine. Although getting an official response from the LF would be good. If I don't hear back in a few days, I'll go start poking people... As part of the discussion we had internally I believe RH legal spoke to the LF and got some sort of response that it would be fine if we complied with the requirements and kept getting referred to the website and we complied with all open documented requirements but then we got an off the cuff unofficial comment along the lines of so your going to support conman? The closest I got was this architecture doc [1] which will have all but conman and ofono. The last I don't see as an issue as we're not a phone and we never intend on supporting the application store as that's not what Fedora is about. Peter [1] http://meego.com/developers/meego-architecture ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Trademark compliance, name usage, etc.
On Wed, Sep 22, 2010 at 7:55 AM, Dave Neary dne...@maemo.org wrote: Hi, Peter Robinson wrote: If so, great, what's happening with a few distros that are shipping MeeGo without using ConMan? Fedora is planning on stripping the MeeGo logos and just using the UX as if it was gnome/kde. Just wondering, what do the UI developers call the MeeGo desktop environment? There is more than Mutter, right? meego-panel-myzone, meego-panel-people, etc (collectively called meego-panel, I guess?) If the UX layer had a name other than MeeGo or MeeGo Netbook UX then presumably there'd be less of an issue. But if that's called MeeGo Netbook UX (breaking MeeGo's own trademark guidelines) then calling it that without the entire MeeGo stack there doesn't seem to me to be a problem. We don't plan on calling it MeeGo, likely something like Fedora Netbook Spin or similar and mention it uses the MeeGo Netbook UX or something along those lines. Peter ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Creating a Python project for MeeGo
On 09/22/10 07:42, Kellomaki Pertti (Nokia-MS/Tampere) wrote: On 09/21/2010 03:33 PM, Poussa Sakari (Nokia-MS/Helsinki) wrote: However, we are in the process of publishing the core os package list which would then end of in the repos as well. Now the core os package list is undefined. Please cross check the list with the MeeGo bugzilla. There are now packages (e.g. meegotouch-*) that are in the core repository but bugzilla has them in the handset ux. Yes, the bugzilla is a mess. We are working on that one as well to make the structure more sensible. -sakari ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Services
I have some questions about starting of services in MeeGo: I have seen that the rc.sysinit is used pretty heavily to start services is this a permanent solution or a quick fix ? If not is there any plan on when to fix this ? Is there any document describing how starting of services should be done in MeeGo ? I read in a mail thread here about init/upstart/systemd what's the plan for the MeeGo starting at the moment ? /R ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] HLEP: How to Show Meego Handset UI on BeagleBoard
Hi, I followed the wiki http://wiki.meego.com/ARM/Meego_on_Beagleboard_from_scratch, and can boot the meego from console, but no UI show up, just a black screen with a cursor. The attachment is my log. During copying the rootfs, I met a problem, after use this command sudo rsync -aHx --progress --delete ./image/* /media/root, I try to use this command tar xvfz 2.6.35.5-x4-modules.tar.gz -C /media/root, but it failed. Then, I add sudo to execute this command, after that the /media/root can not be accessed any more. So, I just use sudo cp command to copy all the file under image/ to /media/root/, then install the kernel and modules. Is this cause the problem? Please help me! Thanks a lot! Chen OMAP3 beagleboard.org # setenv bootcmd 'mmc init; fatload mmc 0 0x8200 uImage;bootm 0x8200' OMAP3 beagleboard.org # setenv bootargs 'mem=256M console=ttyS2,115200n8 mpurate=600 buddy=unknown vram=12M vram=12M omapfb.vram=0:4M,1:4M,2:4M omapfb.mode=dvi:hd720 omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait' OMAP3 beagleboard.org # boot mmc1 is available reading uImage 4468232 bytes read ## Booting kernel from Legacy Image at 8200 ... Image Name: Linux-2.6.35.5-x4 Image Type: ARM Linux Kernel Image (uncompressed) Data Size:4468168 Bytes = 4.3 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.35.5-x4 (d...@dc-laptop) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #1 PREEMPT Tue Sep 21 11:05:53 CST 2010 [0.00] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f [0.00] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache [0.00] Machine: OMAP3 Beagle Board [0.00] Beagle expansionboard: unknown [0.00] Memory policy: ECC disabled, Data cache writeback [0.00] OMAP3430/3530 ES3.1 (l2cache iva sgx neon isp ) [0.00] SRAM: Mapped pa 0x4020 to va 0xfe40 size: 0x10 [0.00] Reserving 12582912 bytes SDRAM for VRAM [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 [0.00] Kernel command line: mem=256M console=ttyS2,115200n8 mpurate=600 buddy=unknown vram=12M vram=12M omapfb.vram=0:4M,1:4M,2:4M omapfb.mode=dvi:hd720 omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait [0.00] PID hash table entries: 1024 (order: 0, 4096 bytes) [0.00] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) [0.00] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) [0.00] allocated 1310720 bytes of page_cgroup [0.00] please try 'cgroup_disable=memory' option if you don't want memory cgroups [0.00] Memory: 256MB = 256MB total [0.00] Memory: 230328k/230328k available, 31816k reserved, 0K highmem [0.00] Virtual kernel memory layout: [0.00] vector : 0x - 0x1000 ( 4 kB) [0.00] fixmap : 0xfff0 - 0xfffe ( 896 kB) [0.00] DMA : 0xffc0 - 0xffe0 ( 2 MB) [0.00] vmalloc : 0xd080 - 0xf800 ( 632 MB) [0.00] lowmem : 0xc000 - 0xd000 ( 256 MB) [0.00] modules : 0xbf00 - 0xc000 ( 16 MB) [0.00] .init : 0xc0008000 - 0xc0049000 ( 260 kB) [0.00] .text : 0xc0049000 - 0xc080f000 (7960 kB) [0.00] .data : 0xc0888000 - 0xc08e7960 ( 383 kB) [0.00] SLUB: Genslabs=9, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [0.00] Hierarchical RCU implementation. [0.00] RCU-based detection of stalled CPUs is disabled. [0.00] Verbose stalled-CPUs detection is disabled. [0.00] NR_IRQS:402 [0.00] Clocking rate (Crystal/Core/MPU): 26.0/332/720 MHz [0.00] omap_hwmod: l3_hwmod: cannot be enabled (3) [0.00] omap_hwmod: l4_core_hwmod: cannot be enabled (3) [0.00] omap_hwmod: l4_per_hwmod: cannot be enabled (3) [0.00] omap_hwmod: l4_wkup_hwmod: cannot be enabled (3) [0.00] Reprogramming SDRC clock to 33200 Hz [0.00] GPMC revision 5.0 [0.00] IRQ: Found an INTC at 0xfa20 (revision 4.0) with 96 interrupts [0.00] Total of 96 interrupts on 1 active controller [0.00] OMAP GPIO hardware version 2.5 [0.00] OMAP clockevent source: GPTIMER12 at 32768 Hz [0.00] Console: colour dummy device 80x30 [0.00] Calibrating delay loop... 690.06 BogoMIPS (lpj=2695168) [0.00] pid_max: default: 32768 minimum: 301 [0.00] Security Framework initialized [0.00] Smack: Initializing. [0.00] Mount-cache hash table entries: 512 [0.00] Initializing cgroup subsys ns [
Re: [MeeGo-dev] Install Meego to N900
Can MeeGo be installed to N95(TI OMAP2420)? Thanks Felix changhong electric co., ltd -- Original -- From: Sharavana Ram Kumar Ssharavan...@aricent.com; Date: Wed, Sep 22, 2010 01:17 PM To: meego-dev@meego.commeego-dev@meego.com; Subject: Re: [MeeGo-dev] Install Meego to N900 Hi, Get the Meego image specified in the below link: 1) Try with prebuilt images given in link: http://tablets-dev.nokia.com/meego-codedrop.php Download the below files from the above link Rootfs file (To be put on the micro sd): meego-handset-armv5tel-n900-nokia-proprietary-1.0.80.13.20100803.2-mmcblk0p.raw.bz2 Kernel image(To be flashed on the device): meego-handset-armv5tel-n900-nokia-proprietary-1.0.80.13.20100803.2-vmlinuz-2.6.35~rc6-133.2-n900 (OR) 2) If you build the image yourself using mic tool then download the kickstart file as specified in the below link: http://forum.meego.com/showpost.php?p=6580postcount=90 Using the rootfs and the kernel try bringing up Meego on n900 Hope you are aware of the steps to copy rootfs to the microSD and flasher tool to flash meego kernel into N900 Regards Sharavana Aricent Technologies (Holdings) Limited Bangalore. DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. ___ 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] Still question on MeeGo on devkit8000
On Wed, Sep 22, 2010 at 3:56 PM, Markus Kreidl markus.kre...@gmail.com wrote: Hi I saw you thread, and maybe you have a idea. I compiled 2.6.35-rc3-g6042075 kernel SGX is adapted, compiled and installed - sgx_blit_test is working. (on devkit8000) BUT I do not get any GUI from the meego system. when I start meego-dm it gets killed. Do I need to install additional packages ? Are you getting any errors while running eglinfo, it is the test binary you get with the SGX package. This may help as well http://e2e.ti.com/support/embedded/f/354/p/58411/209974.aspx Regards, Amit Pundir thx markus ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Meego on the Beagleboard
2010/9/21 Chen Dai daichen...@gmail.com: Hi Amit, I'm a newer to Meego, and I have got a Devkit 8000 with the LCD. I want to run Meego on Devkit 8000. I have already built the rootfs followed http://wiki.meego.com/ARM/Meego_on_Beagleboard_from_scratch#Build_the_rootfs What's the next should I do? How to build the devkit 8000 kernal and bootloader? Can you share your step and other info? Here you go :) Clone Devkit8000 kernel $ git clone git://gitorious.org/devkit8000/linux-omap-devkit8000.git Clone u-boot $ git clone git://git.denx.de/u-boot.git setenv bootargs 'bootargs=console=ttyS2,115200n8 noinitrd root=/dev/mmcblk0p2 rootfstype=ext3 rw nohz=off rootdelay=5 omapdss.def_disp=lcd omapfb.mode=lcd:800x480' setenv bootcmd 'mmc init; fatload mmc 0 0x8030 uImage; bootm 0x8030' Regards, Amit Pundir Thank you very much:), looking forward to your reply Chen 2010/7/23 Amit Pundir pundira...@gmail.com: On Fri, Jul 23, 2010 at 9:12 AM, vijay singh testmrs@gmail.com wrote: On Thu, 2010-07-22 at 15:50 -0400, Jason Kridner wrote: On Sun, Jul 11, 2010 at 7:29 AM, Coffey Wei coffey...@gmail.com wrote: Dear All, Now，I'm trying to let Meego to work at TCC89XX, I will feed back everynew of Meego_TCC89XX, In China, there's no Beagleboard! so I choose TCC89xx. Actually, you can get the BeagleBoard in China, but, you might otherwise go with the Embest DevKit8000 (http://elinux.org/DevKit8000). I have tried MeeGo on DevKit but not able to boot the kernel. Hi, I'm able to boot the kernel-2.6.35.xx on devkit few days back. I was dropped to a shell. Only thing I verified that time was touch-screen and ethernet. I didn't get enough time to play around UI/X but I will surely count on the instructions given here http://wiki.meego.com/ARM/Meego_on_Beagleboard_from_scratch Check the following thread to get the devkit8000 kernel and u-boot source links: http://groups.google.com/group/beagleboard/browse_thread/thread/3e02302066a6c003?pli=1 regards, Amit Pundir I have used FS from below location http://wiki.meego.com/ARM/Meego_on_Beagleboard_from_scratch#Make_X_start If any one able to up the DevKit then please share the experience. On Sat, Jul 10, 2010 at 7:01 PM, Till Harbaum / Lists li...@harbaum.org wrote: Hi, http://wiki.meego.com/ARM/Meego_on_Beagleboard_from_scratch Till Am Samstag 10 Juli 2010 schrieb Erandi Chavolla: Hi All, I'm trying to flash meego on the beagleboard but I have some issues could you help me, I'm following this steps: http://wiki.meego.com/ARM/Meego_on_the_Beagle But are not working, if someone already did please share with me the steps. Thanks in advance Erandi ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev -- df ___ 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 ___ 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] Meego on the Beagleboard
Amit Pundir had written, on 09/22/2010 06:06 AM, the following: 2010/9/21 Chen Dai daichen...@gmail.com: Hi Amit, I'm a newer to Meego, and I have got a Devkit 8000 with the LCD. I want to run Meego on Devkit 8000. I have already built the rootfs followed http://wiki.meego.com/ARM/Meego_on_Beagleboard_from_scratch#Build_the_rootfs What's the next should I do? How to build the devkit 8000 kernal and bootloader? Can you share your step and other info? Here you go :) Clone Devkit8000 kernel $ git clone git://gitorious.org/devkit8000/linux-omap-devkit8000.git Clone u-boot $ git clone git://git.denx.de/u-boot.git just fyi - i created a u-boot package in build.meego.com with build support for beagleboard as well.. we may want to consider using it in the mic maybe? setenv bootargs 'bootargs=console=ttyS2,115200n8 noinitrd root=/dev/mmcblk0p2 rootfstype=ext3 rw nohz=off rootdelay=5 omapdss.def_disp=lcd omapfb.mode=lcd:800x480' setenv bootcmd 'mmc init; fatload mmc 0 0x8030 uImage; bootm 0x8030' would be better to do this as part of boot.scr. -- Regards, Nishanth Menon ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Services
On 9/22/2010 1:05 AM, Robert MARKLUND wrote: I have some questions about starting of services in MeeGo: I have seen that the rc.sysinit is used pretty heavily to start services is this a permanent solution or a quick fix ? this is a permanent solution, not a quick hack. our core OS boot flow is pretty carefully laid out in terms of ordering and which services are on the critical path versus which ones are background. if you want to add your own services, you can just put a normal regular init script in place. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Trademark compliance, name usage, etc.
On Wed, Sep 22, 2010 at 07:58:19AM +0100, Peter Robinson wrote:
As part of the discussion we had internally I believe RH legal spoke
to the LF and got some sort of response that it would be fine if we
complied with the requirements and kept getting referred to the
website and we complied with all open documented requirements but then
we got an off the cuff unofficial comment along the lines of so your
going to support conman?
{sigh} This isn't the first time I've heard this type of thing
happening, and again, it's totally not acceptable.
I'll keep following up on this...
thanks,
greg k-h
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Problems about Meego image-creator
Hi, I checked the latest mic from git, and make installed it, but I have some problems 1. mic-check-alldeps will check and install all depended packages, when checking the syslinux, it will show ''mic2 requires syslinux version = 3.85, please update syslinux to 3.85 but I have already installed syslinux 4.02. Is syslinux 4.02 supported? Or I must install 4.00? Because it is very hard to install 4.00, the sudo apt-get install syslinux=4.00 can not find and install 4.00. The syslinux 4.00 also can not be found in meego repo. 2. I try to build meego handst img for beagle, and used this command sudo mic-image-creator --run-mode=0 --cache=mycachedir --format=loop --arch=armv7l --release=daily --config=handset-armv7l-beagle.ks But during the creating, there were some warnings and errors Installing: dbus [ 35/447]warning: group dbus does not exist - using root Installing: sysvinit-tools [ 67/447]warning: group tty does not exist - using root Installing: grep # [ 81/447] install-info: No such file or directory for /usr/share/info/grep.info.gz Installing: cpp # [122/447] install-info: No such file or directory for /usr/share/info/cpp.info.gz Installing: meegotouch-feedback # [127/447] /var/tmp/rpm-tmp.nnp0XQ: line 3: mkdir: command not found /var/tmp/rpm-tmp.nnp0XQ: line 5: ln: command not found warning: %post(meegotouch-feedback-0.10.4-1.2.armv7l) scriptlet failed, exit status 127 Installing: libutempter ## [169/447]warning: group utempter does not exist - using root warning: group utmp does not exist - using root Installing: binutils # [175/447] install-info: No such file or directory for /usr/share/info/as.info install-info: No such file or directory for /usr/share/info/binutils.info install-info: No such file or directory for /usr/share/info/gprof.info install-info: No such file or directory for /usr/share/info/ld.info install-info: No such file or directory for /usr/share/info/standards.info install-info: No such file or directory for /usr/share/info/configure.info Installing: libgomp # [176/447] install-info: No such file or directory for /usr/share/info/libgomp.info.gz Installing: glibc-devel # [227/447] install-info: No such file or directory for /usr/share/info/libc.info.gz Installing: gcc # [234/447] install-info: No such file or directory for /usr/share/info/gcc.info.gz Installing: coreutils# [242/447] install-info: No such file or directory for /usr/share/info/coreutils.info Installing: util-linux-ng### [249/447]warning: group tty does not exist - using root Installing: util-linux-ng# [249/447] install-info: No such file or directory for /usr/share/info/ipc.info Installing: avahi [298/447]warning: user avahi does not exist - using root warning: group avahi does not exist - using root Installing: openssh-clients # [345/447]warning: group nobody does not exist - using root Running scripts /bin/sed: can't read /etc/gconf/gconf.xml.moblin/%gconf-tree.xml: No such file or director Is that ok? What cause those errors? 3. finally, the img created, but there is still an error. close failed in file object destructor: IOError: [Errno 9] Bad file descriptor What does this mean? 4. Is there or somewhere I can download the beagle image file directly? Thanks in advance! Chen ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Terminal on MeeGo Handheld image on pinetrail
Hi all, Two questions on MeeGo Handheld on Pinetrail - Is there any build of MeeGo Handheld for pinetrail where the xterminal actually works from within the UI? Even the most recent build from here: http://repo.meego.com/MeeGo/builds/1.0.90/1.0.90.3.20100917.1/handset/images/meego-handset-ia32-pinetrail-mtf/ has problems. It launches but you see only a black screen, which you need to exit by typing blindly exit. Cntrl-Alt-F1 helps, but in certain cases I want to launch a UI app from the terminal. - Is there a developer version of MeeGo Handheld on Pinetrail, with yum, gcc, rpm tools, etc?? Downloading everything is extremely painful, and time consuming. By the way, there is a problem with the zypper config files. You have to remove the proxy otherwise you get the following error: Download (curl) error for 'http://repo.meego.com/MeeGo/builds/trunk/preview/non-oss/repos/ia32/packages/content?proxy=httpproxyport=//192.168.50.99:3128/': Error Code: Connection Failed Error Message: Couldn't connect to host Rami -- Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/Muenchen, Deutschland Sitz der Gesellschaft: Feldkirchen bei Muenchen Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer Registergericht: Muenchen HRB 47456 Ust.-IdNr./VAT Registration No.: DE129385895 Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052 ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] [announce] MeeGo kernel mailing list
Hi, I'd like to announce the creation/existence of the MeeGo kernel mailing list, and I'd like to invite all interested parties to join and help us review patches and make the MeeGo kernel the best distro kernel in the industry. To join, use the mailman interface at http://lists.meego.com/listinfo/meego-kernel (in case you wonder why this is not done on meego-dev... meego-dev is not suitable at this point for this kind of thing) ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Terminal on MeeGo Handheld image on pinetrail
- Is there any build of MeeGo Handheld for pinetrail where the xterminal actually works from within the UI? Even the most recent build from here: http://repo.meego.com/MeeGo/builds/1.0.90/1.0.90.3.20100917.1/handset/images/meego-handset-ia32-pinetrail-mtf/ has problems. It launches but you see only a black screen, which you need to exit by typing blindly “exit”. Just FYI, I'm experiencing a similar issue with MeeGo Handheld for N900, I can only see the commands/output when the window is 'zoomed out' in the task switcher. Is there a developer version of MeeGo Handheld on Pinetrail, with yum, gcc, rpm tools, etc?? Downloading everything is extremely painful I would use the appropiate kickstart file and add the development packages to generate the image. - Fernando ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] MeeGo 1.1 Development Release 1.0.90.3.20100921.1 is available
Status summary for supported hardware = Highlights and Issues: Handset, Aava: * Music player crash reported in the preview release are no longer seen. * Email icon is still unavailable (now a red block is seen in its place) (Bug 7003) * Logical strings appear on the settings applications (Bug 7612) * Screen is blank on start up, tapping on the screen once shows up the home screen (Bug 5705) * VKB has issues launching and operating. VKB launching is not consistent, the user is unable to see characters getting entered in the text area. (Bug 6047) * Email, social networking applications present in the application matrix but they are not fully useable. It’s usage is blocked due to the VKB issue. * Touch screen calibration is still a bit skewed. (Bug 4985) * The typed content not displayed unless VKB is closed. (Bug 6047) * Certain applications have missing icons, red blocks are shown instead. (Bug 3921) * Calibration application is broken, on exiting turns the screen blank, recovering to the home screen is very difficult. (Bug 5127) * Audio still does not work on Aava, though the default media is visible. Handset, Pinetrail: * Email icon is not appearing in the quick launch area. (Bug 7003) * Logical strings appear on the settings applications (Bug 7612) * Screen remains black after boot up, tapping on the touchpad reveals the home UI (Bug 3916) * Tapping on text entry blocks out the whole screen. (Bug 5606) * Applications that require configurations (Chat, Social Networking, Email) is blocked due to this. * Default videos still unavailable. * X-term is not working correctly. (Bug 3551) * Trying to open the status area by clicking and dragging down the top area of the screen blacks out the screen (Bug 3561) Handset, N900: * Browser launching is still broken (Bug 4021) * Most applications launch and work normally * Battery charging does not work, bug listed as fixed (Bug 2260) Netbook, generic ia32 netbook: * Image found to be quite stable. * No major issues spotted. Available images Handset http://repo.meego.com/MeeGo/builds/1.0.90/1.0.90.3.20100921.1/handset/images/meego-handset-ia32-aava-mtf-devel/ http://repo.meego.com/MeeGo/builds/1.0.90/1.0.90.3.20100921.1/handset/images/meego-handset-ia32-aava-mtf/ http://repo.meego.com/MeeGo/builds/1.0.90/1.0.90.3.20100921.1/handset/images/meego-handset-ia32-mtf-devel/ http://repo.meego.com/MeeGo/builds/1.0.90/1.0.90.3.20100921.1/handset/images/meego-handset-ia32-mtf/ http://repo.meego.com/MeeGo/builds/1.0.90/1.0.90.3.20100921.1/handset/images/meego-handset-ia32-pinetrail-mtf/ Netbook http://repo.meego.com/MeeGo/builds/1.0.90/1.0.90.3.20100921.1/netbook/images/meego-netbook-ia32/ Features 5214 Elantech kernel module needed for EeePC 901 touchpad 3067 [FEA] Voice-over-IP (VoIP) application 4353 [FEA] Email Composer Send action 4357 [FEA] Email Signature 3068 [FEA] Instant Messaging (IM) application Bugs fixed: === 746 refresh/install/update functions in pkcon and gpk applications do not if proxy set 1030 No prompt message when download/install package if the disk space is insufficient 2492 Update system translation misspelling 3246 Changes to contacts data not reflected in dialer 3921 [REG] Some buttons (App-launcher, Home, Close) and app icons (Settings/Lock icons) are rendered as red blocks 4979 no default radio button is selected in Manage Apps-Filters-Source 5281 [Audio player][REG]No A-Z alphabetic bar showed in the audio player 5784 [Video player]There are not played time and total time in the time line 5804 X failed to start in QEMU with -vga std after xserver upgraded to 1.8.99 5838 dialer seg faults when ofono isn't running. 5987 xterm terminal should not be integrated in MeeGo image 5991 [Audio player][REG]it is unable to save a new creating playlist 6026 Email launched from quick launch bar and app-launcher are not consistent 6058 Expose an interface to get Recent Communications from a Contact 6076 meegotouchcp-telephony doesn't match wireframes 6153 No Settings/Refresh buttons for social networking 6154 Social networking status appears randomly in stead of fixed order by date 6174 timed not started 6221 [Chat] Unable to create IM account in Chat application 6222 The size of the Appointment window is not enough 6242 Request Email for a DBus interface for sharing photo 6277 The default POP3/SMTP/IMAP incoming/outgoing port number is incorrect 6285 videoplayer not properly localized: movie folder names hardcoded 6291 Updated visual assets not being used 6295 Potential format string vulnerability from web server content 6302 [Photo viewer]the textfield is still in the bottom after switching into All photos or Albums from the search category 6317 [REG] Social networking status background color is red 6319 [REG] Load social networking main window when set up account 6435 Black BAR is coming on top,in Album View of Photo application
[MeeGo-dev] [announce] MeeGo Security Discussion List
All, Like Arjan did for the kernel mail list, I would like to announce the creation/existence of the MeeGo Security Discussion list and would like to invite any and all who are interested in various parts of MeeGo security (generic OS configuration, security framework, infrastructure security, etc.) The mailman interface for this list is at http://lists.meego.com/listinfo/meego-security-discussion If you have any questions/concerns, please feel free to voice them here or email me directly. As always, if you feel you have found a security issue with meego, please report it to secur...@meego.com. Thanks, Ryan ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Which package has QApplication?
Thanks, this was the solution: zypper install libqt-devel Best regards, Axel. fathi.bou...@nokia.com 09/17/2010 04:16 PM To axel.end...@renesas.com cc meego-dev@meego.com Subject RE: [MeeGo-dev] Which package has QApplication? Here's your problem: Qt's headers are not in /usr/include/qt4, they are in /usr/include. pkg-config even says so. No, only Qt development package is missing (libqt-devel or qt-devel). Cheers, Fathi ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo Porting Guide available for reading
On Sep 13, 2010, at 9:30 AM, Foster, Dawn M wrote: On Sep 13, 2010, at 3:18 AM, jari.paloja...@nokia.com jari.paloja...@nokia.com wrote: In my opinion, a meego-porting mailing list would be a good idea. Dawn (and others) – any thoughts about this? We're getting a lot of porting questions, so I think it's probably a good time to create a specific list for it. I'll try to have it available at the end of this week or early next week. Jari - would you be the primary contact for this new list? The new meego-porting list has been created. More details: http://lists.meego.com/listinfo/meego-porting Dawn ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] Blank xterm (was: Re: Terminal on MeeGo Handheld image on pinetrail)
On 09/22/2010 11:09 PM, ext Fernando Muñoz wrote: xterminal actually works from within the UI? Even the most recent build from here: http://repo.meego.com/MeeGo/builds/1.0.90/1.0.90.3.20100917.1/handset/images/meego-handset-ia32-pinetrail-mtf/ has problems. It launches but you see only a black screen, which you need to exit by typing blindly “exit”. Just FYI, I'm experiencing a similar issue with MeeGo Handheld for N900, I can only see the commands/output when the window is 'zoomed out' in the task switcher. I found a workaround for this somewhat accidentally. Start xterm and blindly start another xterm from it (i.e. type xterm followed by return). Now put the (first) xterm into the switcher by tapping in the upper left corner. Once in the switcher, tap on the window of the xterm to bring it back, and voila, you have a prompt and the xterm command you just issued. Press ctrl-z to stop the (second) xterm and there you go. I'm sure there are other way to accomplish this, but this is the one I stumbled on. I think the underlying reason is a bug in the compositor, which for some reason does not manifest itself when there are more windows. -- Pertti ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Blank xterm
Here's the relevant bug to follow: http://bugs.meego.com/show_bug.cgi?id=3551 -- Pertti ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Review board for MeeGo
Last time I checked there was some alpha/beta version that allowed you to monitor (or link) your repos in a git server outside (e.g. Gitorious). Need to check if that made it to some release. -- Stefano Sent from N900 - Messaggio originale - Reviewing the code sent via emails is quite a tedious task and sometimes error prone. Review board (http://www.reviewboard.org/) presents a very nice interface for code review and responses. Could we have review board installed at MeeGo? Something like reviewboard.meego.com ? I support Review board because, well, I think it's an excellent too for what it does - reviews patches. The daunting task is to upload the diffs there. It seem recently Review board added a command line tool to nicely integrate with your local Git repo and send the patch to Review board: http://www.reviewboard.org/downloads/ RBTools 0.2 However, last time I tried that it didn't work. Some required Python module was not available. Maybe someone could take a look at that and tell us if (s)he has more luck with that. Would be really nice to have Reviewboard but without the upload hassle. -- Johan ___ 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
