Hello,
Do you know whether the native MySQL connector works under LO 4.0.4?
If it does I will try THAT release, otherwise I will revert to 3.6.2 -
which works just fine.
Regards
H
On Sun, 21 Jul 2013 11:06:35 +0200, sun shine <phaedrusv@gmail.com> wrote:
On 21/07/13 09:34, Heinrich Stoellinger wrote:
Hello,
The system on which I am trying to get LO 4.1-RC3 to run is:
Linux Debian Wheezy with KDE 4.10, latest software levels.
I first removed LO 3.6.2 using "apt-get remove libreoffice*" and then
installed 4.1-RC3 using "dpkg- i *deb" from within all three
directories in
the correct sequence.
The installation went smoothly - no hick-ups!
Now I find LO 4.1 within the programme start menu of KDE (under office
applications). To be precise - everything is there (base, writer,
impress, etc.)
except the icon for LibreOffice itself (like it used to be under 3.6).
When I now try to start Writer, nothing at all happens. The same is
true when
trying to start the other components...
Any help is appreciated.
Regards from sunny and hot Salzburg
H. Stoellinger
Same here Heinrich - which is precisely the same problem I experienced
when I tried installing 4.1 about a month ago. This is why I thought a
desktop-integration directory was still required. The current
installation does not support Gnome (or related) menus, does not seem to
trigger any application to launch.
The read me's and installation documents still refer to a separate
desktop integration command, and if one is to use the installation file,
there is no clear indication of how to do so.
I'm happy enough to beta test, but would like to know how to install the
application to get it to start in the first place.
Anyone out there who has successfully gotten the 4.1 to install and
start on a Debian type system? I'm running Mint 14, and at this point in
time am stymied, so I'm reverting back to 4.0.4 which seems to be pretty
stable and installs and works as one has come to expect of LibO.
On Sat, 20 Jul 2013 20:22:08 +0200, sun shine <phaedrusv@gmail.com>
wrote:
On 20/07/13 19:06, Mirosław Zalewski wrote:
On 20/07/2013 at 19:51, "Kracked_P_P---webmaster"
<webmaster@krackedpress.com>
wrote:
So we no longer have to do a separate install command for
installing the
desktop menus? So one "sudo dpkg -i *.deb" is all we need?
Yes, this is how it is supposed to work.
(There are some bugs in rc3 that causes package conflicts with
earlier version
of LO, so running this command might run you into trouble.)
On the other hand: if you are like me and you keep different LO
versions
installed for testing purposes, then you must take extra care to not
install
desktop-menus and not pollute your working environment with
unnecessary menu
entries.
But since this is not use-case for most of users, I believe change
is for
good.
In which case the installation notes for the 4.1 for *.deb need to be
updated since they still give the two separate commands, the second
suggesting cd to the desktop-integration directory before issuing the
second sudo dpkg -i *.deb command.
Cheers
--
Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Re: [libreoffice-users] desktop-integration · Petr Mladek
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.