LinuxVillage

Questions En => Help requests => Discussion démarrée par: djohnston le 04 juin 2013 à 04:04:33

Titre: Problems with LXDE
Posté par: djohnston le 04 juin 2013 à 04:04:33
The first post in this thread has been moved to here (http://linuxvillage.net/index.php/topic,381.msg2614.html#msg2614). The reason is that this thread has become a mix of LXDE and other help answers, as well as an assortment of how-tos.

Titre: Re : Problems with LXDE
Posté par: patrick013 le 04 juin 2013 à 05:03:35
The installed applications are part of the Debian LXDE desktop, except for file-roller which replaced Xarchiver.

I put a copy of PeaZip portable in mine.    It's supposed to have 100's
of filetypes.    Just an idea.

Can't get used to using a root logoff, and haven't found a good theme
yet, but my Debian LXDE otherwise works great.

Have a good one.

Patrick
Titre: Re : Problems with LXDE
Posté par: djohnston le 04 juin 2013 à 08:48:30
Can't get used to using a root logoff, and haven't found a good theme yet, but my Debian LXDE otherwise works great.

root logoff? Do you mean you can't logout or shutdown/reboot unless you are user root? If so, something's missing.

Titre: Re : Problems with LXDE
Posté par: patrick013 le 04 juin 2013 à 14:21:18
root logoff? Do you mean you can't logout or shutdown/reboot unless you are user root? If so, something's missing.

Yes, if there's any window open it needs the root password,
otherwise it logs right out.    Debian's the only one that does
that.       Any fix for that ?

THX

Patrick
Titre: Re : Problems with LXDE
Posté par: Taco.22 le 04 juin 2013 à 14:47:24
If root is active then the root password is needed to log out, or the root activity shut down.  For example, if Synaptic is open, or apt-get is still live in a terminal the logout command will trigger a request for the root password so that the system can shut down those apps.  If you close them manually then the system will logout without error.
Titre: Re : Problems with LXDE
Posté par: melodie le 04 juin 2013 à 15:46:17
Hi,

Please use the link with this path: http://tyruiop.eu/~melodie/Downloads/ISOS/LinuxVillage/Debian (http://tyruiop.eu/~melodie/Downloads/ISOS/LinuxVillage/Debian)

The other one is only a symlink which I will remove on day next. (No need to thank me, but if you want to thank someone it would be Nazral who offers this hosting to me at no cost).


Titre: Re : Problems with LXDE
Posté par: melodie le 04 juin 2013 à 16:38:46
Debian's the only one that does that. Any fix for that ?

Perhaps polkit authorizations. This is the guess I would do.

Look in the directory: /etc/polkit-1/localauthority/50-local.d : is there a file in it ?

If not, you could try to use this one:
http://meets.free.fr/Downloads/debian/configurations/55-myconf3.pkla (http://meets.free.fr/Downloads/debian/configurations/55-myconf3.pkla)

name is as you want, you need a number and the .pkla at the end.

You can change the unix group as per this file:
http://meets.free.fr/Downloads/debian/configurations/55-myconf2.pkla (http://meets.free.fr/Downloads/debian/configurations/55-myconf2.pkla)

or this file:
http://meets.free.fr/Downloads/debian/configurations/55-myconf.pkla (http://meets.free.fr/Downloads/debian/configurations/55-myconf.pkla)

your user needs to be in the group "sudo", or "polkituser" or "wheel", if it belongs to one of these, then you can write it in the Identity=unix-group:something line.

Titre: Re : Problems with LXDE
Posté par: patrick013 le 04 juin 2013 à 18:17:42
Perhaps polkit authorizations. This is the guess I would do.

Well I'm right in the middle of backing everything up, so will try this
shortly.

There is a LXPolkit and a gnome-polkit which I've tried both.

If it works without sudo that would be nice.    The fellow at livarp
has his Debian working logouts without a root password, don't
know exactly how yet.   Something to do later.

thanks for the response(s).

Patrick
Titre: Re : Problems with LXDE
Posté par: djohnston le 04 juin 2013 à 19:14:51
Please use the link with this path: http://tyruiop.eu/~melodie/Downloads/ISOS/LinuxVillage/Debian (http://tyruiop.eu/~melodie/Downloads/ISOS/LinuxVillage/Debian)

The other one is only a symlink which I will remove on day next.
I don't understand. Are you saying the direct links I posted to the iso and md5 sum files will disappear?

Titre: Re : Problems with LXDE
Posté par: djohnston le 04 juin 2013 à 19:22:28
If it works without sudo that would be nice.    The fellow at livarp has his Debian working logouts without a root password, don't know exactly how yet. Something to do later.

You should not need to use sudo or any root privileges to logout. Even with no policykit. As far as shutdown and poweroff requests, that is usually handled by consolekit. If you have a standard Debian LXDE installation, you should have no problems whatsoever. I've never encountered this with Debian. Unless ...

Are you using a login manager, such as LightDM, XDM, Slim, etc? The login manager package installs and configures consolekit. But, to logout, without reboot or shutdown, no policykit or consolekit is required. Unless the situation is as Taco.22 described.

Titre: Re : Problems with LXDE
Posté par: melodie le 04 juin 2013 à 19:55:01
You should not need to use sudo or any root privileges to logout. Even with no policykit. As far as shutdown and poweroff requests, that is usually handled by consolekit.

Consolekit makes use of some rules. The above files make the rules more flexible.

The "sudo" part I mentioned is related to groups to which the priviledge of shutting down without the root password will be given. Therefore to use it you need to check the /etc/group file and the groups the user belong to. Another possibility if I remember would to put "Identity=user:login_name_of_the_user" instead of "Identity=unix-group:something".

Exemples:
http://mdzlog.alcor.net/2010/06/27/navigating-the-policykit-maze/ (http://mdzlog.alcor.net/2010/06/27/navigating-the-policykit-maze/)

https://wiki.archlinux.org/index.php/PolicyKit#Authorities (https://wiki.archlinux.org/index.php/PolicyKit#Authorities)

and things are moving, so… ConsoleKit will no more be in use in the distributions. I suggest you try the file I provided, for me it works in any distro, Ubuntu (using Upstart) and in Archlinux (using systemd - and systemctl-logind instead of ConsoleKit).

Edit: and to add this file for a distribution provided for all, the line Identity=unix-group:something
is the way to go.

For exemple, if the distro has as an habbit to make the first user created belonging to the group "sudo", (as in Ubuntu) then you should use "sudo". If the distro has another habbit, for exemple the first user created (and or others) belong to the group "users", then instead of "sudo" you could use "users". If you want to make your version more restrictive, then you could write Identity=unix-group:wheel, and just tell the users that only if they make their login name belong to the wheel group, they can have the privilege, which will mean that they need to make use of the root password to add the user Bob, Alice or whoever to the wheel group,  therefore the shutdown, access to internal or external file systems, CD, whatever, will be entirely under their responsibility (even though you can make it easier for them to manage it).


Titre: Re : Problems with LXDE
Posté par: djohnston le 05 juin 2013 à 01:17:23
Melodie,

Well, I was responding to Patrick and his use of LXDE in Debian. Please remember that Ubuntu system rules may not apply to Debian. The configuration shown below is from the JWM Debian wheezy install I'm working on. I am able to logout, shutdown and reboot as a normal user.

Look in the directory: /etc/polkit-1/localauthority/50-local.d : is there a file in it ?

No, there is no file.

[root@VSLV ~]# ls -la /etc/polkit-1/localauthority/50-local.d
total 8
drwxr-xr-x 2 root root 4096 Dec 20 12:14 .
drwx------ 7 root root 4096 May 17 15:35 ..
[root@VSLV ~]#

your user needs to be in the group "sudo", or "polkituser" or "wheel", if it belongs to one of these, then you can write it in the Identity=unix-group:something line.

My normal user does not belong to any of those groups.

[root@VSLV ~]# cat /etc/group | grep darrel
dialout:x:20:darrel
cdrom:x:24:darrel
floppy:x:25:darrel
audio:x:29:darrel
video:x:44:darrel
plugdev:x:46:darrel
vboxsf:x:103:darrel
netdev:x:109:darrel
darrel:x:1000:
[root@VSLV ~]#

I am able to shutdown and reboot as a normal user using consolekit commands. I shamelessly stole them from one of Taco.22's Openbox remasters. Here they are from the .jwmrc file:

<Program icon="lock.png" label="Reboot">dbus-send --system --print-reply --dest=org.freedesktop.ConsoleKit /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Restart</Program>
<Program icon="lock.png" label="Shutdown">dbus-send --system --print-reply --dest=org.freedesktop.ConsoleKit /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop</Program>

I do intend to take advantage of mimas's obsession package. Anything that makes things simpler is best, in my opinion. And consolekit is anything but simple.

Titre: Re : Problems with LXDE
Posté par: melodie le 05 juin 2013 à 01:58:15
I had taken the consolekit commands from a buddy doing an Archlinux version with Openbox, and provided it in the pclos openbox versions, where Taco got it from.

And obsession-logout has the ability to use either consolekit or two other processes, systemd... and the Ubuntu thing for the power management.

From the experience I had here: http://linuxvillage.net/index.php/topic,292.0.html (http://linuxvillage.net/index.php/topic,292.0.html)

Citer
Then something will be needed so that obsession (the power management gui) still works correctly, that's to say provides all the features such as shutdown, reboot, suspend, hibernate, logout and cancel. A configuration file for polkit will have to be added into the system, otherwise, we will only get "Logout" and "Cancel", which might seem a bit short.

Here is a configuration file fit for our purpose, which we can name "55-myconfig.pkla", make it belong to root:root with 644 permissions and install to /etc/polkit-1/localauthority/50-local.d

Here is a content to allow the first user to shutdown and reboot, even if there is another session started:


In case of need, you could just use one.

Could I see the entire content of your /etc/group file ? I wonder which process in Debian sets up the groups for the first user created at install time?


PS: >Please remember that Ubuntu system rules may not apply to Debian.

The .pkla files can be needed in all distributions using polkit. I have one which I did manually, in Archlinux. It is possible that Debian devs considers it also an addition to be done by the administrator of the machine.

Unless the problem met is related to the same issue as here:
http://forums.debian.net/viewtopic.php?f=7&t=103881 (http://forums.debian.net/viewtopic.php?f=7&t=103881)

Titre: Re : Problems with LXDE
Posté par: Taco.22 le 05 juin 2013 à 03:07:27
I am building a system based on VillageBox but using Spacefm to create a "desktop" environment.  I installed lxpanel which comes with the logout command that usually connects to lxsession or something like that which I don't have.  Rumaging around in my box of spare bits I found the debian version of obsession that mimas had posted somewhere - I can't find where so just in case I have it here for download (https://dl.dropboxusercontent.com/u/18945176/obsession-compiled-for-debian-testing.tar.xz).

It is a manual install, but is very simple.  Once installed everything worked perfectly.  I even created a launcher on the panel, created a bash script and .desktop file and now also have obsession launch direct from the panel.  I had previously tried obsession from source but couldn't resolve a dependency issue - however this is very simple, straight forward and effective, and no configuring to do.
Titre: Re : Problems with LXDE
Posté par: melodie le 05 juin 2013 à 03:47:21
Hi,

The debian compiled tarball, is under here:
http://meets.free.fr/Downloads/debian/ (http://meets.free.fr/Downloads/debian/)

obsession-debian-testing-compiled.tar.xz (http://meets.free.fr/Downloads/debian/obsession-debian-testing-compiled.tar.xz)

You don't have much to do to change the menu logout in Lxpanel. I don't even have one with lxpanel under the hand to check. It's something as simple as a right-click on the panel go to preferences or panel settings, something of the kind and it's somewhere in the tabs (perhaps in advanced tab): you just change the logout command from there, replacing the command "lxsession-logout" with the command "obsession-logout".

See here? http://code.google.com/p/mimarchlinux/downloads/detail?name=obsession-20130101.tar.bz2 (http://code.google.com/p/mimarchlinux/downloads/detail?name=obsession-20130101.tar.bz2)

Citer
* xdg-autostart, start applications following Freedesktop Autostart specification.
* obsession-logout, display a dialog to power off, suspend, hibernate, logout or switch user.
* obsession-exit, the command line version of obsession-logout.

This is the first release. A lot of code was borrowed from LxDE.

The content of the above tarball should go directly into /usr/local, as usual, you should check the tree of the tarball.

Well, in fact if you just unpack it as root right under / you will get automatically everything at the right place with the right permissions!

# tar xfvJ obsession-debian-testing-compiled.tar.xz
brings out:
Citer
# ls -l usr/local/
total 0
drwxr-xr-x 2 root root 100  3 mars  15:34 bin
drwxr-xr-x 4 root root  80  3 mars  15:35 share
#

Citer
# ls -l usr/local/bin/
total 40
-rwxr-xr-x 1 root root 11296  3 mars  15:33 obsession-exit
-rwxr-xr-x 1 root root 20424  3 mars  15:33 obsession-logout
-rwxr-xr-x 1 root root  7728  3 mars  15:33 xdg-autostart
#

Citer
# ls -l usr/local/share/
total 0
drwxr-xr-x 63 root root 1260  3 mars  15:33 locale
drwxr-xr-x  3 root root   60  3 mars  15:33 obsession
#

guess what is in usr/local/share/locale and in usr/local/share/obsession ? :)

Titre: Re : Problems with LXDE
Posté par: Taco.22 le 05 juin 2013 à 04:43:17
Thanks for the link - I had one or two that hit a dead end.  Your're right about the panel logout command - right click the panel and hit Panel Settings which brings up PanelPreferences(?!?), go to Advanced and fill in the appropriate Logout Command.  Nice and simple.  I just went an extra step and added a Logout button on the panel which LXDE doesn't supply.

By the way, the VillageBox menu.xml and rc.xml settings still apply, so the keybinding of W-x still shuts the machine down, even if the Openbox root menu is not accessible on the "desktop".   
Titre: Re : Problems with LXDE
Posté par: melodie le 05 juin 2013 à 04:59:33
Some time ago I put most of the stuff here: http://meets.free.fr/Downloads. (http://meets.free.fr/Downloads.) (Kind of winter cleaning).


Titre: Re : Problems with LXDE
Posté par: Taco.22 le 05 juin 2013 à 05:16:42
That was one of my dead-end links.
Titre: Re : Problems with LXDE
Posté par: djohnston le 05 juin 2013 à 09:10:01
Could I see the entire content of your /etc/group file ? I wonder which process in Debian sets up the groups for the first user created at install time?

The JWM installation is starting to shape up and uses 47.3 MB at startup. The following is from that installation:

darrel@VSLV:~$ cat /etc/group
root:x:0:
daemon:x:1:
bin:x:2:
sys:x:3:
adm:x:4:
tty:x:5:
disk:x:6:
lp:x:7:
mail:x:8:
news:x:9:
uucp:x:10:
man:x:12:
proxy:x:13:
kmem:x:15:
dialout:x:20:darrel
fax:x:21:
voice:x:22:
cdrom:x:24:darrel
floppy:x:25:darrel
tape:x:26:
sudo:x:27:
audio:x:29:darrel
dip:x:30:
www-data:x:33:
backup:x:34:
operator:x:37:
list:x:38:
irc:x:39:
src:x:40:
gnats:x:41:
shadow:x:42:
utmp:x:43:
video:x:44:darrel
sasl:x:45:
plugdev:x:46:darrel
staff:x:50:
games:x:60:
users:x:100:
libuuid:x:101:
crontab:x:102:
vboxsf:x:103:darrel
fuse:x:104:
scanner:x:105:saned
messagebus:x:106:
colord:x:107:
bluetooth:x:108:
netdev:x:109:darrel
Debian-exim:x:110:
mlocate:x:111:
ssh:x:112:
avahi:x:113:
lpadmin:x:114:
utempter:x:115:
saned:x:117:
lightdm:x:116:
ntp:x:118:
nogroup:x:65534:
darrel:x:1000:
darrel@VSLV:~$

Titre: Re : Problems with LXDE
Posté par: djohnston le 05 juin 2013 à 10:04:52
Rumaging around in my box of spare bits I found the debian version of obsession that mimas had posted somewhere - I can't find where so just in case I have it here for download (https://dl.dropboxusercontent.com/u/18945176/obsession-compiled-for-debian-testing.tar.xz).

Pre-compiled.  :)  I like it!

Your're right about the panel logout command - right click the panel and hit Panel Settings which brings up PanelPreferences(?!?), go to Advanced and fill in the appropriate Logout Command.  Nice and simple.  I just went an extra step and added a Logout button on the panel which LXDE doesn't supply.

There is another way, but it isn't provided by installing just lxpanel. The shell script /usr/bin/lxde-logout and the desktop file /usr/share/applications/lxde-logout.desktop are provided by the Debian lxde-common package. If that one is installed along with lxpanel, you can create a launcher on the panel. Right-click the lxpanel, select Panel Settings and it shows a window titled "Panel Preferences", just like you said. Instead of selecting the Advanced tab, select the Panel Applets tab. Scroll to the bottom, select "Application Launch Bar" and add it to the panel. Close the window, then right-click the Application Launch Bar you just added to the panel. Select "'Application Launch Bar' Settings" and the window will pop up. You can browse the Available Applications in the right pane and add them to the left pane, thereby adding the application to the App Launch Bar on the panel. Confused yet?

You can add the Logout app, except that it doesn't show in the right pane unless you also installed the lxde-common package. Even then, it doesn't show. Here's why. The desktop file in /usr/share/applications contains the entry:

NoDisplay=true

Change that to:

NoDisplay=false
or
#NoDisplay=true

Add a Categories= line, for example:

Categories=System;

and it will show up in the System section where you can add it to the Application Launch Bar section of the lxpanel. Oh, and you can have multiple launch bars. When you click the Logout icon in the newly added Application Launch bar on the lxpanel, it will run the shell script /usr/bin/lxde-logout, which in turn calls the compiled executable /usr/bin/lxsession-logout. The executable displays the standard LXDE Shutdown/Reboot/Hibernate/Logout etc. menu.

Come to think of it, the way you did it is a helluva lot easier!  ;)

