Seems like there is something with GNOME config files in user home
folder, indeed.
After touching GNOME so that it saves some config, the problem disappeared.
(I have removed the Volume applet from the upper toolbar in production
server, and after that upgrade went without problems; Seems like
Are you saying that after updating to a new OI151a9 BE, you removed the
volume applet from the toolbar while logged in under an OI151a7 BE, and
then you booted to OI151a9.
Whereupon everything worked perfectly after logging in under OI151a9???
On 2014-02-20 19:32, Dmitry Kozhinov wrote:
Seems
Not exactly. I have removed the volume applet in 151a7 even before
upgrading to 191a9. Not sure that this is why the upgrade went
surprisingly well (on a production server).
However when i tried to reproduce the problem in virtualbox, seemed like
the following helped:
- Updated to 151a9;
Hi Milan,
Is this considered a next release preview?
pkg set-publisher-ghttp://pkg.opensolaris.cz:1/
--search-before=openindiana.org jds.openindiana.org
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
Hi,
On pá, 2014-02-21 at 02:12 +0600, Dmitry Kozhinov wrote:
Hi Milan,
Is this considered a next release preview?
pkg set-publisher-ghttp://pkg.opensolaris.cz:1/
--search-before=openindiana.org jds.openindiana.org
jds.o.o is testing repo of bits which will be included in the
Not to blame anyone, but IMO every next OI release becomes less stable
than previous...
The latest release which works stable for me is 151a7. 151a8 also
worked, though I could not configure network interface using GUI tool in
it (after disabling nwam and enabling default).
Then 151a9 was
This is basically my7 experience, too.
And noone seems to have any idea about why these Gnome problems ACTUALLY
occur.
On 2014-02-19 15:09, Dmitry Kozhinov wrote:
Not to blame anyone, but IMO every next OI release becomes less stable
than previous...
The latest release which works stable
On 19/02/2014 15:09, Dmitry Kozhinov wrote:
.
There was an advice to reinstall gvfs. Tried in a test virtualbox setup.
This worked in reverse! In /virtualbox/, 151a7 /successfully/ upgraded
to 151a9. Though in vbox the upgrade went successfully, I have tried if
reinstalling gvfs is safe
Le 2014/02/19 16:09 +0100, Hans J. Albertsson a écrit:
This is basically my7 experience, too.
And noone seems to have any idea about why these Gnome problems ACTUALLY
occur.
GNOME has always been a little picky on upgrades, that's why there is a
gnome-cleanup tool in Solaris, and I believe,
: Hans J. Albertsson [mailto:hans.j.alberts...@branneriet.se]
Sent: Wed 2014-02-19 09:44
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] How do I upgrade from 151a7 to 151a9 ?
This is basically my7 experience, too.
And no one seems to have any idea about why these Gnome
Hi,
could you describe your system configuration? What is in your
~/.xsession-errors ?
If you do pkg verify then is your system OK?
If you check output of pkg list, are all your packages on the latest
versions? It means all components from system repository are on versions
ending with
Milan,
I've so far NOT added your jds repo to my config; I can't make head or
tails of how to do that, please elucidate!
My publishers are currently set up as:
PUBLISHER TYPE STATUS URI
openindiana.orgorigin online
Hi,
pkg set-publisher --non-sticky openindiana.org
pkg set-publisher-g http://pkg.opensolaris.cz:1/
--search-before=openindiana.org jds.openindiana.org
pkg set-publisher --non-sticky sfe
pkg set-publisher --non-sticky sfe-encumbered
Best regards,
Milan
On st, 2014-02-19 at 20:55 +0100,
13 matches
Mail list logo
