Hi!
I'm not sure if I do it correctly, but I can't get Xvnc to work at build 117.
When VNC session is opened and the gnome window is asking me for user and
password, the hole window turns into white screen after that I have logged in.
--
This message posted from opensolaris.org
I can't say with certainty, but from my own experience, it is very
tolerant of hardware changes.
Are you saying that you can boot from the same root filesystem as you used
in the other system?
My experience is different; you can boot failsafe but you need to
rebuild /etc/path_to_inst and
I can't say with certainty, but from my own experience, it is very
tolerant of hardware changes.
Are you saying that you can boot from the same root filesystem as you used
in the other system?
With zfs boot / root it sometimes works: when the boot / root disk
can be found by devid. In
The hostname.* issue can be avoided by using nwam
(default in OpenSolaris / Indiana).
Except that it only works in simple situations. I.e., not if you
use the system as a home server (dhcp server, multiple internet
connection) and it doesn't work with a ipfilter, etc.
As we're not talking
Thanks so much for the update and info. Yes, after the reboot my daily
notification and download went away. I am just used to the way the Ubuntu does
the update notice and then the notice that a reboot is needed. I don't think I
have noticed Ubuntu giving the the same package over and over
Hi, Pablo!
It seems that it's a problem with spanish or latinamerican layouts, and
no xorg.conf configuration file.
I had the same trouble after upgrading to snv_117, then logged into my
box from other machine, created the xorg.conf, svcadm disable gdm, and
svcadm enable gdm.
Now works!
Best
Hello, Sabina!
It seems that it's a problem with spanish or latinamerican layouts, and
no xorg.conf configuration file.
I had the same trouble after upgrading to snv_117, then logged into my
box from other machine (ssh -l your user your_ip), created the
xorg.conf, svcadm disable gdm, and svcadm
Hello!
My ssh client, after upgrading from snv_111b to snv_117 is not working
anymore, giving to me an ld.so.1 error.
Does anybody else have this error when trying to ssh a machine from your
Osol one?
Thanks, and best regards,
HeCSa.
___
It seems that you have enabled G_DEBUG,
so these critical warning caused core dump.
you can unset it .
Andrew V.Statsenko :
$ ekiga
(ekiga:9450): GConf-CRITICAL **: file gconf-value.c: line 836: assertion `value
!= NULL' failed
(ekiga:9450): GConf-CRITICAL **: file gconf-value.c: line 836:
According to gnome schedule, its 2.26.3 tarball due day is Jul 1st.
Desktop will bump to that version also.
it may be 119 or 120.
Hi,
After exploring OSOL2010.02-b117 yesterday, I noticed a weird error in my
mouse clicks and scrolling while working with the gnome panels. This was
something
casper@sun.com wrote:
I can't say with certainty, but from my own experience, it is very
tolerant of hardware changes.
Are you saying that you can boot from the same root filesystem as you used
in the other system?
Correct.
My experience is different; you can boot failsafe but you
Jürgen Keil wrote:
I can't say with certainty, but from my own experience, it is very
tolerant of hardware changes.
Are you saying that you can boot from the same root filesystem as you used
in the other system?
With zfs boot / root it sometimes works: when the boot / root disk
can be found
12 matches
Mail list logo
