No way to kill maximus

Bug #396485 reported by Luca Ferretti
48
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Maximus
Confirmed
Wishlist
Unassigned
maximus (Ubuntu)
Confirmed
Wishlist
Unassigned

Bug Description

Could be good add a way to kill all running maximus and prevent them to restart

Current behavion:
 If you have maximus started in you session and if you try to kill it, it will be restarted

Expeted behavior
 Provide a command line option (for example, --kill or --quit) to quit maximus and don't automatically restart it in current session

Reason
 Of course this is a feature for "advanded" users, that could need to stop maximus without disabling in startup application capplet and restart the session. For example, currently I need it to test gnome-shell

Tags: ubuntu-unr
Revision history for this message
Paul Larson (pwlars) wrote :

This bug has been moved to the Ubuntu distribution

Changed in maximus:
status: New → Won't Fix
Changed in maximus (Ubuntu):
importance: Undecided → Wishlist
tags: added: ubuntu-unr
Neil J. Patel (njpatel)
Changed in maximus:
status: Won't Fix → Confirmed
importance: Undecided → Medium
milestone: none → 0.4.11
milestone: 0.4.11 → none
importance: Medium → Wishlist
Neil J. Patel (njpatel)
Changed in maximus (Ubuntu):
status: New → Confirmed
Revision history for this message
Mark Stosberg (markstos) wrote :

I disagree with this feature request. I think the ability to stop the maximus service and logout/login again is sufficient.

Revision history for this message
dbkaplun (dbkaplun) wrote :

Please tell me why you think I shouldn't be able to kill a process that is not required for proper functionality. To me that's like not being able to kill gnome-panel (which is WAY more vital than maximus).

Please, either tell users like me how to stop the damn process, or make it killable.

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

This daemon is part of the session, in lucid, you can switch back to gnome session to not have it. As every session daemon, you can activate/deactivate them in System -> Preferences -> Startup apps which is the right and only way to stop session deamon.

Revision history for this message
dbkaplun (dbkaplun) wrote :

I have no maximus in my Startup Apps.

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

Hum, strange, get it there on lucid (not a fresh install).

You still can either edit it manually or change the value on gconf-editor like thoses in /apps/maximus/ (it will still be there, but you can disable the maximize function)

Revision history for this message
dbkaplun (dbkaplun) wrote :

I have no_maximize set to checked and undecorate as unchecked but it still maximizes and undecorates.

Revision history for this message
Berend De Schouwer (berend-de-schouwer) wrote :

I have the same problem:
- maximus starts, even though it's not in startup.
- cannot get rid of it.

This appears to be due to a Ubuntu upgrade, that saved it in the session,

Revision history for this message
Gizmo (simplysoftware) wrote :

I also can't turn off maximus, I've tried removing it from startup, I've tried logging into gnome session, next step is to remove it manually and completely, however I'm not sure if this will break things

Revision history for this message
kayandus (bierfiltertje) wrote :

1,5 years later, but I just had the same problem. It seemed liked a reinstall of maximus solved the problem for me.

Revision history for this message
Jeff Grembecki (jyff) wrote :

You can start maximus with the -s option and it will not automatically restart.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.