Linux Lite 2.4 won't log out...Live CD or installed

[avj]

I don't know if this will help or not but it was interesting, give it a read.
https://forum.xfce.org/viewtopic.php?id=6580

[gold_finger]

Unless I am mistaken, this is an LL-specific issue. As that, this needs to be looked at by someone...

I actually don't think it's an LL specific thing.  I have vague recollections of seeing this type of thing on Mint forums before.  I never really paid that much attention to it, but it did stick in my head that people had better luck using the "Action Buttons" on panel rather than normal shutdown.  Why?  I have no idea and I really wasn't expecting much when I threw that suggestion out here for this thread.  Apparently it does make a difference.  There must be some confluence of circumstances that causes this problem every once and a while for certain people, since it seems to be pretty rare.  My guess is that for some reason certain hardware setups don't react as expected to the code for shutting down written into the Menu shutdown button; but do work from the code written for the Action Button -- which, presumably must be slightly different (otherwise you'd expect that to fail too).  All purely a guess on my part though.  I could be completely wrong.

Hi GoldFinger,
Yes that worked for me. However I don't have a small action button on the panel but a large-ish square on the desktop with my name on. But clicking on it does indeed log me out correctly. I suppose the next question is: can I superimpose it on or even replace the official shutdown button with it? Also is there any way I can resize it? But these are just minor details really.

Thanks for your help, much appreciated.

That's very strange!  I have no idea how the button ended up on the desktop instead of the panel.  Try following steps again to add it to the panel.  If it works, then just delete the one on the desktop.

[N4RPS]

Hello!

May be an issue with the AMD processor, as there was someone else here who also has an AMD processor.

To find out if it's part of a greater issue with XFCE, I'll try installing Xubuntu 14.04 on it, and see what happens...

73 DE N4RPS
Rob

[litelovelinux]

i have xubuntu installed now on it...no issues...with the workaround gold finger mentioned, it's odd how the shutdown command button works and the log off/out doesn't. Maybe its something with the whisker menu.

i tried the method avj linked...didn't work either

[anon222]

Interesting, Not sure what the issue is.

xfce uses this command to logout

Code:

xfce4-session-logout --logout

There is a shutdown script also.
Open the text editor with this command

Code:

leafpad $HOME/Desktop/logout.sh

paste this code inside

Code:

#!/bin/sh

LOGOUT=$(zenity --width=300 --height=300 --list --radiolist --text="Choose" --title="Logout" --column="Choice" --column="Action" TRUE "Shutdown" FALSE "Restart" FALSE "Suspend" FALSE Hibernate FALSE "Lock with xscreensaver" FALSE "Lock with light-locker" FALSE Logout)

if [ -n "${LOGOUT}" ];then
case $LOGOUT in
  Shutdown)
    dbus-send --system --print-reply --dest="org.freedesktop.ConsoleKit" /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop
    ;;
  Restart)
    dbus-send --system --print-reply --dest="org.freedesktop.ConsoleKit" /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Restart
    ;;
  "Lock with xscreensaver")
    xscreensaver-command -lock
    ;;
  "Lock with light-locker")
    light-locker-command -l
    ;;
  Suspend)
   dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend
   ;;
  Hibernate)
   dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Hibernate
   ;;
  Logout)
   xfce4-session-logout --logout
   ;;
  esac
fi

save and close it.
You'll see logout.sh on the Desktop, right-click on it and make executable. When you run it it will bring a list of shutdown options.

Just remembered, it could be the AMD Graphics driver.
Are you using propriatary  or free drivers?

Code:

/usr/bin/software-properties-gtk --open-tab=4

[N4RPS]

Hello!

With some help from its creator, I was able to successfully complete the procedure documented in the YouTube video.

I created your script on the desktop, and made it executable. So far, it seems to work right away, This is very good, because in an actual install, the action button is just as slow to respond as the Whisker Menu is. Additionally, the gksu/gksudo command, or anything else requiring root password (except terminal sudo/su) takes 30-40 seconds to appear after being called on.

Just remembered, it could be the AMD Graphics driver. Are you using propriatary  or free drivers?

UPDATE:

It IS a driver issue with certain AMD Radeon HD video cards!. As I see it all, seem AMD, the X11 folks, and XFCE are blame-shifting the whole thing back and forth. Meanwhile....

The Full Story: https://bugs.launchpad.net/ubuntu/+sourc...ug/1319220

Let's see... I had figured out that X11 had something to do with it - specifically, X11 as XFCE uses it. Misko's reference to the video driver was the missing piece of the puzzle.

If you're affected by this in LL and XFCE, creating the following file should fix it. If the fixes the OP's issue, then I guess this one can be flagged as SOLVED.