EDIT: I believe the source code for /usr/bin/lxsession-logout is part of what mimas used to create the obsession package. Very clever, that genius.  ;)
Titre: Re : Problems with LXDE
Posté par: Taco.22 le 05 juin 2013 à 11:38:04
Citation de: djohnston
Come to think of it, the way you did it is a helluva lot easier!  ;)

Yep, got it in one!  What I did is set up Openbox with lxpanel - stayed well away from LXDE itself.  So under the bonnet it is still Openbox running everything. I'm using Spacefm to create the "desktop" experience, but even though the Openbox right-click root menu is disabled OB's autostart, menu.xml and rc.xml are still running the show.  That and a bit of tweaking of the panel and gtk theme.  Adding the Logout button to the panel was straightforward - used "NoDisplay=true" so that it doesn't show in the main menu.  Also did that with Remastersys' Live Installer - not sure if that needs to be just laying about!
Titre: Re : Problems with LXDE
Posté par: melodie le 05 juin 2013 à 13:17:07
Pre-compiled.  :)  I like it!

Thanks. ;)
/me pre compiles here and then…

Citer
EDIT: I believe the source code for /usr/bin/lxsession-logout is part of what mimas used to create the obsession package. Very clever, that genius.  ;)

He said so, code borrowed from LXDE. He is very clever at coding!

