This is the result of the changes to roles in this build. I will file
this bug.
-Sanjay
P-O Yliniemi wrote:
After upgrading to b130, the auto-snapshot services are not able to
start anymore.
Starting the Gnome Time Slider Manager application, I get the
following message:
On 12/31/09 01:49 AM, solarg wrote:
What am i missing?
"Software Installation" isn't yet sufficient to give pkg all the
permissions it needs to install. You'll need "Primary Administrator" if
you want to install packages to the root filesystem.
Support for the "Software Installation" profi
solarg writes:
> hello all,
> i have this problem:
> ERROR: pkg refresh failed when installing package:
> pkg: Could not operate on /var/pkg/catalog/localhost/tmpl4Jhn7
> because of insufficient permissions. Please try the command again
> using pfexec
> or otherwise increase your privileges.
>
>
hello all,
i have this problem:
ERROR: pkg refresh failed when installing package:
pkg: Could not operate on /var/pkg/catalog/localhost/tmpl4Jhn7
because of insufficient permissions. Please try the command again using
pfexec
or otherwise increase your privileges.
the user has the profile:
# pr
After upgrading to b130, the auto-snapshot services are not able to
start anymore.
Starting the Gnome Time Slider Manager application, I get the following
message:
Snapshot manager service dependency error
The snapshot manager service has been placed offline due to a dependenc
On 12/30/09 12:53 AM, John M. Martin wrote:
| my trouble is different. After upgrading from 129 to 130, package
| NVDAgraphics has disappeared!
| after reinstalling it, it works...
Is this the NVDAgraphics IPS or SYSV package?
The contents of the SYSV NVDAgraphics package, in particular
/usr/X
| my trouble is different. After upgrading from 129 to 130, package
| NVDAgraphics has disappeared!
| after reinstalling it, it works...
Is this the NVDAgraphics IPS or SYSV package?
The contents of the SYSV NVDAgraphics package, in particular
/usr/X11/lib/modules/drivers[/amd64]/nvdia_drv.so wil
On 12/29/09 09:37 AM, ken mays wrote:
Paul,
Hoping for the snv_131 fixes and Nvidia 190.53 integration update
which will help fix more things.
Ken
Thanks Ken, I'm just waiting patiently for b131 to come out and see how
everything unfolds. I was reading on the 195.30 driver, any plans
> I takes a little time to get used to, but I must
> admit I've come to like
> the new login interface already. It's nice to have
> the options in the
> bar. It works fine and looks OK.
Except for some reason a clean install of build 130 doesn't list all the
languages that it should - no United K
Paul,
Hoping for the snv_131 fixes and Nvidia 190.53 integration update
which will help fix more things.
Ken
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Thank you, Fuyuki
It does fix the problem.
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Paul Gress wrote:
> Hopefully this can clue somebody what the real problem is. If I try to
> analyze whats happening, my computing platform is running 64 bit and
> libGL.so.1 is 32 bit, maybe there lies the problem.
On Solaris, 32-bit libraries are in /usr/lib and 64-bit in /usr/lib/64
(which lin
Jürgen Keil wrote:
> I think the new Xorg is recursively scanning the extensions
> directory and loads all modules that it finds. Maybe it scans
> the mesa directory before the "GL" directory?
It shouldn't load all modules it finds, but glx is one of the
default ones - and I've noticed the recursi
I heard JDK1.7 utilizes fonts.conf instead of the traditional Java's fontconfig
properties file. So, that's why you can see CJK chars on osol_130, I guess.
Fuyuki
Evereasy wrote:
It will display Chinese Characters correctly, if I use openjdk 1.7.0-ea -
r...@x-wing:/ # cd /usr
r...@x-wing:/usr
Evereasy wrote:
After updated to b130, Java Application/NetBeans can not display Chinese
Characters correctly.
Please kindly help if there is any work around to fix this problem.
I'm not checking actual osol_130 yet, but the same problem should also
happen with Japanese and Korean characters.
On 12/26/09 04:29 PM, Paul Gress wrote:
On 12/26/09 04:07 PM, Paul Gress wrote:
___
OK, tried what you suggested. I could start compiz but with
Pro-Engineer, the same exact results as I previously got.
bash-4.0$ /Disk1/Binaries/Pro-Engineer/WF5/
On 12/26/09 04:07 PM, Paul Gress wrote:
___
OK, tried what you suggested. I could start compiz but with
Pro-Engineer, the same exact results as I previously got.
bash-4.0$ /Disk1/Binaries/Pro-Engineer/WF5/bin/proe1 &
[1] 2806
bash-4.0$ ld.so.1: p
On 12/26/09 03:51 PM, Paul Gress wrote:
directory and loads all modules that it finds. Maybe it scans
the mesa directory before the "GL" directory?
Maybe you can workaround the problem by hiding the
mesa subdirectory in /usr/lib/xorg/modules/extensions,
e.g. "tar cf mesa.tar mesa" and "rm -rf me
On 12/26/09 03:22 PM, Jürgen Keil wrote:
That appears to be similar to defect 13131
"gnome desktop does not start, shows white screen; constype fails to open
/dev/fb"
http://defect.opensolaris.org/bz/show_bug.cgi?id=13131
Followed instructions for workaround # 2,
Workaround #2 (fr
> > That appears to be similar to defect 13131
> > "gnome desktop does not start, shows white screen; constype fails to open
> > /dev/fb"
> > http://defect.opensolaris.org/bz/show_bug.cgi?id=13131
> >
>
> Followed instructions for workaround # 2,
>
>
> Workaround #2 (from 6822628):
> # sv
On 12/26/09 03:52 AM, Jürgen Keil wrote:
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/mesa/amd64/libglx.so
(II) Module glx: vendor="X.Org Foundation"
...
(**) Dec 25 14:21:52 NVIDIA(0): Enabling RENDER acceleration
(EE) Dec 25 14:21:52 NVIDIA(0): Failed to init
Any ideas how to change the login theme, now that gdmsetup is no more?
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
hello all,
my trouble is different. After upgrading from 129 to 130, package
NVDAgraphics has disappeared!
after reinstalling it, it works...
very strange,
PS: the "Switch User" isn't functionnal at all, a very bad thing, and
this is a very bad idea to offer it as a possible choice
gerard
It will display Chinese Characters correctly, if I use openjdk 1.7.0-ea -
r...@x-wing:/ # cd /usr
r...@x-wing:/usr # rm java
r...@x-wing:/usr # ln -s jdk/instances/openjdk1.7.0 java
r...@x-wing:/usr # java -version
openjdk version "1.7.0-ea"
OpenJDK Runtime Environment (build 1.7.0-ea-b59)
OpenJDK
After updated to b130, Java Application/NetBeans can not display Chinese
Characters correctly.
Please kindly help if there is any work around to fix this problem.
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-disc
I takes a little time to get used to, but I must admit I've come to like
the new login interface already. It's nice to have the options in the
bar. It works fine and looks OK.
--
Dick Hoogendijk -- PGP/GnuPG key: 01D2433D
+ http://nagual.nl/ | SunOS 10u7 5/09 | OpenSolaris 2010.02 b130
+ All that
On Fri, 2009-12-25 at 15:30 -0500, Paul Gress wrote:
> On 12/25/09 03:17 PM, Paul Gress wrote:
> >>
> >
> > Thanks for the reply. Yes I restarted the X server in the form of a
> > reboot. I think it goes a little deeper, as my Xorg.0.log shows it's
> > still loading the mesa library. I just po
> (II) LoadModule: "glx"
> (II) Loading /usr/lib/xorg/modules/extensions/mesa/amd64/libglx.so
> (II) Module glx: vendor="X.Org Foundation"
...
> (**) Dec 25 14:21:52 NVIDIA(0): Enabling RENDER acceleration
> (EE) Dec 25 14:21:52 NVIDIA(0): Failed to initialize the GLX module; please
> check in yo
On 12/25/09 03:45 PM, Christian Thalinger wrote:
On Fri, 2009-12-25 at 13:30 -0500, Paul Gress wrote:
On 12/25/09 05:38 AM, dick hoogendijk wrote:
pfexec pkg install SUNWipkg -> 750 new pkgs / 347 MB
Is this normal if I want to renew one(1) pkg?
This is more like an image-uodate whi
On Fri, 2009-12-25 at 13:30 -0500, Paul Gress wrote:
> On 12/25/09 05:38 AM, dick hoogendijk wrote:
> > pfexec pkg install SUNWipkg -> 750 new pkgs / 347 MB
> > Is this normal if I want to renew one(1) pkg?
> > This is more like an image-uodate which was refused because an
> > out-of-date SUNWipkg
On 12/25/09 03:17 PM, Paul Gress wrote:
Thanks for the reply. Yes I restarted the X server in the form of a
reboot. I think it goes a little deeper, as my Xorg.0.log shows it's
still loading the mesa library. I just posted the output of
Xorg.0.log minutes before this one.
__
On 12/25/09 02:53 PM, John Beck wrote:
Paul> I've just finished upgrading to b130 and had some small issues which I
Paul> resolved. But there is one issue I cannot resolve.
Paul> It is labeled:
Paul> 6912450 OpenGL switcher broken for NVIDIA graphics in b130
Paul> http://bugs.opensolaris.
Paul> I've just finished upgrading to b130 and had some small issues which I
Paul> resolved. But there is one issue I cannot resolve.
Paul> It is labeled:
Paul> 6912450 OpenGL switcher broken for NVIDIA graphics in b130
Paul> http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6912450
Pa
I've just finished upgrading to b130 and had some small issues which I
resolved. But there is one issue I cannot resolve.
It is labeled:
6912450 OpenGL switcher broken for NVIDIA graphics in b130
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6912450
I've followed all the instruct
> Try the following command:
>
> pkg contents -Ho pkg.name,action.raw -t depend | grep fmri=entire@ | cut -f1
>
> If you get output, you need to remove these packages (from contrib) to
> upgrade to b130.
I knew that bug and I was almost sure I'd removed DosBox last time (from
contrib). It was s
On 12/25/09 05:38 AM, dick hoogendijk wrote:
pfexec pkg install SUNWipkg -> 750 new pkgs / 347 MB
Is this normal if I want to renew one(1) pkg?
This is more like an image-uodate which was refused because an
out-of-date SUNWipkg (from b129)
Sounds like your getting the error:
http://defect
pfexec pkg install SUNWipkg -> 750 new pkgs / 347 MB
Is this normal if I want to renew one(1) pkg?
This is more like an image-uodate which was refused because an
out-of-date SUNWipkg (from b129)
___
indiana-discuss mailing list
indiana-discuss@opensolari
37 matches
Mail list logo
