stop "triggers" logout (from gnome-session?) without warning. Argument required but ignored?

Bug #1256262 reported by Páll Haraldsson on 2013-11-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-session (Ubuntu)
Undecided
Unassigned
upstart (Ubuntu)
Undecided
Unassigned

Bug Description

In shell:
stop

Result:
"logout"

Intended:
Nothing (was a typo, meant to write top).

Fortunetly I didn't loose any data, but I would have if I would have had any unsaved files so this is at least a critical usablity issue if not a security vulnerability (Denial of Service vulnereabilty from authenticated user.. (myself)? Didn't check the box. shutdown requires sudo..).

Also (all?) other initctl commands affected:

start
start: Job is already running: gnome-session

man stop
start JOB [KEY=VALUE]...

stop JOB [KEY=VALUE]...

JOB should be required(?)

Just in case (not sure how to report/change "Affects"), using 13.10, upstart 1.10-0ubuntu7, but I guess older/newer versions are also affected..

Related branches

description: updated
summary: - stop "triggers" logout (from gnome-session?) without warning, argument
+ stop "triggers" logout (from gnome-session?) without warning. Argument
required but ignored?
description: updated
description: updated
James Hunt (jamesodhunt) wrote :

Problem is caused by UPSTART_JOB and UPSTART_INSTANCE still being set in the gnome-session environment.

affects: upstart → upstart (Ubuntu)
Changed in upstart (Ubuntu):
status: New → Confirmed
James Hunt (jamesodhunt) on 2013-12-05
Changed in gnome-session (Ubuntu):
status: New → Fix Released
James Hunt (jamesodhunt) on 2013-12-09
Changed in upstart (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers