I went back and did a clean install of MeeGo 1.2.0. I saw the crash on the new IVI desktop. Then I modified the /etc/zypp/repo.d to point to where the update testing repo is - http://repo.meego.com/MeeGo/builds/1.2.0/1.2.0.0.5.20110709.1/ - and did a zypper update. After that I did an install of ivi home.
Good news - no more UX crashing - so that must have been the graphics bug that was fixed in the update Bad news - ivihome is now a conglomeration of the new UX and the old UX, and there is no easy way to launch a second console (which was the reason I wanted to use ivihome in the first place I don't think that it is worth filing bugs against ivihome - are they on the roadmap to be fixed? Susan. -----Original Message----- From: Kok, Auke-jan H [mailto:[email protected]] Sent: Thursday, July 14, 2011 3:44 PM To: Foster, Susan B Cc: [email protected]; [email protected] Subject: Re: [MeeGo-dev] Using old IVI home on MeeGo 1.2.0 and uxlaunch keeps getting called On Thu, Jul 14, 2011 at 2:21 PM, Foster, Susan B <[email protected]> wrote: > Hi, > > I need to be able to launch more than one console window at a time so I > reverted back to the old ivihome from the new QML UI by doing the following: > > #zypper install ivihome > > Modify uxlaunch > #vi /etc/sysconfig/uxlaunch > > Edit so that the only uncommented out lines are: >>user=meego >>session=/usr/bin/startivi > > remove the meego-ux-daemon.desktop file from /etc/xdg/autostart > directory #mv /etc/xdg/autostart/meego-ux-daemon.desktop ~ > > The problem I am getting is that with the 1.2.0 release on Crossville-OKI I > get the following line printed on console every 9 seconds: > Localhost klogd: [ 98.142230] Process uxlaunch(pid: 969, ti=f1448000 > task=f149ee30 task.ti=f1448000) > > When I look at the processes, sure enough there are LOTS of uxlaunch > processes. > > What do I need to do to disable this? uxlaunch is crashing, you need to figure out why: 1) include /var/log/uxlaunch.* 2) include /tmp/Xorg.* 3) dmesg output 4) /var/log/messages 5) /home/meego/.xsession-errors most likely it's because you modified some component, and that is misbehaving. A ~10 second interval usually suggests that Xorg is not properly functional. Did you modify the X server somehow? Auke _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
