Redhat 8
GNOME 3.32

How can I prevent a program from being automatically started in GNOME after logging in?

I tried the Tweaks extension.

Once I reboot the system the program still starts up and its listing in the Tweaks has returned.

Is there a text file I can edit as root or a path I can go to in the gconf-editor?

Thanks

Happy Friday

Steve

On 2022-01-07 07:35, Steve Mysterious wrote:

> How can I prevent a program from being automatically started in GNOME after logging in?
> Once I reboot the system the program still starts up and its listing in the Tweaks has returned.
>
What is the program you do not want to start?
Does it return to Startup Apps if you log out/in?

--
James Moe
jmm-list at sohnen-moe dot com
Think.

On 1/7/22 9:35 AM, Steve Mysterious wrote:
> Redhat 8
> GNOME 3.32
>
> How can I prevent a program from being automatically started in GNOME after logging in?

Don't use Gnome ... it sucks. :-)

On Tue, 11 Jan 2022 00:14:00 -0500, "1.AAC0832" <z24ba7.net> wrote:
>
> On 1/7/22 9:35 AM, Steve Mysterious wrote:
>> Redhat 8
>> GNOME 3.32
>> How can I prevent a program from being automatically started in
>> GNOME after logging in?
>
> Don't use Gnome ... it sucks. :-)

Tending to agree (there starts another desktop war ;-). I used Gnome
since 2008 or something. Never really bothered what's running. But now my
computer is rather old and each update of packages slows it down more. I
noticed now the program "gnome-session" at a good chunk of RAM and short
bursts of up to 50 % CPU time.

Cleaning out some files and packages I remembered I had MATE installed
next to Gnome, thought to have a look at MATE before removing it. But I
liked it right away. It's also friendlier to my aging hardware. Thus MATE
is now my default desktop.
--
Andreas

On 11/01/2022 19:28, Andreas Kohlbach wrote:
> thought to have a look at MATE before removing it. But I
> liked it right away. It's also friendlier to my aging hardware. Thus MATE
> is now my default desktop.
+1.

I went through similar evolutions, tried cinammon - all fur coat and no
knickers - and came back to MATE. Decent compromise between easy on the
eye and functional.

I occasionally try something else, but its never quite as much what I
want as MATE

--
"If you don’t read the news paper, you are un-informed. If you read the
news paper, you are mis-informed."

Mark Twain

On 2022-01-10 22:14, 1.AAC0832 wrote:

>> How can I prevent a program from being automatically started in GNOME after logging in?
> Don't use Gnome ... it sucks. :-)
>
That is singularly unhelpful for ... anyone.
No one cares about your opinion of Gnome.

--
James Moe
jmm-list at sohnen-moe dot com
Think.

On 1/11/22 5:24 PM, James Moe wrote:
> On 2022-01-10 22:14, 1.AAC0832 wrote:
>
>>> How can I prevent a program from being automatically started in GNOME after logging in?
>> Don't use Gnome ... it sucks. :-)
>>
> That is singularly unhelpful for ... anyone.
> No one cares about your opinion of Gnome.

Daresay some DO ....

It's just a BAD direction. Can't figure out why ANYONE
would install it. The cleaned-up old Gnome, MATE, isn't
nearly so awful ... but XFCE and LXDE/QT are a hell of
a lot better and even bloated KDE is still far more
sane.

I suspect the only reason GNOME still exists is because,
for some mad reason, RHEL and clones come with it by
default.

On 12/01/2022 04:05, 1.AAC0832 wrote:
> On 1/11/22 5:24 PM, James Moe wrote:
>> On 2022-01-10 22:14, 1.AAC0832 wrote:
>>
>>>> How can I prevent a program from being automatically started in
>>>> GNOME after logging in?
>>>     Don't use Gnome ... it sucks.  :-)
>>>
>>    That is singularly unhelpful for ... anyone.
>>    No one cares about your opinion of Gnome.
>
>   Daresay some DO ....
>
>   It's just a BAD direction. Can't figure out why ANYONE
>   would install it. The cleaned-up old Gnome, MATE, isn't
>   nearly so awful ... but XFCE and LXDE/QT are a hell of
>   a lot better and even bloated KDE is still far more
>   sane.
>
>   I suspect the only reason GNOME still exists is because,
>   for some mad reason, RHEL and clones come with it by
>   default.

