Misleading "you have open files" logout message

[qwach]

Sometimes, the "you have open files that you might want to save" logout/shutdown message appears even when all I'm doing at the time is web browsing (Chromium). I haven't been able to consistently trigger this yet, but will try in a few minutes.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
Uname: Linux 3.8.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell,dbus,scale,expo]
Date: Sun May 19 15:11:11 2013
InstallationDate: Installed on 2013-01-01 (138 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
SourcePackage: unity
UpgradeStatus: Upgraded to raring on 2013-04-28 (21 days ago)

[qwach (qwach)]

OK, test case: open the Log Out or Shut Down dialog while a program is being started in the launcher (I only got it to work the first time a program starts because the first start takes much longer), and the "you have open files" message will be shown. Beyond that - and this is much worse - the system will be automatically rebooted (Shut Down dialog) or log the current user out (Log Out dialog) after a few seconds if the dialog is exited. I haven't tested what happens if the dialog is left alone.

[qwach (qwach)]

Done: The forced log out/reboot will happen no matter what, shortly after the program that was being loaded opens behind the Log Out/Shut Down dialog.

[Launchpad Janitor (janitor)]

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

[Will Cooke (willcooke)]

Sorry folks, but as part of the bug clean up ahead of 16.04 I'm marking this as invalid because it affects an Ubuntu release which is now unsupported. If you can still recreate this bug in a supported release please do open a new bug and we can triage it for consideration in the 16.04 development cycle.