The JWM installation is starting to shape up and uses 47.3 MB at startup. The following is from that installation:

darrel@VSLV:~$ cat /etc/group
root:x:0:
daemon:x:1:
bin:x:2:
sys:x:3:
adm:x:4:
tty:x:5:
disk:x:6:
lp:x:7:
mail:x:8:
news:x:9:
uucp:x:10:
man:x:12:
proxy:x:13:
kmem:x:15:
dialout:x:20:darrel
fax:x:21:
voice:x:22:
cdrom:x:24:darrel
floppy:x:25:darrel
tape:x:26:
sudo:x:27:
audio:x:29:darrel
dip:x:30:
www-data:x:33:
backup:x:34:
operator:x:37:
list:x:38:
irc:x:39:
src:x:40:
gnats:x:41:
shadow:x:42:
utmp:x:43:
video:x:44:darrel
sasl:x:45:
plugdev:x:46:darrel
staff:x:50:
games:x:60:
users:x:100:
libuuid:x:101:
crontab:x:102:
vboxsf:x:103:darrel
fuse:x:104:
scanner:x:105:saned
messagebus:x:106:
colord:x:107:
bluetooth:x:108:
netdev:x:109:darrel
Debian-exim:x:110:
mlocate:x:111:
ssh:x:112:
avahi:x:113:
lpadmin:x:114:
utempter:x:115:
saned:x:117:
lightdm:x:116:
ntp:x:118:
nogroup:x:65534:
darrel:x:1000:
darrel@VSLV:~$



So this is antiX ? You see a "sudo" group in the list: use "sudo" in a 55-myconf.pkla under /etc/polkit-1/… as previously presented. Then the user just has to add himself to the sudo group if he is not in yet.
Titre: Re : Problems with LXDE
Posté par: patrick013 le 05 juin 2013 à 23:42:46
What an improvement.     Working with Scorpio.

Installed obsession, fixed the pkla file, and Scorpio
now shutdown's with root windows open without
asking for the root password with both obsession and
pygtk-shutdown.

Contemplating changing  /home/user-oldgroup to
/home/user-wheel for my /home/user directory and files
but no problems yet with that.

Thanks a bunch Melodie,

Patrick      :D
Titre: Re : Problems with LXDE
Posté par: melodie le 06 juin 2013 à 00:00:55
Hi Patrick,

Welcome.

Changing the ownership of files or directories is not what I was talking about. To add a user to a group the command as root is "gpasswd -a <user> <group>".

This is what I was talking about.

Titre: Re : Problems with LXDE
Posté par: djohnston le 06 juin 2013 à 00:06:19
So this is antiX ? You see a "sudo" group in the list: use "sudo" in a 55-myconf.pkla under /etc/polkit-1/… as previously presented. Then the user just has to add himself to the sudo group if he is not in yet.

No, not AntiX. Straight Debian. I believe the sudo group is added for Remastersys's live CD session. But, you still don't need to be a member of the sudo group to logout/restart/shutdown. It's just not necessary.

There's something added by the installation of LightDM, (which is included in the standard Debian installation), that enables the consolekit access for a regular user. I just haven't discovered what it is, yet. I know this because I lost consolekit access when I removed LightDM and used ~/.xinitrc to startx on user login. I could logout normally, but not shutdown or reboot. I added exec ck-launch-session jwm to the .xinitrc, but still wasn't working. After about 3 hours of web searching and trying different approaches to the problem, I threw in the towel and reinstalled LightDM.

For the record, AntiX uses Slim display manager instead of LightDM.
Titre: Re : Problems with LXDE
Posté par: djohnston le 06 juin 2013 à 00:11:36
Contemplating changing  /home/user-oldgroup to /home/user-wheel for my /home/user directory and files
but no problems yet with that.

Patrick, that's not a good idea. The /home/user-oldgroup files and directories should belong to user-oldgroup, or to another normal user. But, not to wheel. Wheel is a reserved group with elevated system privileges and should not be the owner of any files in the /home directory structure.

Titre: Re : Problems with LXDE
Posté par: melodie le 06 juin 2013 à 00:20:51
Patrick, that's not a good idea. The /home/user-oldgroup files and directories should belong to user-oldgroup, or to another normal user. But, not to wheel. Wheel is a reserved group with elevated system privileges and should not be the owner of any files in the /home directory structure.

Exactly.

Generally speaking the ownership configured normally by the system for the files and the directories should never be changed.

In Archlinux, the files which belong to the user used to belong to "user:group" which was for example "melodie:users". Later, it became as in Ubuntu : "melodie:melodie" and since it has been "melodie:users" again. In Slackware and derived, it's also "user:users".

If a file or directory has the wrong permission, because, let's say, you created it as root, then you will need to change the ownnership in a way which will allow you to manage it as user : the ones in your home, of course!



Titre: Re : Problems with LXDE
Posté par: patrick013 le 06 juin 2013 à 00:58:09

Changing the ownership of files or directories is not what I was talking about. To add a user to a group the command as root is "gpasswd -a <user> <group>".

This is what I was talking about.

That command helps.    I'm able to get into the users group and the wheel
group at the same time.    gnome-user-settings would only do one or the other.

thx

patrick
Titre: Re : Problems with LXDE
Posté par: melodie le 06 juin 2013 à 01:08:41
<user> stands for your username and <group> for your group. Usually you are already member of the group users : it's the default and minimum in all distros, AFAIK.

And it allows adding your user to one group at same time only. (Sorry but " I'm able to get into the users group and the wheel group at the same time. " does not make sense to me... )

Titre: Re : Problems with LXDE
Posté par: patrick013 le 06 juin 2013 à 01:27:05
And it allows adding your user to one group at same time only. (Sorry but " I'm able to get into the users group and the wheel group at the same time. " does not make sense to me... )
guest:x:1000:guest
wheel:x:1001:guest

According to my /etc/group    I'm a member of both groups OK .
That's what I meant.    See above code.    I think that's what is
needed for that to be 100% right.

thx

patrick
Titre: Re : Problems with LXDE
Posté par: Taco.22 le 06 juin 2013 à 04:48:53
For some reason now obsession won't show icons on the logout dialogue box - it used to.  Not sure what I did.  I'm running Openbox with spacefm, greybird gtk theme, meliaeSVG icon theme - otherwise bog-standard VillageBox.  Obsession has it's own icons in /usr/local/share/obsession/images, and I have tried swapping the system icons and theme around.  Even reinstalled obsession.  The .desktop file is set to NoDisplay=true, but changing that makes no difference.  Any ideas?
Titre: Re : Problems with LXDE
Posté par: melodie le 06 juin 2013 à 16:16:26
guest:x:1000:guest
wheel:x:1001:guest

According to my /etc/group    I'm a member of both groups OK .
That's what I meant.    See above code.    I think that's what is
needed for that to be 100% right.

is "guest" your username ?

wheel is a group which allows a given user to have all rights and permissions.

See here for more information:
http://en.wikipedia.org/wiki/Wheel_%28Unix_term%29 (http://en.wikipedia.org/wiki/Wheel_%28Unix_term%29)

and here if you like little stories:
http://administratosphere.wordpress.com/2007/07/19/the-wheel-group (http://administratosphere.wordpress.com/2007/07/19/the-wheel-group)

For some reason now obsession won't show icons on the logout dialogue box - it used to.Any ideas?