Look , it really is simply a matter of what you want.

As I type this, into thunderbird, it matters not one jot what in fact
the underlying window manager is. Nor indeed the operating system.
People who *use* computers really don't care that much.

The only obvious factor here is that there are autohiding status and
menu bars, one of which features virtual screens so I don't need to have
two or more monitors :-)

So, looking at it, apart from the window frames, which look remarkably
like OSX, its hard to tell what the window manager or operating system
actually is.

The guy has gnome. H e wants to know how to stop programs autostarting.
There is probably a control panel item for start up menus, if that is
how it is happening, but I have MATE, not gnome, so I cant tell.

https://askubuntu.com/questions/37957/how-do-i-manage-applications-on-startup-in-gnome-3

is probably enough info for the OP

--
If I had all the money I've spent on drink...
...I'd spend it on drink.

Sir Henry (at Rawlinson's End)

On Wed, 12 Jan 2022 07:14:15 -0500, The Natural Philosopher <tnp@invalid.invalid> wrote:
> The guy has gnome. H e wants to know how to stop programs autostarting.
> There is probably a control panel item for start up menus, if that is
> how it is happening, but I have MATE, not gnome, so I cant tell.

There are many ways a program can autostart on user login. Without knowing
which distribution, desktop envrionments installed, and program that's starting
the question can not be answered.

Keep in mind that just because gnome is the current desktop environment being
used, other desktop environments may also be installed, and their autostart
functions may work in gnome. Then their's xdg, dbus, systemd, etc.

Regards, Dave Hodgins

Steve Mysterious <tinker123@gmail.com> writes:
> Redhat 8
> GNOME 3.32
>
> How can I prevent a program from being automatically started in GNOME after logging in?
>
Using MINT MATE:

On Panel is a menu item 'System':

System -> Control Centre -> Personal/Startup Applications

Find the program you don't want and uncheck it or 'remove' it.

I assume its very similar in most of the Gnome Desktops.

Jack
--
Why do meteorites always land in craters?

On 12/01/2022 17:56, David W. Hodgins wrote:
> On Wed, 12 Jan 2022 07:14:15 -0500, The Natural Philosopher
> <tnp@invalid.invalid> wrote:
>> The guy has gnome. H e wants to know how to stop programs autostarting.
>> There is probably a control panel  item for  start up menus, if that is
>> how it is happening, but I have MATE, not gnome, so I cant tell.
>
> There are many ways a program can autostart on user login. Without knowing
> which distribution, desktop envrionments installed, and program that's
> starting
> the question can not be answered.
>
> Keep in mind that just because gnome is the current desktop environment
> being
> used, other desktop environments may also be installed, and their autostart
> functions may work in gnome. Then their's xdg, dbus, systemd, etc.
>
> Regards, Dave Hodgins

However he did say 'start on login' which lets out most of te system
approaches to starting code and suggest the autostart menu

--
To ban Christmas, simply give turkeys the vote.

On Thu, 13 Jan 2022 05:16:51 -0500, The Natural Philosopher <tnp@invalid.invalid> wrote:
> However he did say 'start on login' which lets out most of te system
> approaches to starting code and suggest the autostart menu

Wrong.

$ systemctl --user status
● x3.hodgins.homeip.net
State: running
Jobs: 0 queued
Failed: 0 units
Since: Tue 2022-01-11 18:02:15 EST; 1 day 13h ago
CGroup: /user.slice/user-500.slice/user@500.service
├─redshift-gtk.service
│ ├─3535 /bin/bash /usr/local/bin/redshift-gtk
│ ├─3612 /usr/bin/python3 /usr/bin/redshift-gtk
│ └─3613 /usr/bin/redshift -v
├─pulseaudio.service
│ └─2835 /usr/bin/pulseaudio --daemonize=no --log-target=journal
├─gvfs-daemon.service
│ └─3618 /usr/libexec/gvfsd
├─init.scope
│ ├─2391 /usr/lib/systemd/systemd --user
│ └─2395 (sd-pam)
└─dbus.service
└─2865 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

$ tree -ifa .config/systemd/user/
..config/systemd/user
..config/systemd/user/default.target.wants
..config/systemd/user/default.target.wants/redshift-gtk.service -> /etc/xdg/systemd/user/redshift-gtk.service
..config/systemd/user/ethumb.service -> /dev/null

So as above, I'm using systemd user units to cause redshift-gtk to start and to
stop ethumb from running.

Also, see "man systemd-xdg-autostart-generator", and try opening a terminal
and running xdg-autostart.

Neither xdg or systemd user units involve a desktop environment's autostart, but
both start things on user login. There's also dbus that can run things on user
login.

On user login, the autostart menu is just one of several ways things can start on
user login. As I mentioned before, if multiple desktop environments are installed,
the non running desktop can still activate things from it's autostart on user login.

Without knowing which distro and package is involved, and what desktop environments
have been installed, so things can be looked at to see which methods are used, the
question cannot be answered.

Regards, Dave Hodgins

On 13/01/2022 12:32, David W. Hodgins wrote:
> On Thu, 13 Jan 2022 05:16:51 -0500, The Natural Philosopher
> <tnp@invalid.invalid> wrote:
>> However he did say  'start on login' which lets out most of te system
>> approaches to starting code and suggest the autostart menu
>
> Wrong.
>
> $ systemctl --user status
> ● x3.hodgins.homeip.net
>     State: running
>      Jobs: 0 queued
>    Failed: 0 units
>     Since: Tue 2022-01-11 18:02:15 EST; 1 day 13h ago
>    CGroup: /user.slice/user-500.slice/user@500.service
>            ├─redshift-gtk.service
>            │ ├─3535 /bin/bash /usr/local/bin/redshift-gtk
>            │ ├─3612 /usr/bin/python3 /usr/bin/redshift-gtk
>            │ └─3613 /usr/bin/redshift -v
>            ├─pulseaudio.service
>            │ └─2835 /usr/bin/pulseaudio --daemonize=no
> --log-target=journal
>            ├─gvfs-daemon.service
>            │ └─3618 /usr/libexec/gvfsd
>            ├─init.scope
>            │ ├─2391 /usr/lib/systemd/systemd --user
>            │ └─2395 (sd-pam)
>            └─dbus.service
>              └─2865 /usr/bin/dbus-daemon --session --address=systemd:
> --nofork --nopidfile --systemd-activation --syslog-only
>
> $ tree -ifa  .config/systemd/user/
> .config/systemd/user
> .config/systemd/user/default.target.wants
> .config/systemd/user/default.target.wants/redshift-gtk.service ->
> /etc/xdg/systemd/user/redshift-gtk.service
> .config/systemd/user/ethumb.service -> /dev/null
>
> So as above, I'm using systemd user units to cause redshift-gtk to start
> and to
> stop ethumb from running.
>
> Also, see "man systemd-xdg-autostart-generator", and try opening a terminal
> and running xdg-autostart.
>
> Neither xdg or systemd user units involve a desktop environment's
> autostart, but
> both start things on user login. There's also dbus that can run things
> on user
> login.
>
> On user login, the autostart menu is just one of several ways things can
> start on
> user login. As I mentioned before, if multiple desktop environments are
> installed,
> the non running desktop can still activate things from it's autostart on
> user login.
>
> Without knowing which distro and package is involved, and what desktop
> environments
> have been installed, so things can be looked at to see which methods are
> used, the
> question cannot be answered.
>
> Regards, Dave Hodgins

These are all daemons and applets though - he said 'programs'
And he certainly never mentioned multiple desktop environments. I think
you are over thinking this

--
In todays liberal progressive conflict-free education system, everyone
gets full Marx.

On Thu, 13 Jan 2022 14:47:21 -0500, The Natural Philosopher <tnp@invalid.invalid> wrote:
> These are all daemons and applets though - he said 'programs'
> And he certainly never mentioned multiple desktop environments. I think
> you are over thinking this

Applets are programs that just happen to be confined to the system tray, normally.

My whole point was that not enough info was given. Speculating and making
assumptions doesn't server any purpose without the op saying what program was
being started.

Regards, Dave Hodgins

On 13/01/2022 20:25, David W. Hodgins wrote:
> On Thu, 13 Jan 2022 14:47:21 -0500, The Natural Philosopher
> <tnp@invalid.invalid> wrote:
>> These are all daemons and applets though - he said 'programs'
>> And he certainly never mentioned multiple desktop environments. I think
>> you are over thinking this
>
> Applets are programs that just happen to be confined to the system tray,
> normally.
>
> My whole point was that not enough info was given. Speculating and making
> assumptions doesn't server any purpose without the op saying what
> program was
> being started.
>
It's clear that you never went to Sandhurst or operated in a real world
managerial position.
Making decisions in the absence of certain knowledge is the art of real
management.

Its like that WWII intelligence story 'how many tanks are the Germans
producing?'

'we don't know, but if we collect all the gearbox serial numbers of
wrecked tanks, and assume that the Germans have a linear numbering
system, and analyse the statistical spread, we can come up with a useful
estimate';

> Regards, Dave Hodgins

--
“Some people like to travel by train because it combines the slowness of
a car with the cramped public exposure of 
an airplane.”

Dennis Miller

On Thu, 13 Jan 2022 15:47:45 -0500, The Natural Philosopher <tnp@invalid.invalid> wrote:
> It's clear that you never went to Sandhurst or operated in a real world
> managerial position.
> Making decisions in the absence of certain knowledge is the art of real
> management.

But it's pointless in usenet discussions about a specific problem when the op
doesn't answer questions. Speculating about what program the op was referring to
is a waste of time. Feel free to keep doing so. I'm done with this discussion
unless the op provides the answer indicating he actually does want an answer.

Regards, Dave Hodgins

On 1/13/22 4:22 PM, David W. Hodgins wrote:
> On Thu, 13 Jan 2022 15:47:45 -0500, The Natural Philosopher
> <tnp@invalid.invalid> wrote:
>> It's clear that you never went to Sandhurst or operated in a real world
>> managerial position.
>> Making decisions in the absence of certain  knowledge is the art of real
>> management.
>
> But it's pointless in usenet discussions about a specific problem when
> the op
> doesn't answer questions. Speculating about what program the op was
> referring to
> is a waste of time. Feel free to keep doing so. I'm done with this
> discussion
> unless the op provides the answer indicating he actually does want an
> answer.
>
> Regards, Dave Hodgins

I still think todays Gnome was the product of
pointy-haired bosses .......

Should any of us help SUPPORT "bad" ?

On Friday, January 7, 2022 at 9:35:24 AM UTC-5, Steve Mysterious wrote:
> Redhat 8
> GNOME 3.32
>
> How can I prevent a program from being automatically started in GNOME after logging in?
>
> I tried the Tweaks extension.
>
> Once I reboot the system the program still starts up and its listing in the Tweaks has returned.
>
> Is there a text file I can edit as root or a path I can go to in the gconf-editor?

My situation was that Microsoft Teams was launching on startup.

I didn't want that as I need a secure VPN connection first, for Teams to work.
It was a nuisance having to shut Teams off first.
The VPN login could not be automated for security reasons.

Despite having GNOME Tweaks installed and going to it to remove Microsoft Teams from the startup applications, Microsoft Teams
would continue to launch on startup. It would also be listed in the startup applications again, after removing it.

I discovered by going through the preferences in Microsoft Teams, that there was an option there to launch on startup.

Despite removing teams from the startup list at the OS level, Microsoft Teams had the ability to put itself back in to the startup list ( or do something similar ).

Once I found that option in Microsoft Teams I was able to uncheck it and keep Microsoft Teams from launching on startup.

Problem solved

Steve

On Tuesday, January 11, 2022 at 12:14:09 AM UTC-5, 1.AAC0832 wrote:
> On 1/7/22 9:35 AM, Steve Mysterious wrote:
> > Redhat 8
> > GNOME 3.32
> >
> > How can I prevent a program from being automatically started in GNOME after logging in?
> Don't use Gnome ... it sucks. :-)

I agree!

It isn't my laptop. I do have Cent OS 7 ( not my choice either ) running in the virtual machine software that comes with Red Hat 8.

Inside of Cent OS 7 running in the virtual machine I installed Cinnamon.

I noticed though that in the Applications menu there were two sets of menu options for many of the same things. I though maybe the copy of GNOME 3 with the Red Hat 8 host might have been canceling out my settings to the startup list, vice-versa, or if there was a permissions issue with me not being able to update the startup applications list.

It turned out Microsoft Teams, the application I did not want to launch on startup, had its own option to launch on startup. Once I discovered and unchecked that I was able to make Microsoft Teams stop launching on startup.

Steve