Using old IVI home on MeeGo 1.2.0 and uxlaunch keeps getting called

[Foster, Susan B]

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

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?

Susan Foster
Software Platform Applications Engineer
Automotive Solutions Division (ASD)
Embedded and Communications Group (ECG)
Intel Corporation

Email: susan.b.foster-***@public.gmane.org
Voice: [phone]

[Jimmy Huang]

I have no problems brining up the old ivihome using your steps, but I am
running on a Russellville with a
meego-ivi-ia32-1.2.0.90.6.20110701.83.img.

Jimmy

Post by Foster, Susan B
Hi,
#zypper install ivihome
Modify uxlaunch
#vi /etc/sysconfig/uxlaunch

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 ~
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?
Susan Foster
Software Platform Applications Engineer
Automotive Solutions Division (ASD)
Embedded and Communications Group (ECG)
Intel Corporation
Voice: [phone]
_______________________________________________
MeeGo-ivi mailing list
http://lists.meego.com/listinfo/meego-ivi

[Kok, Auke-jan H]

On Thu, Jul 14, 2011 at 2:21 PM, Foster, Susan B

Post by Foster, Susan B
Hi,
#zypper install ivihome
Modify uxlaunch
#vi /etc/sysconfig/uxlaunch

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 ~
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

[Alison Chaiken]

I'm booting Tablet UX on ExoPC to runlevel 3, chroot'ing to IVI and
starting uxlaunch from a shell. If I start uxlaunch in background,
I can change among vt's the usual ways. If I start it in foreground,
I cannot.

Post by Foster, Susan B
Localhost klogd: [ 98.142230] Process uxlaunch(pid: 969, ti=f1448000 task=f149ee30 task.ti=f1448000)

I get these messages, but only infrequently. I haven't bothered to
look into them yet, as most things seem to be working. I have some
bugs I will report later; I am on a business trip.

Post by Foster, Susan B
When I look at the processes, sure enough there are LOTS of uxlaunch processes.

uxlaunch is respawned if you kill it, so doing so may result in lots
of zombie processes. What does "ps axl | grep uxlaunch" say? Are
those processes all running? What pids do your console messages
have?

Main problems I notice in my current environment are flickering of
backlight and periodic need to unwedge pulseaudio. WiFi works,
nobdy from repos runs, haven't tried bluetooth yet. Camera and HDMI
out don't work, but the former doesn't work on the Tablet UX either,
and the later doesn't even work with Windows with the one monitor I
tried.

[Foster, Susan B]

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: meego-ivi-bounces-***@public.gmane.org [mailto:meego-ivi-bounces-VVXm0OgCXj2zQB+***@public.gmane.orggo.com] On Behalf Of Alison Chaiken
Sent: Friday, July 15, 2011 3:51 AM
To: meego-ivi-***@public.gmane.org
Subject: Re: [MeeGo-ivi] Using old IVI home on MeeGo 1.2.0 and uxlaunch keeps getting called
I'm booting Tablet UX on ExoPC to runlevel 3, chroot'ing to IVI and
starting uxlaunch from a shell. If I start uxlaunch in background,
I can change among vt's the usual ways. If I start it in foreground,
I cannot.

Post by Foster, Susan B
Localhost klogd: [ 98.142230] Process uxlaunch(pid: 969, ti=f1448000
task=f149ee30 task.ti=f1448000)

I get these messages, but only infrequently. I haven't bothered to
look into them yet, as most things seem to be working. I have some
bugs I will report later; I am on a business trip.

Post by Foster, Susan B
When I look at the processes, sure enough there are LOTS of uxlaunch processes.

uxlaunch is respawned if you kill it, so doing so may result in lots
of zombie processes. What does "ps axl | grep uxlaunch" say? Are
those processes all running? What pids do your console messages
have?

Main problems I notice in my current environment are flickering of
backlight and periodic need to unwedge pulseaudio. WiFi works,
nobdy from repos runs, haven't tried bluetooth yet. Camera and HDMI
out don't work, but the former doesn't work on the Tablet UX either, and the later doesn't even work with Windows with the one monitor I tried.

--
Alison Chaiken
[phone]  (cell)
             http://www.exerciseforthereader.org/
Spend much time at the cutting edge and you're liable to get cut.

[Jimmy Huang]

Just disable meego-ux-daemon from the /etc/xdg/autostart directory, and
you should have just ivihome without seeing the new UX. ivihome is
deprecated and no longer supported.

Jimmy

Post by Foster, Susan B
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-----
Sent: Friday, July 15, 2011 3:51 AM
Subject: Re: [MeeGo-ivi] Using old IVI home on MeeGo 1.2.0 and uxlaunch keeps getting called
I'm booting Tablet UX on ExoPC to runlevel 3, chroot'ing to IVI and
starting uxlaunch from a shell. If I start uxlaunch in background,
I can change among vt's the usual ways. If I start it in foreground,
I cannot.

