Iain Curtain wrote:
> I've just noticed an issue in 2.0.0.8 where the right click or java
> menus quickly show then disappear.
>
> I didn't see this issue in 2.0.0.7.
>
> I see the same issue on x86 and sparc versions.
>
> ___
> desktop-discuss mailing li
Dave Lin wrote:
>>
> It should go to the version at /usr/lib, can you run the following
> commands and send me the output?
> ls -l /usr/lib/libgthread-2.0.so.0
> pkgchk -lp /usr/lib/libgthread-2.0.so.0
>
ultra20-henry% ls -l /usr/lib/libgthread-2.0.so.0
lrwxrwxrwx 1 root root
This may extend beyond the scope of pkgbuild, but two things on my wish
list are:
- Something which uses spec files to pull the source code directly into
the NetBeans so that CBE could be run from within this IDE. This would
require some help from the netbeans team.
- A clear and verifiable w
G?rard Henry wrote:
> hello all,
> i got this error:
> > /usr/local/firefox-2.0.0.8/firefox
> ld.so.1: firefox-bin: fatal: libgcc_s.so.1: open failed: No such file or
> directory
> ld.so.1: firefox-bin: fatal: libiconv.so.2: open failed: No such file or
> directory
> ld.so.1: firefox-bin: fatal:
> Dennis Clarke wrote:
>> When you say "no" do you mean that the name "Java Desktop System" is a
>> permanent product name?
> AFAIK it is.
I've subsequently corrected by my colleagues.
Recently the login menu changed the available sessions from "Java
Desktop System" to "GNOME".
So, for the momen
Danek Duvall wrote:
> On Wed, Oct 24, 2007 at 01:28:25PM +0200, Lukas Rovensky wrote:
>
>> One more question from the maintenance point of view. The pkg(1) makes
>> possible to freeze a package at a specified version to stop update flows.
>> Currently this is decided by the user to use this co
Dennis Clarke wrote:
>>> BTW are you dropping the JDS moniker soon?
>> No. We need to distinguish JDS builds from Nevada builds hence "JDS Nevada"
>> instead of just "Nevada"
>>
>
> { just a question .. so don't shoot me }
> When you say "no" do you mean that the name "Java Desktop System" is a
>
Sebastien Roy wrote:
> Wasn't it included in Nevada for a few builds, then removed? I seem to
> remember something like this happening.
Could have been. I don't have long term memory ;)
>> What does the following tell you?
>> $ pkginfo -l SUNWgnome-screensaver
>
> PKGINST: SUNWgnome-screen
Hi,
is any plan (roadmap) for updated CBE (latets 1.6.0). In SXDE are some
of those tools updated and included directly in build now (ie. flex,
bison ...).
Luc
--
Lukas Oboril
When dealing with people, let us remember we are not dealing with
creatures of logic. We are dealing with creatures of
I've just noticed an issue in 2.0.0.8 where the right click or java
menus quickly show then disappear.
I didn't see this issue in 2.0.0.7.
I see the same issue on x86 and sparc versions.
yes i was getting confused . . . . too many numbers
BTW are you dropping the JDS moniker soon?
On Thu, 2007-10-25 at 02:43 -0700, Damien Carbery wrote:
> > vermillion b75 = gnome 2.20 (which goes into nevada
> > b76)
> >
> > nevada b75 = gnome 2.18
> Unfortunately you are wrong for both statem
Iain Curtain wrote:
> vermillion b75 = gnome 2.20 (which goes into nevada b76)
>
> nevada b75 = gnome 2.18
>
Iain, your information above is not accurate.
Nevada b75 = Vermillion b75 = GNOME 2.20
Just as Laca has mentioned :)
-Ghee
> Regards
>
> Iain
>
> On Wed, 2007-10-24 at 08:20 -0700, R
Hi, Darren:
Thank you for the pointers. DBus is online; HAL is in maintenance. ZFS
is OK.
And svcadm enable hal doesn't work, nor does svcadm refresh hal.
The log isn't very helpful - maybe the config file is corrupt, but its
location is not mentioned, nor is its name.
If I can re-install part
>> BTW are you dropping the JDS moniker soon?
> No. We need to distinguish JDS builds from Nevada builds hence "JDS Nevada"
> instead of just "Nevada"
>
{ just a question .. so don't shoot me }
When you say "no" do you mean that the name "Java Desktop System" is a
permanent product name?
Dennis
hello all,
i got this error:
> /usr/local/firefox-2.0.0.8/firefox
ld.so.1: firefox-bin: fatal: libgcc_s.so.1: open failed: No such file or
directory
ld.so.1: firefox-bin: fatal: libiconv.so.2: open failed: No such file or
directory
ld.so.1: firefox-bin: fatal: libgcc_s.so.1: open failed: No such
Damien Carbery wrote:
>> The responsible files are:
>>
>> /usr/share/applications/screensaver-properties.desktop
>> /usr/share/applications/gnome-screensaver-preferences.
>> desktop
>>
>> The first comes from SUNWxwsvr, and the second from
>> SUNWgnome-screensaver. There is no
>> SUNWgnome-screen
On Thu, Oct 25, 2007 at 04:17:18PM +0200, Lukas Rovensky wrote:
> You are right, I asked about something different and maybe I was just
> thinking too much the 'patch way'. The scenario I had in mind is like the
> following -- a customer has a problem, a fix is implemented and needs to be
> ve
Hi Sharon,
In the first two cases (g-v-m and ospm-applet) it would appear that either (or
both) HAL and D-Bus system services are not running, check using:
svcs hal dbus
Both should be in the "online" state. If they are offline enable them using:
svcs enable dbus
svcs en
> So... is JDS Nevada build 76 in SXCE b75?? I think
> that is a more fair question. I'm using SXCE b74 +
> JDS Nevada build 76 and didn't want to go back in JDS
> versions!!
No, JDS Nevada build 76 is NOT in SXCE b75.
JDS Nevada build 75 IS in SXCE b75 (not the matching '75')
As I said in my rep
So... is JDS Nevada build 76 in SXCE b75?? I think that is a more fair
question. I'm using SXCE b74 + JDS Nevada build 76 and didn't want to go back
in JDS versions!!
~ Ken
This message posted from opensolaris.org
> The responsible files are:
>
> /usr/share/applications/screensaver-properties.desktop
> /usr/share/applications/gnome-screensaver-preferences.
> desktop
>
> The first comes from SUNWxwsvr, and the second from
> SUNWgnome-screensaver. There is no
> SUNWgnome-screensaver in the latest
> Nevada
> vermillion b75 = gnome 2.20 (which goes into nevada
> b76)
>
> nevada b75 = gnome 2.18
Unfortunately you are wrong for both statements (but I can understand the
confusion wrt nevada b75).
The build numbers, for both JDS Nevada and JDS Vermillion builds, always
corresponds to the target Nevada
On 24 Oct 2007, at 17:05, Sebastien Roy wrote:
> The first comes from SUNWxwsvr, and the second from
> SUNWgnome-screensaver. There is no SUNWgnome-screensaver in the
> latest
> Nevada builds, so there would appear to be some upgrade bug where
> something forgets to remove it...
Yup, but in r
23 matches
Mail list logo