Code:

sudo mkdir -p /etc/X11/xorg.conf.d/

Code:

sudo leafpad /etc/X11/xorg.conf.d/20-radeon.conf

Copy the following lines, and paste them into Leafpad with [CTRL-V]:

  Section "Device"
      Identifier "Radeon"
      Driver "radeon"
      Option "AccelMethod" "EXA"
  EndSection

Press [CTRL-S] to save, and [CTRL-Q] to quit. Reboot. For me, LL is now as snappy as it ought to be!

If  anyone doesn't know what kind of video card they have, as you see below, if the output of

Code:

sudo lshw -c video

says AMD or ATI, please reply with the model number. This way, we can get an idea of which models are affected - and which ones aren't. We already know that Radeon HD 8250 is, but Radeon HD 6320 is not...

END UPDATE

Not sure, but it just MIGHT be the issue:

rob@N4RPS-3135-LL:~$ sudo lshw -c video
[sudo] password for rob:

30-45 seconds later...

  *-display             
      description: VGA compatible controller
      product: Temash [Radeon HD 8250/8280G]
      vendor: Advanced Micro Devices, Inc. [AMD/ATI]
      physical id: 1
      bus info: pci@0000:00:01.0
      version: 00
      width: 64 bits
      clock: 33MHz
      capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
      configuration: driver=radeon latency=0
      resources: irq:81 memory:e0000000-efffffff memory:f0800000-f0ffffff ioport:3000(size=256) memory:f0200000-f023ffff memory:f0260000-f027ffff

On my Samsung, which has no latency issues, this report also took a bit of time to generate. IT has a Radeon HD *6320*, and the width is *32 bits*. Same driver  - radeon. (I wonder if THAT could have something to do with it?)

I sure hope an overall solution is out there for this. These long delays are going to drive me to forget about running LL on this particular netbook...

73 DE N4RPS
Rob

[litelovelinux]

i tried a few things misko_2083 posted and had mixed results

i pasted the long code into leafpad..saved it as logoff.sh and made it executable and
set it on the desktop. On the Athlon 5350 pc it immediately went to this little window with options



click on any of these options it immediately works, I was surprised. So i restarted and clicked on the start menu log off button, the original issue, and the same frozen results.

I'm not a coder but is the code you posted misko_2083 the same as the one linked to the log off button in the whisker menu? Seems like it works but with a different gui style logoff window.

BTW..i also pasted it into terminal and the log out window immediately popped up with the same working results

next i tried the video card suggestion script code and i have found an odd happening. I noticed this the other day but didnt think anything of it. I can see the additional driver updates to install but i cant screen shot it with the athlon 5350 pc...it freezes. So i loaded the live usb onto my trusty Phenom II pc and captured what it looks like in the Athlon 5350 pc..



It shows im using the VESA driver. Where it says "open source tested" next to the end of the vesa string, the Athlon 5350 says "recommended". Ive tried in LL and Xubuntu to grab the fglrx drivers with no success...So i stay with the VESA (Recommended) driver. My Phenom PC has a sapphire 6850 in it and the fglrx works fine. The vesa in the Athlon 5350 seems ok to...1080p rez and no heat issues from what i can tell. I don't know why it wont let me get the fglrx drivers. Maybe its just this little chips on-board graphics are odd or the fglrx arent optimized for it.

I'm torn from thinking its the graphics driver because there's 2 things that conflict.

reason against video driver issues - xubuntu works and logs off fine with this athlon 5350 pc

reason for video driver issues - the screenshot tool doesnt work on the athlon 5350 pc

remember im doing all these things in a live session...but as i mentioned in my first post, i installed LL with the same issues as the live previously.

I haven't mentioned it yet but i really appreciate all the input. I never thought i'd get this type of response. The best part is i'm learning a little bit more about Linux

update

here's a screen of the graphics setup in xubuntu...identical to LL...it's not vesa but Xorg...and it says recommended above the driver version line...not beside it

[gold_finger]

Thanks a lot N4RPS for digging further into this.  Looks like you may have found cause & solution.

Just for the record, I have two machines running with the Radeon HD 4250 (using standard Linux drivers) and they don't seem to be affected by this.

[N4RPS]

Hello!

Thanks. I guess this only affects the latest AMD/ATI chipsets. Let me tell you - the fix has transformed this thing into a completely different machine. No lag whatsoever now - it finally performs as a quad-core netbook with LL, an SSD, and 4 GB RAM SHOULD.

To make it easier for others to find in the future, I'm thinking about posting this in the hardware area...

73 DE N4RPS
Rob

[litelovelinux]

Looks like you may have found cause & solution.

the fix

what's the fix or solution?