| 2013-11-29 10:26:18 |
Páll Haraldsson |
bug |
|
|
added bug |
| 2013-11-29 10:27:39 |
Páll Haraldsson |
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 useablity issue if not a security vulnerability (Denial of Service vulnereabilty from authenticated user (myself)? Didn't check the box).
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(?) |
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).
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(?) |
|
| 2013-11-29 10:33:42 |
Páll Haraldsson |
summary |
stop "triggers" logout (from gnome-session?) without warning, argument required but ignored? |
stop "triggers" logout (from gnome-session?) without warning. Argument required but ignored? |
|
| 2013-11-29 10:35:30 |
Páll Haraldsson |
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).
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(?) |
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(?) |
|
| 2013-11-29 10:40:57 |
Páll Haraldsson |
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(?) |
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.. |
|
| 2013-12-02 17:50:23 |
James Hunt |
affects |
upstart |
upstart (Ubuntu) |
|
| 2013-12-02 17:50:42 |
James Hunt |
upstart (Ubuntu): status |
New |
Confirmed |
|
| 2013-12-02 17:53:54 |
James Hunt |
attachment added |
|
Updated /usr/share/upstart/sessions/gnome-session.conf that fixes the issue https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1256262/+attachment/3921596/+files/gnome-session.conf |
|
| 2013-12-04 09:34:59 |
Launchpad Janitor |
branch linked |
|
lp:~jamesodhunt/ubuntu/trusty/gnome-session/bug-1256262 |
|
| 2013-12-04 12:32:48 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-desktop/gnome-session/ubuntu |
|
| 2013-12-04 12:47:43 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/trusty-proposed/gnome-session |
|
| 2013-12-05 09:13:41 |
James Hunt |
bug task added |
|
gnome-session (Ubuntu) |
|
| 2013-12-05 09:14:00 |
James Hunt |
gnome-session (Ubuntu): status |
New |
Fix Released |
|
| 2013-12-09 09:01:08 |
James Hunt |
upstart (Ubuntu): status |
Confirmed |
Invalid |
|
