Ctrl+Alt+Delete does not open sys monitor

[Doug McMahon]

Test Case:
Fresh install or live session with current image (10.05 here
Go Ctrl+Alt+Delete on keyboard

What should happen:
system-monitor should open

What does happen:
Log out window opens

If the compiz intergrated binding is unset & then set back to default then sys monitor will open

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: compiz 1:0.9.10+13.10.20131004-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Oct 5 16:50:54 2013
DistUpgraded: Fresh install
DistroCodename: saucy
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0209]
InstallationDate: Installed on 2013-10-05 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131005)
MachineType: Dell Inc. XPS M1330
MarkForUpload: True
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic root=UUID=c3cc23f6-929e-4b25-9e41-479728438116 ro quiet splash vt.handoff=7
SourcePackage: compiz
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: XPS M1330
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.10+13.10.20131004-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu9
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.903-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Christopher Townsend (townsend)]

Yeah, I sometimes see it working and other times it is not. Currently, it's working again for me, but for a colleague of mine, it brings up the logout dialog. I think using the Commands plugin in Compiz to accomplish this is just too fragile. I plan on trying to fix this correctly for 14.04.

I've seen other comments about whether this is a good idea or not. I will say that this is a design issue and Ayatana Design has said that System Monitor opened to the processes tab is the expected behavior (see bug #890747). I want to stay out of the debate as to whether this should be the expected behavior- I've only been tasked to implement it:)

[Doug McMahon (mc3man)]

From a user perspective the commands plugin could be described as 'fragile'. I've found in compiz 0.9.x that user set commands have have a lifetime of several days or so during which they just disappear & need to be reset over & over again.

However an integrated command seems to be very solid & persistent once set which seemed to be the issue here.
( for myself took the change as an opportunity to integrate a command I do want without much work & it has been fine ever since, both for orig. user & any add. users.

So to test current state booted to todays image -
In live session on ubuntu user sys mon was opened from binding
Set up a new user, logged in, sys mon was opened ^

Installed 13.10 from the image, rebooted & when logged in sys mon was opened from the intended binding.

So atm all seems well, what was happening before on new installs doesn't seem to be anymore
(the command & binding where set but not active for the orig. user of that new install

I've no doubt that if your colleague either did a new install or unset & reset the binding back to the default in dconf it would work as Design intends & remain working.

What could happen to upgraders with the current setup I've no clear idea, one would have to try..

[j s n j (jsnj)]

I found this bug thread because I thought it was a bug that the system monitor opened instead of the log out dialog. I don't have a major problem with this being hard coded so to speak for the system monitor. The problem is that in Settings - Keyboard - Shortcuts, Ctrl Alt Del is set to Log Out, so a user would expect that behavior. There needs to be consistency. If it's going to be set in compiz to system monitor, it should reflect that in settings and perhaps grayed out/unselectable. As of this writing, if the user sets Log Out to Ctrl Alt Del in Settings it will stay that way only for that session. There's no indication anywhere that it will be automatically reset to system monitor upon log in, yet still not reflect the change in Settings. It's the eve of the final 13.10 release. I'll retest with the final 13.10 release and see if the settings reflect the compiz command behavior.

[Doug McMahon (mc3man)]

This appears to be fixed in 14.04, at least as seen with a new install of 11/15 image