Post by Foster, Susan B
Localhost klogd: [ 98.142230] Process uxlaunch(pid: 969, ti=f1448000
task=f149ee30 task.ti=f1448000)

I get these messages, but only infrequently. I haven't bothered to
look into them yet, as most things seem to be working. I have some
bugs I will report later; I am on a business trip.

Post by Foster, Susan B
When I look at the processes, sure enough there are LOTS of uxlaunch processes.

uxlaunch is respawned if you kill it, so doing so may result in lots
of zombie processes. What does "ps axl | grep uxlaunch" say? Are
those processes all running? What pids do your console messages
have?
Main problems I notice in my current environment are flickering of
backlight and periodic need to unwedge pulseaudio. WiFi works,
nobdy from repos runs, haven't tried bluetooth yet. Camera and HDMI
out don't work, but the former doesn't work on the Tablet UX either, and the later doesn't even work with Windows with the one monitor I tried.
--
Alison Chaiken
[phone] (cell)
http://www.exerciseforthereader.org/
Spend much time at the cutting edge and you're liable to get cut.
_______________________________________________
MeeGo-ivi mailing list
http://lists.meego.com/listinfo/meego-ivi
_______________________________________________
MeeGo-ivi mailing list
http://lists.meego.com/listinfo/meego-ivi

[Foster, Susan B]

I did disable meego-ux-daemon from /etc/xdg/autostart. I moved it right out of the directory. I'll send you pictures, Jimmy (they were too big to post to the list)

-----Original Message-----
From: Jimmy Huang [mailto:jimmy.huang-VuQAYsv1563Yd54FQh9/***@public.gmane.org]
Sent: Friday, July 15, 2011 12:02 PM
To: Foster, Susan B
Cc: Alison Chaiken; meego-ivi-***@public.gmane.org
Subject: Re: [MeeGo-ivi] Using old IVI home on MeeGo 1.2.0 and uxlaunch keeps getting called

Just disable meego-ux-daemon from the /etc/xdg/autostart directory, and you should have just ivihome without seeing the new UX. ivihome is deprecated and no longer supported.

Jimmy

Post by Foster, Susan B
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-----
Sent: Friday, July 15, 2011 3:51 AM
Subject: Re: [MeeGo-ivi] Using old IVI home on MeeGo 1.2.0 and
uxlaunch keeps getting called
I'm booting Tablet UX on ExoPC to runlevel 3, chroot'ing to IVI and
starting uxlaunch from a shell. If I start uxlaunch in background,
I can change among vt's the usual ways. If I start it in foreground,
I cannot.

Post by Foster, Susan B
Localhost klogd: [ 98.142230] Process uxlaunch(pid: 969, ti=f1448000
task=f149ee30 task.ti=f1448000)

I get these messages, but only infrequently. I haven't bothered to
look into them yet, as most things seem to be working. I have some
bugs I will report later; I am on a business trip.

Post by Foster, Susan B
When I look at the processes, sure enough there are LOTS of uxlaunch processes.

uxlaunch is respawned if you kill it, so doing so may result in lots
of zombie processes. What does "ps axl | grep uxlaunch" say? Are
those processes all running? What pids do your console messages
have?
Main problems I notice in my current environment are flickering of
backlight and periodic need to unwedge pulseaudio. WiFi works,
nobdy from repos runs, haven't tried bluetooth yet. Camera and HDMI
out don't work, but the former doesn't work on the Tablet UX either, and the later doesn't even work with Windows with the one monitor I tried.
--
Alison Chaiken
[phone] (cell)
http://www.exerciseforthereader.org/
Spend much time at the cutting edge and you're liable to get cut.
_______________________________________________
MeeGo-ivi mailing list
http://lists.meego.com/listinfo/meego-ivi
_______________________________________________
MeeGo-ivi mailing list
http://lists.meego.com/listinfo/meego-ivi

[Alison Chaiken]

Post by Foster, Susan B
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

Note that in any case, a system can have only one /dev/console.
Procedure below gets access to /dev/tty? where ? > 0.

Here's how I get a second (and third and fourth) virtual terminal
with 1.2 Tablet UX version of uxlaunch:

1. Edit /etc/syslinux/syslinux.conf (or similar) and set bootloader
timeout to, say, 10 seconds. Turn off splash screen (delete
"quiet" or "hiddenmenu").

2. When you reboot, hit tab when bootloader appears in order to get a prompt.

3. Type a space at the end of the line and then "3" (no quotes) to get
an X-less console boot. (What are we going to do to get text-mode
boot with systemd? Not sure myself.)

4. At prompt, login. You should be able to change among virtual
terminals with Ctrl-Alt-F? mechanism, not to mention "chvt." If you
still don't have multiple virtual terminals, try "openvt /bin/bash".

5. On one virtual terminal, type "uxlaunch&" Starting uxlaunch in
background preserves access to other vt's with usual mechanisms.

HTH.
-- Alison