Logout doesn't call com.canonical.Unity.Session.RequestLogout

Bug #1323992 reported by Ying-Chun Liu
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-session (Ubuntu)
New
Critical
Charles Kerr

Bug Description

Hi,

I've tried with by branch lp:~paulliu/unity8/logout with Unity-Mir session.
When manually using qdbus, I can successfully kill unity8 process.
But when click logout in indicator-session, I found it didn't call com.canonical.Unity.Session.RequestLogout
Here's the dbus-monitor --session log http://paste.ubuntu.com/7534797/

Please check it.

Many Thanks,
Paul

--
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu

Distributor ID: Ubuntu
Description: Ubuntu Utopic Unicorn (development branch)
Release: 14.10
Codename: utopic

2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center

indicator-session:
  Installed: 12.10.5+14.04.20140410-0ubuntu1
  Candidate: 12.10.5+14.04.20140410-0ubuntu1
  Version table:
 *** 12.10.5+14.04.20140410-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ utopic/main i386 Packages
        500 http://tw.archive.ubuntu.com/ubuntu/ utopic/main i386 Packages
        100 /var/lib/dpkg/status

3) What you expected to happen

unity8 process killed

4) What happened instead

nothing happened.

Charles Kerr (charlesk)
Changed in indicator-session (Ubuntu):
assignee: nobody → Charles Kerr (charlesk)
importance: Undecided → High
Revision history for this message
Albert Astals Cid (aacid) wrote :

Moving to Critical since https://bugs.launchpad.net/unity8/+bug/1302213 that depends on this one is set as Critical

Revision history for this message
Albert Astals Cid (aacid) wrote :

Ah, i can't :D Well, just wanted to say it should be Critical then ^_^

Lars Karlitski (larsu)
Changed in indicator-session (Ubuntu):
importance: High → Critical
Revision history for this message
Charles Kerr (charlesk) wrote :

So, this is not the bug that I thought it was -- I already have a branch for this that I thought had landed in trunk but hasn't, so when investigating I expected to see a bug in the new code rather than the old, unpatched code :-)

This is all covered in bug #1296814 so I'm marking this ticket as a duplicate and will promote its importance to Critical to match this one.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.