On 31 Mar 2010, at 03:58, halton wrote:

> On Tue, 2010-03-30 at 02:12 -0700, Lee Essen wrote:
>> Hi,
>> 
>> I'm using snv_134 and I've managed to get the VNC 'display' working nicely 
>> within ConsoleKit, but I have noticed that if Xvnc dies (which it does if 
>> you hit the shift-key bug) then it doesn't get restarted.
>> 
>> If I disable and then re-enable consolekit then it starts back up again.
>> 
>> I can't see anything in any logs that might help.
>> 
>> Is this a bug or am I doing something wrong?
> Could you let me know how you start Xvnc?
> So far, there are two ways to do that.
> 1) Add a VNC seat as described in example 4 of console-kit-daemon(1m).
> 2) Enable XDMCP in /etc/gdm/custom.conf and xvnc-inetd service

I just edited the existing LocalVNC.device to include more sensible settings 
(no composite, no query, and a password file) and then created a new seat as 
per the man page. I also disabled the 00-primary.seat (using hidden) as I don't 
need a graphical console.

In the LocalVNC.display I now have:

Exec=/usr/bin/Xvnc $display -auth $auth -PasswordFile /etc/vnc/passwd -rfbport 
8080 -extension Composite

But I also tried it with the default setting and it has exactly the same 
behaviour.

[Seat Entry]
Version=1.0
Name=VNC Seat
Description=start one VNC display on :64
Devices=
Sessions=LocalVNC;

> And could you add "Enable=true" under section [debug] in
> file /etc/gdm/custom.conf. Restart gdm and let me know any useful
> message in /var/adm/message.

This will probably have to wait for the weekend, but it's a standard config 
otherwise, very recent clean snv_134 build .. so I imagine this would be easily 
reproducible.


>> 
>> BTW -- with a completely standard snv_134 build Xvnc doesn't seem to work 
>> with console kit because of compiz ... I have added "-extension Composite" 
>> to get everything working.
> This is know issue,
> http://defect.opensolaris.org/bz/show_bug.cgi?id=9891
> 
> Cheers,
> Halton.
> 
> 

Cheers,

Lee.
_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to