stop "triggers" logout (from gnome-session?) without warning. Argument required but ignored?
Bug #1256262 reported by
Páll Haraldsson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-session (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| upstart (Ubuntu) |
Invalid
|
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
lp:~jamesodhunt/ubuntu/trusty/gnome-session/bug-1256262
- Dimitri John Ledkov: Approve
-
Diff: 809 lines (+10/-762)5 files modified.pc/103_kill_the_fail_whale.patch/gnome-session/gsm-fail-whale.c (+0/-47)
.pc/13_display_session_properties.patch/data/session-properties.desktop.in.in (+0/-15)
.pc/git_fix_wrong_unref_call.patch/gnome-session/gsm-shell.c (+0/-700)
debian/changelog (+7/-0)
debian/gnome-session.user-session.upstart (+3/-0)
| 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 |
Revision history for this message
| James Hunt (jamesodhunt) wrote | #1 |
| affects: | upstart → upstart (Ubuntu) |
| Changed in upstart (Ubuntu): | |
| status: | New → Confirmed |
| Changed in gnome-session (Ubuntu): | |
| status: | New → Fix Released |
| Changed in upstart (Ubuntu): | |
| status: | Confirmed → Invalid |
To post a comment you must log in.
Problem is caused by UPSTART_JOB and UPSTART_INSTANCE still being set in the gnome-session environment.