I would try to copy the content of the /usr/local/share/obsession/images directly to /usr/share/pixmaps. (directly : not under a sub-directory). My guess is your default icon theme might not have the icons for shutdown and so on, or maybe not with the same file names. If this is the good guess, then /usr/share/pixmaps or /usr/share/icons as a place for the obsession image files could fix it.






Titre: Re : Problems with LXDE
Posté par: mimas le 06 juin 2013 à 16:53:50
Obsession supplies fallback icons in DATA_DIR_PREFIX/share/obsession/images (DATA_DIR_PREFIX is set to /usr/local by default but it can be changed before compilation by 'make configure' command*)

I don't know how the package is built. Obsession-logout takes "system-shutdown", "gnome-session-reboot", "gnome-session-suspend", "gnome-session-hibernate", "gnome-session-switch" and "system-log-out" from stock icons (the theme) before falling back to packaged icons. If there are no icons, it should be a compilation issue, or a path issue or... i don't know.

Did you try to put icons in the /usr/share/obsession/images and /usr/local/share/obsession/images to see if they are displayed?

>  I believe the source code for /usr/bin/lxsession-logout is part of what mimas used to create the obsession package. Very clever, that genius.

Dwarfs standing on the shoulders of giants. :)

* Look at INSTALL (https://code.google.com/p/mimarchlinux/source/browse/INSTALL?repo=obsession).
Titre: Re : Problems with LXDE
Posté par: patrick013 le 06 juin 2013 à 22:38:59
is "guest" your username ?

Yes, group guest includes member guest, and group wheel includes
member guest.    The pkla file works with wheel then as the unix group.

The way it is any user can run "su" to get root privileges.    That's OK too.
Or restrict "su" to the wheel group, but I don't need that today.

thx

patrick
Titre: Re : Re : Problems with LXDE
Posté par: djohnston le 06 juin 2013 à 23:38:33
Yes, group guest includes member guest, and group wheel includes member guest.

Patrick,

I am struggling to understand how your installation is set up. Are you talking about a live CD session or a full installation to hard drive? If this is an installation, you should not have to use the guest account. Create a new user account for yourself with a unique name (not root, guest, wheel, admin). Just like the group wheel, guest is a system reserved account name. Guest is meant to have extremely limited privileges. Under no circumstances should the guest account be a member of the group wheel. By doing so, you have given the guest account, which is meant to have limited privileges, full system access by being a member of the group wheel.

Titre: Re : Problems with LXDE
Posté par: Taco.22 le 07 juin 2013 à 01:10:34
re: obsession

I just did a launch in terminal and got -
/usr/share/shearwater/gtk-2.0/gtkrc:339: Unable to locate image file in pixmap_path: "panel-bg-dark.png"
The icons are at /usr/local/share/obsession/images so I'll try relocating them to /usr/share/pixmaps and see how it goes.
Titre: Re : Re : Re : Problems with LXDE
Posté par: patrick013 le 07 juin 2013 à 02:05:14
I am struggling to understand how your installation is set up. Are you talking about a live CD session or a full installation to hard drive? If this is an installation, you should not have to use the guest account.

When I installed this to the flash drive, full install, I made myself a user
in group "guest" user name "guest"  group number 1000.    I could setup
a different group for each user, like group"guest1"  user name "guest1"
group number 2000  and so forth.    Setting up normal users is very flexible.

Being in the Wheel group does not give user "guest" root power, already
tried it, had to enter the root password for that.    So the root password is
req'd for everyone in group wheel to run root programs as usual.     Without
the root password I can't do anything, if in the wheel group or not.

So it should be safe to use the wheel group.    Additional config to wheel
would be req'd to give everybody in there root powers without the root
password,  make it a group equal to root:root somehow.

thanks for the response.

patrick
Titre: Re : Problems with LXDE
Posté par: melodie le 07 juin 2013 à 02:45:03
I know this because I lost consolekit access when I removed LightDM and used ~/.xinitrc to startx on user login. I could logout normally, but not shutdown or reboot. I added exec ck-launch-session jwm to the .xinitrc, but still wasn't working. After about 3 hours of web searching and trying different approaches to the problem, I threw in the towel and reinstalled LightDM.

For the record, AntiX uses Slim display manager instead of LightDM.

Then try again but with:
exec dbus-launch ck-launch-session jwm
in your ~/.xinitrc

I had to do it this way in Archlinux. (And you need to check if you have seats in your session, as simple user "ck-list-sessions".)

But Archlinux has moved so fast to systemd…  ConsoleKit isn't used anymore in the current Archlinux.




Titre: Re : Re : Problems with LXDE
Posté par: melodie le 07 juin 2013 à 02:48:06
re: obsession

I just did a launch in terminal and got -
/usr/share/shearwater/gtk-2.0/gtkrc:339: Unable to locate image file in pixmap_path: "panel-bg-dark.png"
The icons are at /usr/local/share/obsession/images so I'll try relocating them to /usr/share/pixmaps and see how it goes.

Yes, and if that does not work (you might need to logout/login in between? Not sure about that) you can try /usr/share/icons and also what mimas suggested above:
Citer
Did you try to put icons in the /usr/share/obsession/images and /usr/local/share/obsession/images to see if they are displayed?

Titre: Re : Problems with LXDE
Posté par: patrick013 le 07 juin 2013 à 02:52:58
guest:x:1000:guest
wheel:x:1001:
polkituser:x:1002:guest

@dj

The obsession logout works also with the polkituser group setup in /etc/group.
Reply 32 this thread has two links from Melodie about the "archaic"
wheel group.

Just FYI

Patrick
Titre: Re : Re : Problems with LXDE
Posté par: djohnston le 07 juin 2013 à 05:33:11
@dj

The obsession logout works also with the polkituser group setup in /etc/group. Reply 32 this thread has two links from Melodie about the "archaic" wheel group.
I think you mean reply #31. In any case, the "archaic" link Mel posted (https://administratosphere.wordpress.com/2007/07/19/the-wheel-group/) goes on to say this:

Citer
The wheel group is, perhaps, not widely used today, or is seen as “archaic” and irrelevant. Nothing could be further from the truth.
The article goes on to say,

Citer
Is it any wonder that GNU/Linux systems don’t enable the wheel group by default?
You are right, though. The wheel group is meant to limit the users who can su to the root account, as explained on one of Slackbook pages (http://alien.slackbook.org/dokuwiki/doku.php?id=linux:admin):

Citer
The wheel group is a legacy from UNIX. When a server had to be maintained at a higher level than the day-to-day system administrator, root rights were often required. The 'wheel' group was used to create a pool of user accounts that were allowed to get that level of access to the server. If you weren't in the 'wheel' group, you were denied access to root.
Coming from a UNIX background before ever seeing Linux, I was looking at the wheel group in that context. I was looking at it the wrong way, though. Thanks for setting me straight. However, and this is where it gets a bit sticky, you should be able to logout/shutdown/reboot as a normal user in Debian, even as the user guest. Here's a guy (http://forums.debian.net/viewtopic.php?t=85433) who was trying to disable that feature in wheezy:

Citer
I installed 6.0.something wheezy, and i want to create a guest user without the privilege to shutdown/reboot my computer.
So, now I am unsure as to where your original problem with logging out originated from. I am not a member (http://linuxvillage.net/index.php/topic,378.msg2561.html#msg2561) of the group wheel or sudo or polkituser, yet I am able to logout/shutdown/reboot as a normal user. As a matter of fact, the groups wheel and polkituser do not even exist (http://linuxvillage.net/index.php/topic,378.msg2577.html#msg2577) in my installation(s).

Of course, you are free to setup your installation however you see fit. I should have no say in what you do unless it affects me in some way. I just don't understand why you are using the guest account to login as a regular user. It seems foreign to me.
Titre: Re : Re : Re : Problems with LXDE
Posté par: patrick013 le 07 juin 2013 à 06:55:00
I am not a member of the group wheel or sudo or polkituser, yet I am able to logout/shutdown/reboot as a normal user. As a matter of fact, the groups wheel and polkituser do not even exist (http://linuxvillage.net/index.php/topic,378.msg2577.html#msg2577) in my installation(s).
My LXDE came straight from Debian, Scorpio from LinuxVillage.
You must not have "root" programs open when shutting down or
have sudo in the  command line.     Beats me ?     Some library
nobody else has ?     Some Polkit option set ?

I just don't understand why you are using the guest account to login as a regular user. It seems foreign to me.
In the full installs I do :

guest:x:1000:guest          (the normal user I login with)
or
users:x:100:patrick          (my user if in the users group)

are both the same in the sense that neither interfere with
system or root or admin groups and are seen by the system
as normal users in normel groups.    I could put many users
in group 1000 with any name as normal non-root users.

Have a good one.

Patrick
Titre: Re : Re : Re : Re : Problems with LXDE
Posté par: djohnston le 07 juin 2013 à 14:06:44
My LXDE came straight from Debian, Scorpio from LinuxVillage. You must not have "root" programs open when shutting down or have sudo in the  command line.     Beats me ?     Some library nobody else has ?     Some Polkit option set ?
Okay, I took the plunge. I installed Scorpio from the Scorpio_2013-2 iso image (http://tyruiop.eu/~melodie/Downloads/ISOS/Debian/Scorpio_2013-2.iso). Is that the one you used? On installation, I added a normal user named "darrel". On first boot after installation, I opened a terminal, and as root did: apt-get update, then apt-get dist-upgrade. After the upgrade, I installed Synaptic, then rebooted.

After rebooting, I started Synaptic and installed the lxde desktop. I did not install lxde (metapackage) or task-lxde-desktop (metapackage). I selected the lxde-common package and accepted all the recommended dependencies. Whatever other LXDE packages were still unmarked I selected for installation, except lxmusic and lxpolkit. Then I closed Synaptic and logged out. LXDE is now the default Xsession. At the LightDM login window, I can select Default Xsession or LXDE and I will get the same result. I logged in as user "darrel". After about a minute, I clicked the red logout button in the far right corner of the lxpanel. This brought up the lxde-session window and I selected Reboot. The machine rebooted.

I logged in as user darrel again and opened a terminal. After su'ing to root, I created the user "guest".

root@Scorpio:~# useradd -d /home/guest -m guest

Notice I did not specify any groups to add the user guest to. I only specified the home directory and the switch to create the directory. Next, I set a password for user guest.

root@Scorpio:~# passwd guest
Enter new UNIX password:
Retype new UNIX password:
passwd: password updated successfully
root@Scorpio:~#


After ending root's terminal session, I logged out and logged in as user guest. After about a minute, I clicked the red logout button in the far right corner of the lxpanel. This brought up the lxde-session window and I selected Reboot. The machine rebooted.

Here are the groups user guest belongs to:

guest:x:1001:

Yet, user guest is able to logout, reboot and shutdown the machine. Here are the groups user darrel belongs to:

dialout:x:20:darrel
cdrom:x:24:darrel
floppy:x:25:darrel
audio:x:29:darrel
video:x:44:darrel
plugdev:x:46:darrel
netdev:x:113:darrel
vboxsf:x:119:darrel
darrel:x:1000:

The vboxsf group is for the VBox shared folder service. User darrel is not a member of sudo, polkituser or wheel. As a matter of fact, there is no polkituser or wheel group.

root:x:0:
daemon:x:1:
bin:x:2:
sys:x:3:
adm:x:4:
tty:x:5:
disk:x:6:
lp:x:7:
mail:x:8:
news:x:9:
uucp:x:10:
man:x:12:
proxy:x:13:
kmem:x:15:
dialout:x:20:darrel
fax:x:21:
voice:x:22:
cdrom:x:24:darrel
floppy:x:25:darrel
tape:x:26:
sudo:x:27:
audio:x:29:darrel
dip:x:30:
www-data:x:33:
backup:x:34:
operator:x:37:
list:x:38:
irc:x:39:
src:x:40:
gnats:x:41:
shadow:x:42:
utmp:x:43:
video:x:44:darrel
sasl:x:45:
plugdev:x:46:darrel
staff:x:50:
games:x:60:
users:x:100:
libuuid:x:101:
crontab:x:102:
avahi-autoipd:x:103:
scanner:x:104:saned
messagebus:x:105:
colord:x:106:
lpadmin:x:107:
ssl-cert:x:108:
Debian-exim:x:109:
mlocate:x:110:
ssh:x:111:
netdev:x:113:darrel
bluetooth:x:114:
saned:x:115:
fuse:x:116:
lightdm:x:117:
utempter:x:118:
vboxsf:x:119:darrel
debian-xfs:x:121:
ntp:x:120:
nogroup:x:65534:
darrel:x:1000:
guest:x:1001:

Again, this is an LXDE installation to Taco.22's Scorpio 2013.2 remaster. I employed no trickery. There are no "magic" groups. Just a standard straightforward install, with the exception of manually adding user guest.

Also notice that user darrel's UID (user ID) is 1000 and that user guest's UID is 1001. If I create another user, the default UID will be 1002, unless I specify a different UID when creating the new user.

Without knowing more about how you did the installation and what steps you took to create multiple guest users, I could only guess as to what caused your original problem with being able to log out. You say that a program is "running as root" when you logout. If by that you mean that there is an application that you manually started as user root, then I fail to see why you would want to leave it running during a logout, reboot or shutdown. If you mean that there are system services that were started by user root, that is normal and is part of the sysvinit bootup process.

Titre: Re : Re : Problems with LXDE
Posté par: djohnston le 07 juin 2013 à 14:12:06
Then try again but with:
exec dbus-launch ck-launch-session jwm
in your ~/.xinitrc

Pretty sure I already tried that, but I'll uninstall LightDM and try it again. I'm pretty sure the authorization is coming from PAM rules that LightDM (and probably other display managers) install. Just haven't narrowed it down yet. This may all be moot anyway, as I intend to use mimas's obsession. So, I'm off to try that.

Titre: Re : Re : Re : Problems with LXDE
Posté par: melodie le 07 juin 2013 à 15:35:03
Pretty sure I already tried that, but I'll uninstall LightDM and try it again. I'm pretty sure the authorization is coming from PAM rules that LightDM (and probably other display managers) install. Just haven't narrowed it down yet. This may all be moot anyway, as I intend to use mimas's obsession. So, I'm off to try that.

Can you post the /etc/pam.d/lighdm file ? We could try to study it's content. I have not enough knowledge about PAM yet and this would be an opportunity to have a close look on this specific issue.





Titre: Re : Re : Re : Re : Re : Problems with LXDE
Posté par: patrick013 le 07 juin 2013 à 21:21:10
Without knowing more about how you did the installation and what steps you took to create multiple guest users, I could only guess as to what caused your original problem with being able to log out. You say that a program is "running as root" when you logout. If by that you mean that there is an application that you manually started as user root, then I fail to see why you would want to leave it running during a logout, reboot or shutdown. If you mean that there are system services that were started by user root, that is normal and is part of the sysvinit bootup process.
guest:x:1000:guest
wheel:x:1001:
polkituser:x:1002:guest

With guest as a member of group 1000 and also a member of group 1002
I am able to use Melodie's .pkla file and shutdown when there are root
programs open.    Which is what I wanted to do anyway.

The install was a remaster and reinstall of an original Scorpio from Taco.
The iso was like 1 GB, too big for a remaster IMO.    But it will shutdown
when I close root programs, now it shutdowns when I don't.

Try it, copy the 55-myconf2.pkla file to your install and setup the group
for polkituser, add yourself as user there, and it will shutdown when root
programs are open and running.

Shutdown LXDE when root programs are open (http://linuxvillage.net/index.php/topic,378.msg2553.html#msg2553)

Have a good one,

Patrick
Titre: Re : Problems with LXDE
Posté par: djohnston le 08 juin 2013 à 05:58:42
I do intend to take advantage of mimas's obsession package. Anything that makes things simpler is best, in my opinion. And consolekit is anything but simple.
Done. Works like a charm!

Thanks, mimas!!


(http://s19.postimg.org/wqf3j96vz/VSLV02.jpg) (http://postimg.org/image/wqf3j96vz/)

Titre: Re : Problems with LXDE
Posté par: Taco.22 le 08 juin 2013 à 07:07:07
Yeah, mine used to look like that!  Don't know what went wrong but I now have those icons installed into a rather large number of places and they still won't show up.  Did you use the Debian compiled or the source with installer?
Titre: Re : Re : Problems with LXDE
Posté par: djohnston le 08 juin 2013 à 10:42:04
Did you use the Debian compiled or the source with installer?

I had to use the source to change "Openbox" to "JWM" in the displayed message. Then just do: $make #make install. The icons you see in the screenshot aren't the ones mima supplied. However, I got them to show up by copying them from /usr/local/share/obsession/images to /usr/share/pixmaps. After installing, I discovered the Logout function called by obsession isn't working in JWM. Kinda weird.
Titre: Re : Problems with LXDE
Posté par: Taco.22 le 08 juin 2013 à 12:26:21
Ahh, it just all got too hard!!  I'm just going to stick to the logout commands in Openbox root menu as written in menu.xml.  Simple, precise and trouble-free - no need for a GUI.
Titre: Re : Re : Problems with LXDE
Posté par: melodie le 08 juin 2013 à 17:17:52
Ahh, it just all got too hard!!  I'm just going to stick to the logout commands in Openbox root menu as written in menu.xml.  Simple, precise and trouble-free - no need for a GUI.

You both are talking about two different types of desktops. I don't quite see what is so hard? Is it about the icons? I was almost sure that having them directly under /usr/share/pixmaps would solve it, as djohnston confirms. Up to now any icon trouble was solved without problem by doing so.

For me it's not just the gui, it's nice looking and gives even more a feeling of having a real Desktop environment and it has also made my main menu shorter, I like it this way. :)




Titre: Re : Problems with LXDE
Posté par: Taco.22 le 09 juin 2013 à 02:35:46
I used the Debian configured version, and I have put those icons EVERYWHERE, and they still don't show up on the obsession menu!!  I've tried the installer a couple of times but I'm getting config errors.  However this is all for a Spacefm based "desktop" which I'm having second thoughts about.  There is a reason why I developed Scorpio as it is - it is, to my mind, the "ideal" Openbox setup; in fact the "ideal" OS.
Titre: Re : Re : Problems with LXDE
Posté par: djohnston le 09 juin 2013 à 04:46:15
I'm just going to stick to the logout commands in Openbox root menu as written in menu.xml.  Simple, precise and trouble-free - no need for a GUI.

I'm considering doing the same thing. Only it will be in ~/.jwmrc (which is written in XML). I previously had the menu set up that way.

Titre: Re : Re : Problems with LXDE
Posté par: mimas le 09 juin 2013 à 12:27:55
@djohnston,
Thanks for the banner. :D

> After installing, I discovered the Logout function called by obsession isn't working in JWM. Kinda weird.

Do you use obsession-exit?
If some actions aren't display in obsession-logout, maybe you could try 'obsession-exit -c' to see what power functions are detected (it shares the same code with obsession-logout).

Here I've got :
$ obsession-exit -c
Capabilities:
  Shutdown
  Reboot
  Suspend
  Hibernate
  User switch

edit : quote fixed
Titre: Re : Problems with LXDE
Posté par: Taco.22 le 09 juin 2013 à 14:18:07
Hi mimas,

I don't have any problems with obsession working - I use the command "obsession-logout" and the resulting pop-up dialogue box is fully functional.  My issue is that the icons aren't present in that box.  I think they were initially but somewhere along the line they disappeared.  As I've said before, I can't get them to appear, regardless of where I put icons - I even installed the gnome-icon-theme just in case.  Now, this isn't straight Debian Openbox - I have Spacefm controlling the "desktop" ala LXDE but without the LXDE metapackage, so who knows what may have happened under the bonnet. 
Titre: Re : Problems with LXDE
Posté par: mimas le 09 juin 2013 à 14:29:56
Yes, I was lost in the quotes.
Titre: Re : Re : Problems with LXDE
Posté par: melodie le 09 juin 2013 à 15:42:27
so who knows what may have happened under the bonnet.

Hi Taco,

I suppose you checked the rights and permissions of your icons where ever you put them? Where is that version of your's now, is it possible to download it to try it?

Titre: Re : Re : Re : Re : Problems with LXDE
Posté par: djohnston le 11 juin 2013 à 09:20:52
Can you post the /etc/pam.d/lighdm file ?

I replaced LightDM with Slim, so I'll have to take the files from the standard Debian LXDE install.

/etc/pam.d/lightdm

#%PAM-1.0
auth    requisite       pam_nologin.so
auth    required        pam_env.so readenv=1
auth    required        pam_env.so readenv=1 envfile=/etc/default/locale
#auth    sufficient      pam_thinkfinger.so
@include common-auth
auth    optional        pam_gnome_keyring.so
@include common-account
# SELinux needs to be the first session rule. This ensures that any
# lingering context has been cleared. Without out this it is possible
# that a module could execute code in the wrong domain.
# When the module is present, "required" would be sufficient (When SELinux
# is disabled, this returns success.)
session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close
session required        pam_limits.so
session required        pam_loginuid.so
@include common-session
# SELinux needs to intervene at login time to ensure that the process
# starts in the proper default security context. Only sessions which are
# intended to run in the user's context should be run after this.
session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open
# When the module is present, "required" would be sufficient (When SELinux
# is disabled, this returns success.)
session optional        pam_gnome_keyring.so auto_start
@include common-password

Since common-auth, common-account, common-session and common-password are called, I'll post the contents of those.

/etc/pam.d/common-auth

#
# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.).  The default is to use the
# traditional Unix authentication mechanisms.
#
# As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
# To take advantage of this, it is recommended that you configure any
# local modules either before or after the default block, and use
# pam-auth-update to manage selection of other modules.  See
# pam-auth-update(8) for details.

# here are the per-package modules (the "Primary" block)
auth [success=1 default=ignore] pam_unix.so nullok_secure
# here's the fallback if no module succeeds
auth requisite pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
auth required pam_permit.so
# and here are more per-package modules (the "Additional" block)
auth optional pam_cap.so
# end of pam-auth-update config

/etc/pam.d/common-account

#
# /etc/pam.d/common-account - authorization settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authorization modules that define
# the central access policy for use on the system.  The default is to
# only deny service to users whose accounts are expired in /etc/shadow.
#
# As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
# To take advantage of this, it is recommended that you configure any
# local modules either before or after the default block, and use
# pam-auth-update to manage selection of other modules.  See
# pam-auth-update(8) for details.
#

# here are the per-package modules (the "Primary" block)
account [success=1 new_authtok_reqd=done default=ignore] pam_unix.so
# here's the fallback if no module succeeds
account requisite pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
account required pam_permit.so
# and here are more per-package modules (the "Additional" block)
# end of pam-auth-update config

/etc/pam.d/common-session

#
# /etc/pam.d/common-session - session-related modules common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of modules that define tasks to be performed
# at the start and end of sessions of *any* kind (both interactive and
# non-interactive).
#
# As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
# To take advantage of this, it is recommended that you configure any
# local modules either before or after the default block, and use
# pam-auth-update to manage selection of other modules.  See
# pam-auth-update(8) for details.

# here are the per-package modules (the "Primary" block)
session [default=1] pam_permit.so
# here's the fallback if no module succeeds
session requisite pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
session required pam_permit.so
# and here are more per-package modules (the "Additional" block)
session required pam_unix.so
# end of pam-auth-update config

/etc/pam.d/common-password

#
# /etc/pam.d/common-password - password-related modules common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of modules that define the services to be
# used to change user passwords.  The default is pam_unix.

# Explanation of pam_unix options:
#
# The "sha512" option enables salted SHA512 passwords.  Without this option,
# the default is Unix crypt.  Prior releases used the option "md5".
#
# The "obscure" option replaces the old `OBSCURE_CHECKS_ENAB' option in
# login.defs.
#
# See the pam_unix manpage for other options.

# As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
# To take advantage of this, it is recommended that you configure any
# local modules either before or after the default block, and use
# pam-auth-update to manage selection of other modules.  See
# pam-auth-update(8) for details.

# here are the per-package modules (the "Primary" block)
password [success=1 default=ignore] pam_unix.so obscure sha512
# here's the fallback if no module succeeds
password requisite pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
password required pam_permit.so
# and here are more per-package modules (the "Additional" block)
password optional pam_gnome_keyring.so
# end of pam-auth-update config
Titre: Re : Re : Re : Problems with LXDE
Posté par: djohnston le 11 juin 2013 à 09:27:49
Do you use obsession-exit?
If some actions aren't display in obsession-logout, maybe you could try 'obsession-exit -c' to see what power functions are detected (it shares the same code with obsession-logout).
I don't remember. I tried one of the two. I'll try again, using both. The actions are all displayed as shown in the screenshot (http://postimg.org/image/wqf3j96vz/). Although Shutdown, Reboot and Cancel worked fine, Logout didn't. (From the window's title, I think it's obsession-logout.)
Titre: Re : Problems with LXDE
Posté par: mimas le 11 juin 2013 à 09:56:03
Obsession-exit is a CLI version of obsession-logout but It was broken until a few days ago.

I released a new version of obsession : http://code.google.com/p/mimarchlinux/downloads/list (http://code.google.com/p/mimarchlinux/downloads/list) (nothing has been done to obsession-logout).

Titre: Re : Re : Problems with LXDE
Posté par: djohnston le 11 juin 2013 à 11:22:22
Obsession-exit is a CLI version of obsession-logout but It was broken until a few days ago.
I released a new version of obsession : http://code.google.com/p/mimarchlinux/downloads/list (http://code.google.com/p/mimarchlinux/downloads/list) (nothing has been done to obsession-logout).

Okay. I got the new one and I'll compile that. Bear in mind this is for a JWM desktop with no LXDE or Openbox sessions running or installed. From what I can gather, JWM isn't XDG compliant, so xdg-autostart may come in handy.

Titre: Re : Problems with LXDE
Posté par: mimas le 11 juin 2013 à 18:01:36
> Bear in mind this is for a JWM desktop with no LXDE or Openbox sessions running or installed.

Obsession is not really Openbox related, it's mostly a tool to manage Systemd, Upower and ConsoleKit session commands with graphic or console interface. Maybe I should have named it suc-session (for Systemd, Upower and ConsoleKit). :) The GUI version also manage the switch user thing provided by the xDM family (LXDM, GDM, KDM, LightDM).

Obsession also brings a modern way to autostart programs with xdg-autostart.

All of these tools can be used with other windows managers that don't have session management .
Titre: Re : Re : Re : Re : Re : Problems with LXDE
Posté par: melodie le 11 juin 2013 à 18:25:13
I replaced LightDM with Slim, so I'll have to take the files from the standard Debian LXDE install.

I am trying to scroll up in the former posts related to the same issue but I can't get into it clearly. If you are still interested (I am but I don't know how much time this could take), then would you open a new thread, resume the start middle and latest? If you don't have time for this, we could give up.