LibreOffice launches unexpectedly at startup

English Install/Boot/Login
1

Good morning,
I was in version 15.3
To resolve a problem with poor display of memo fields in LibreOffice Base, I introduced the line:
export SAL_USE_VCLPLUGIN=gtk3 libreoffice
in the etc/bashrc file.
Everything worked fine…
Later I upgraded the system to 15.4. Everything went well, except that

  1. LibreOffice launches at system startup
  2. There is no longer a password request at startup (I must have done something stupid??)
  3. I can no longer find the bash file in which I put the export command…

I would like to be able to delete this accidental startup (and know where this launch is happening) and regain the login.
Sincerely
Jean Michel

2

It is unbelievable important to tell which DE is in use…

For KDE check systemsettings. Start and shutdown should be set to new/empty session. Also check autostart settings there.

YaST-> Users and Group management → Expert options->Login settings → uncheck autologin

3

DE = Desktop Environment ?
I use KDE on Opensuse 15.4 Leap

Nothing in Autostart and
DISPLAYMANAGER_AUTOLOGIN=“” in file /etc/sysconfig/displaymanager

Ok, the login works at startup, but LibreOffice still launches and the system is stuck until I exit Libre Office (Alt-f, q), then the light bulb appears, then the desktop and I can work Normally.

No idea where LibreOffice is launching…

4

System settings → Startup and shutdown → Session management → On Login → Start with an empty session

5

I had already done it. Nothing changes… :hot_face:

6

Did you try to clear the directories ~/.cache and /tmp after this?

7

Golden rule number 1:

  • Never edit ‘/etc/bash.bashrc’ – always add local changes to ‘/etc/bash.bashrc.local’ …

Next, in system scripts, always first define a shell variable and then, in the next line of the script, export the newly defined variable name …

Are you aware of the following Document Foundation Blog article dealing with VLC and LibreOffice?
<https://dev.blog.documentfoundation.org/2023/01/28/vcl-example-applications-and-tools/>

But, when I read the Document Foundation Blog article, I would say that, the definition of the shell variable using the Blog article’s definiiton, will call whatever “libreoffice” is in the user’s PATH variable – use –

 > which -a libreoffice
/usr/bin/libreoffice
 > file /usr/bin/libreoffice
/usr/bin/libreoffice: symbolic link to ../lib64/libreoffice/program/soffice
 >

to find out exactly which “libreoffice” you are calling with the existing shell variable definition statement.

I suspect that, what the Documentation Foundation folks have documented is that, if you call LibreOffice as follows –

> SAL_USE_VCLPLUGIN=gtk3 /usr/lib64/libreoffice/program/soffice

then, LibreOffice will be executed with the Gtk3 VLC Plugin.

You can also call LibreOffice as follows:

> /usr/lib64/libreoffice/program/soffice -env:SAL_USE_VCLPLUGIN=gtk3

Bottom line:

  • In ‘/etc/bash.bashrc.local’ add the following lines:
SAL_USE_VCLPLUGIN=gtk3
export SAL_USE_VCLPLUGIN
8

Not having read all:

  • check ~/,config/aurostart and /etc/xdg/autostart
  • check the systemsettings re. restoring previous sessions
9

yes. ~/.cache is clear but there are protected folders in /tmp.

10

OK, It was a big mistake I made, but since then I have placed the order
export SAL_USE_VCLPLUGIN=gtk3 in the .bashrc of my home folder.
But during the update to 15.4, the line I put in /etc/.bashrc was moved elsewhere, but I can’t find where…

11

.config/autostart is empty, and in /etc/xdg/autostart no file contains ‘libreoffice’

???
I think i did it. Tell it on a previous post…

12

I had stuck (unintentionally?) the line
SAL_USE_VCLPLUGIN=gtk3 libreoffice
in home/.profile
Sorry for the inconvenience…

13

Take a close look at this CLI line:

> SAL_USE_VCLPLUGIN=gtk3 libreoffice

Especially the attribute which follows the definition of the shell variable → “libreoffice” …

In other words, in bashrc there’s a line which first defines and exports the shell parameter “SAL_USE_VCLPLUGIN” and then, calls the executable “libreoffice” «which understands the value of the shell parameter» …

  • If you call an executable in a bashrc file then, at login that executable will begin executing and, at every subsequent execution of the bashrc file – such as opening a Terminal Window …