Incomplete logout with Gnome/systemd

Hey,
I'm using Gnome 3.6 from the testing repositories. That is because with the current stable version (3.4) custom shortcuts and media keys do not work on my system. But I don't think the version of Gnome does matter, since I experienced the same issue with Gnome 3.4. Also, I'm using systemd, the OS is only installed for a week now.
When I log off (via the Gnome menu) and get to the login screen, I cannot shutdown or restart the system without providing root authentication. My root user doesn't have a password since I'm using sudo, so I have to login again and use shutdown/restart from the menu.
The authentication dialog tells me, I need to authenticate to shutdown while there are still users logged in. However, no one else should be logged in, since I'm using the PC alone. So there really is no reason to ask for authentication. If I log in via terminal, the following users are on the system:
$ who
(unknown) :1 2012-10-25 18:02 (:1)
joker tty2 2012-10-25 18:05
$ users
(unknown) joker
joker is my local user which I logged in as on the terminal. As I understand, (unknown) is the gdm instance. So everything seems to be right. Still, Gnome wants me to authenticate after I logged out of the terminal session again.
https://bugs.archlinux.org/task/30529 seems to fit my problem, but killing pulseaudio does not help in my case. I also tried changing the polkit policies in vim /usr/share/polkit-1/actions/org.freedesktop.consolekit.policy to allow shutdown and restart without authentication even if multiple users are still logged in. But that didn't change anything either.
Can anyone help me with this? Just tell me what additional data you might need.
Thanks in advance!
Last edited by haellowyyn (2012-11-05 19:20:55)

maybe tracker-miner-fs is still running? If yes, vote for bug
https://bugs.archlinux.org/task/30529
problem with pulseaudio was solved with the mentioned configuration, but since gnome-3.6 there seems to be a bug in gvfs that keeps tracker-miner-fs from exiting with session.
This is IMO no more a [testing] thread.
john_h wrote:Alas, hasn't solved it for me.
Last edited by Heinrichmeyer (2012-11-08 08:34:37)

Similar Messages

OS crashed and cannot switch to console model when logout from gnome

after update gnome to 3.2, when I logout login account or switch user with gnome. the os dead.
I have to reset pc to reboot it.
should this isskue relate to gnome update?

What do you mean by "dead"? For me, dead is complete system freeze. Are you thrown to a TTY console? Is it just a blinking cursor? What's the problem?

Xfce-session-logout from gnome-panel

hello i use xfce...i got tired of xfce taskbar and i installed gnome-panel
but when i click on system and then log out
nothing happens
i made a launcher to log out.. but i would like to hit System and Log out
How could i do that?
with this launcher im able to logout
[Desktop Entry]
Version=1.0
Encoding=UTF-8
Type=Application
Name=xfce4-session-logout
Comment=xfce4-session-logout
Categories=Application;GNOME;GTK;Core;Utility;
Exec=xfce4-session-logout
Icon=application-exit
Terminal=false
StartupNotify=false
GenericName=xfce session logout
OnlyShowIn=GNOME;
StartupNotify=true
NoDisplay=true
but i would like to log out from hitting system option then log out
http://img22.imageshack.us/img22/3959/menu002.png

#!bin/sh
#~/.xinitrc
#Executed by startx (run your window manager from here)
#exec wmaker
#exec startkde
#exec icewm
#exec blackbox
#exec fluxbox
exec ck-launch-session startxfce4
but thats not the problem..thanks anyway

[SOLVED] Autostarted programs not exiting on logout with openbox

Hi,
I'm pretty sure I'm just overlooking something obvious, but I simply can't find a solution to the following basic problem. I'm using a simple openbox session started from xdm (also tried lightdm with the same results). In case of xdm, I'm using a .xsession file to start openbox like this:
exec dbus-launch --exit-with-session openbox-session
In case of lightdm, it also works without a .xsession or .xinitrc file.
I'm using "~/.config/openbox/autostart" to start some tools upon login. Until now, I have only started programs which exit right away which worked fine. But now I'd like to use autostart to start a (non-X11) program which should continue to run until I log out. For testing this, I used a simple infinite loop script, let's call it "loop.sh". When I start loop.sh in autostart using "loop.sh &", this script continues to run even if I log out of openbox using the openbox menu. In fact, if I log out and log in multiple times, multiple instances will keep running forever. When I start loop.sh simply using "loop.sh", also the parent processes, namely "/bin/sh /usr/lib/openbox/openbox-autostart OPENBOX" and "sh /home/ochi/.config/openbox/autostart" continue to run.
What is the correct way to have all processes spawned during the X session killed upon logout?
For reference, this is the loop script I use:
#!/bin/bash
while true; do
# If you like, you can also play a sound for feedback.
#paplay /usr/share/sounds/freedesktop/stereo/complete.oga &
sleep 1
done
Update: Using gdm seems to "fix" the problem, i.e. all programs started by the autostart script seem to get killed correctly. However, gdm pulls a LOT of dependencies I don't want to have. I wonder what gdm does differently...
Last edited by Ochi (2015-04-18 23:38:21)

I continued to study this subject, and here is what I found at this time.
First I precise again that I use openbox launched by startx at login in tty.
When I exit openbox, I return to a -bash prompt, and I then can log out of tty.
After logging in into openbox, I have:
└─user.slice
└─user-1000.slice
├─[email protected]
│ ├─1421 /usr/lib/systemd/systemd --user
│ └─1422 (sd-pam)
└─session-c1.scope
├─1414 login -- berbae
├─1425 -bash
├─1432 /bin/sh /usr/bin/startx
├─1454 xinit /home/berbae/.xinitrc -- /etc/X11/xinit/xserverrc :0 vt1 -auth /tmp/serverauth.xxxxxxxxxx
├─1455 /usr/lib/xorg-server/Xorg -nolisten tcp :0 vt1 -auth /tmp/serverauth.xxxxxxxxxx
├─1459 /usr/bin/openbox --startup /usr/lib/openbox/openbox-autostart OPENBOX
├─1464 dbus-launch --sh-syntax --exit-with-session
├─1465 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
etc...
When I exit openbox, without logging out, I have:
└─user.slice
└─user-1000.slice
├─[email protected]
│ ├─1421 /usr/lib/systemd/systemd --user
│ └─1422 (sd-pam)
└─session-c1.scope
├─1414 login -- berbae
└─1425 -bash
If I ran something in background from konsole, when in openbox, this is not killed:
└─user.slice
└─user-1000.slice
├─[email protected]
│ ├─1421 /usr/lib/systemd/systemd --user
│ └─1422 (sd-pam)
└─session-c1.scope
├─1414 login -- berbae
├─1425 -bash
├─1296 /bin/bash /home/berbae/bin/loop.sh
└─1338 sleep 60
If I log out, the process is still not killed!
└─user.slice
├─user-1000.slice
│ ├─[email protected]
│ │ ├─517 /usr/lib/systemd/systemd --user
│ │ └─519 (sd-pam)
│ └─session-c1.scope
│ ├─1296 /bin/bash /home/berbae/bin/loop.sh
│ └─1338 sleep 60
As seen the '[email protected]' with the 'systemd --user' process is not ended too, even after logging out.
Edit: This is due to the session c1 still active; see next post.
I don't know if this is intentional, maybe it is a feature.
Now I found and propose a way to change this apparently default behavior, if it is not wanted.
First to end the 'systemd --user' process at logout, it is easy; just run:
$ systemctl --user enable exit.target
Edit: This is useless, sorry; see next post
Then to run a process in background, which should end when logging out, just launch it like this:
$ systemd-run --user loop.sh
This will launch the command 'loop.sh' as a service in the 'systemd --user' manager, instead of the 'session-c1.scope';
and it will be ended at logout, because the manager is now ended at logout, with the normal end of the manager.
Edit: see next post
I will continue studying this matter, to see if something else interesting can be found.
Edit: See the 'Edit:' lines above for the modifications, before the explanations in the next post.
Last edited by berbae (2015-04-16 14:38:35)

Any known problems with Gnome 2.28 before I update?

Hi, I would like know is there any known problems with Gnome 2.28?
I read that there are a login/logout time increased, something else?
Thanks in advance!

when I upgraded to 2.28, icons in the menu appeared and I'm not able to disable them... other than that gnome 2.28 seems fine to me.

Problem with Gnome and D-Bus

Hi to all, i have a problem with Gnome and D-Bus
Versions:
Arch Release: 0.7.2 Testing
Gnome: 2.14.1-2
D-Bus: 0.61-3
Screenshot explain all:
[URL=http://img366.imageshack.us/my.php?image=gpwned6be.jpg][/URL]

1>then i can't promote garnome on this forum??
yeah you can, but not as a solution to gnome related problem in arch. cause this doesn't resolve anything.
2>You don't have to, garnome2.14.2.1(481kb) download the patches and patch it automatically, just change install dir to /usr
(ONLY if you are using console-linux who want gnome a try). of course there is need small arch related patch.(in my experience 0)
eh, i haven't got a clue what this means, putting patches upstream means they will get include in gargnome and upstream releases. i only tried to say we put a lot of our free time in gnome for arch.
2-1>Well said, so choice is the each one's freedom.
and this category isn't arch, this is Desktop Environments,
i installed arch, BUT THAT DOESN'T MEANS I SHOULD USE gnome FROM ARCH!!!
agreed, but again then we won't support your desktop.
ARCH != gnome
3>some bug stuff about Xorg-7.0, include mine
http://bbs.archlinux.org/viewtopic.php?t=22210[/quote]
ah bugs.archlinux.org so it can be fixed.

No scrolling when viewing man pages with Gnome terminal?

Hi all,
I have just installed Oracle Solaris 11 on x86. For a long time I've used Solaris 9 on SPARC. I like the new OS, but I'm having a problem viewing man pages with Gnome terminal. When I view a long man page, e.g., "man newfs", I don't get a functional scroll bar on the right hand side of the window. And although the space bar works to advance the page, when I reach the end, it doesn't return to the command prompt. It just beeps, prints "END", and I can only exit by closing the window. Can anyone tell me how to fix this? Suggestions would be much appreciated.
Many thanks,
Chris Tidy

It does sound like you're using "less" instead of more. When you see the "(END)" prompt you can simply type "q" and it will exit back to the command line prompt making it unnecessary to close the window. See the "less" manual page for more detail on the less command. Under Solaris 9 the paging was done with the "more" command. If you set the PAGER environment variiable to "more" the man page will use more and revert to the behavior you'd be used to with Solaris 9. Less erases the text you've already read when you type that final "q" which is a behavior I don't like. I didn't bother to determine if there is a way to fix that with less, I just went back to more. The choice between "more" and "less" is a personal preference.

[Solved] Pulse Audio won't work on newly installed system with Gnome

About a year ago I got a new computer and more or less retired my old one with my first arch install. Recently, I decided I would set it up as a Linux system for my sister. I first updated the computer, which broke it royally (since it was last updated before the /bin symlinking happened) but I eventually got it fixed. However, after doing that, Pulse Audio wouldn't work, then I broke X and decided to do a full reinstall.
Now, on this clean install, Pulse is again not working. I have set up Gnome and gdm to work, and everything works great except Pulse. The wiki says that Pulse with Gnome 3 requires no extra setup, so I have not edited conf files at all. I have, however, installed "pulseaudio-alsa", which created this conf file:
# Use PulseAudio by default
pcm.!default {
type pulse
fallback "sysdefault"
hint {
show on
description "Default ALSA Output (currently PulseAudio Sound Server)"
ctl.!default {
type pulse
fallback "sysdefault"
# vim:set ft=alsaconf:
which seems fairly standard. Anyway, I tried removing it and had the same problems. When I have Pulse Audio running and try to play sound, I get the error:
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
Playback open error: -16,Device or resource busy
which is obviously trying for ALSA, or from mplayer:
AO: [pulse] Init failed: Connection refused
Running "pacmd list" nets me:
Daemon not responding.
and pavucontrol gives me:
Fatal Error: Unable to connect to PulseAudio: OK
when I try to start it.
No pulseaudio commands seem to work (e.g. pulseaudio -k). They don't raise any errors, but also it doesn't have any effect on the server.
The only asound conf file is "/etc/asound.conf", clearing ~/.config/pulse does not fix the issue.
Journalctl does not seem to give anything interesting (Stale PID is the only message when starting Pulse), though admittedly I'm just vgrepping all of journalctl since I don't know how to narrow it down more, nor does the output from pulseaudio -vvvv. There are a lot of errors in pulseaudio -vvvv, but they all appear to be related to loading devices that don't exist, and so I assume not a problem, I can post it if necessary. Sometimes when I kill Pulse the process refuses to go away and I have to reboot in order to clear the process out, but I don't think that's related.
If I kill Pulse or keep it from starting on boot, I can play sound, but only through ALSA, and while I didn't have the problem I expected (I can still play multiple things simultaneously) there's still the issue that the volume buttons in Gnome will no longer work and that the volume levels ALSA reports are basically nonsense to a human being.
I basically just blurbed everything I thought of/found on the wiki or forums, and I'm not really sure where to go from here. It's a fairly old computer, so that could be related, and I'd be willing to dump Pulse if Gnome could integrate well with ALSA, but obviously fixing Pulse would be the preferred option.
Any suggestions on where to look next? I've run out of ideas.
Thanks.
Last edited by HuFlungDu (2014-01-07 19:52:11)

Wonder if you have a conflict between two audio cards ... for example, I have a friend with some PulseAudio problems caused by conflict between the HDMI audio from his graphics card and his onboard sound. Something would switch PulseAudio to the wrong card and it would just quit after getting itself into a twist. Unsolved, I'm afraid, but have a look at commands such as:
aplay -l
pactl list sinks
pactl stat
(Latter two will need PulseAudio coaxed into life first)
and of course, the Arch wiki.
If there is a conflict, blacklisting kernel modules might also be needed.

Help required with Gnome 3 Input Sources

I used CapsLock before gnome 3.6 upgrade all working fine, however new Input Sources broke my system a little bit
I fixed my CapsLock by dconf-editor org\gnome\desktop\input-sources\xkb-options ['grp:caps_toggle', 'grp_switch', 'grp_led:caps'], but I can't get work
- language switch indicator not working
- show-flags does nothing anymore
Any help fit is required because of usability issues

Also, with Gnome 3.6 it's no longer possible to switch layouts with the Caps key. That setting is not available even in gnome-tweak-tool.
I figured out how to do make the settings a lot more flexible, and fix all the layout bugs introduced by 3.6. This is done by configuring everything through setxkbmap and not letting gnome interfere with the settings.
Remove all input sources, and the typing shortcuts from gnome keyboard settings window.
Open dconf-editor and remove everything from "org\gnome\desktop\input-sources\xkb-options". I was not able to set it to nothing, but setting it to ['grp_led:caps'] worked. These 2 steps were needed not to interfere with the config described below.
Install kbdd-git from aur, if you want separate layout for each window.
Create a script with preferred setxkbmap settings. Here is mine, setting Caps to switch languages, and swapping alt and win keys on MacBook.
#!/bin/sh
setxkbmap -layout us,ru
setxkbmap -option 'grp:caps_toggle'
setxkbmap -option 'altwin:swap_lalt_lwin'
# kbdd is needed to keep separate layout for each window.
`which kbdd` && kbdd
Launch gnome-session-properties and add this script to the list.
Last edited by ikatson (2012-11-02 21:51:13)

Does NVIDIA prop. work with gnome 3.2 now?

Has Anyone Tried Installing NVIDIA prop. and used it with gnome 3.2. Is the NVIDIA prop. driver updated to work with the new version of xorg-server.I'm trying to switch from nouveau to NVIDIA prop.

So fast! Thanks, i knew it wasn't a party with nouveau but was thinking maybe they would have fixed it for the older cards.

I have down loaded a track which was initially missing 1min 30 seconds. iTunes enabled my to reload the rack which is complete on the PC. However, syncing with my Ipad2 does not seem to replace the incomplete version with the full version. Thanks S

I have down loaded a track which was initially missing 1min 30 seconds. iTunes enabled me to reload the rack which is now complete on the PC. However, syncing with my Ipad2 does not seem to replace the incomplete version with the full version. Can anyone out there help?
Thanks S

Thanks for the response. Unfortunately, I've un-checked the track and re-synced the Ipad as suggested, but then re-checking and re-syncing han no effect. The track is still missing the final minute and a half or so. I've tried it twice, but the effect is the same.
Any other ideas? Would un-checking the entire music collection and staring again work, or is that a road to disaster?

No screen lock with gnome 3

Hello guys
My major problem with gnome 3 is that I'm unable to lock my screen.
I tried every possible alternative such as locking after suspend via pm-suspend, the gnome-menu or closing the lid.
Even lock screen via the gnome-menu doesn't work.
Furthermore I changed my dconf and gconf multiple times ( especially the lock-use-screensaver setting) and tried every solution posted in the web. But nothing solved my problem.
I also tested using GDM in stead of SLIM ( which I prefer ) but this solved my problem neither.
My laptop is an Acer Aspire 3820TG Timeline X running the newest kernel ( 3.0 ) and Gnome 3.0.2.
If you need more information don't hesitate to ask!

I'm not sure what is "ridiculous".
When on a call using the iPhone's earpiece - holding the iPhone up to your ear and face during a call, the iPhone includes a proximity sensor to automatically turn the screen off or lock the screen when doing so - there is no need to press the sleep/wake button while holding the iPhone up to your ear and face during a call. When pulling the iPhone away from your ear and face during a call to look at the screen and to use the iPhone for something else during the call or to hang up the call, etc., the screen turns back on. This is done automatically.

Issue with Gnome 3.12 login and MOTD

Hello,
This may be trivial, but I've struggled to find an answer for a problem I now have following creating an motd. I wanted an motd especially for terminal / ssh logins, but had no idea Gnome would attempt (I believe it does anyway) to display the motd contents immediately after logging in.
Whilst this would not be an issue if it actually worked and displayed the motd rather than garbage (see image below). It makes my login time much longer as it hangs on the login screen, before finally reaching the desktop. If I blank the motd, this problem goes away, however, as said, I really want the motd for ssh and terminal use. Has anyone else experienced this issue? Is there a way to disable Gnome from reading this file, or to display it correctly and not hamper my login times?
I'm running Arch x86_64 with Gnome 3.12 and would appreciate any time and help on this.
Steve
Do Not Post Full Size Images -- Inxsible
- My bad, have created a 230 x 230 thumbnail with link:
In case it helps, my motd code which works fine in the terminal:
#!/bin/bash
#Script to update motd with relevant information.
#Define output file
motd="/etc/motd"
# Collect information
USERNAME=`logname`
HOSTNAME=`uname -n`
KERNEL=`uname -r`
CPU=`awk -F '[ :][ :]+' '/^model name/ { print $2; exit; }' /proc/cpuinfo`
ARCH=`uname -m`
PACMAN=`pacman -Qu | wc -l`
DISC=`df -h | grep /dev/mapper/vg_arch-lv_home | awk '{print $5 }'`
MEMORY1=`free -t -m | grep "buffers/cache" | awk '{print $3" MB";}'`
MEMORY2=`free -t -m | grep "Mem" | awk '{print $2" MB";}'`
PSA=`ps -Afl | wc -l`
PSU=`ps U $USER h | wc -l`
#Time of day
HOUR=$(date +"%H")
if [ $HOUR -lt 12 -a $HOUR -ge 0 ]
then TIME="Morning"
elif [ $HOUR -lt 17 -a $HOUR -ge 12 ]
then TIME="Afternoon"
else TIME="Evening"
fi
#System uptime
uptime=`cat /proc/uptime | cut -f1 -d.`
upDays=$((uptime/60/60/24))
upHours=$((uptime/60/60%24))
upMins=$((uptime/60%60))
upSecs=$((uptime%60))
#System load
LOAD1=`cat /proc/loadavg | awk {'print $1'}`
LOAD5=`cat /proc/loadavg | awk {'print $2'}`
LOAD15=`cat /proc/loadavg | awk {'print $3'}`
#Color variables
W="\033[00;37m"
B="\033[01;36m"
R="\033[01;31m"
G="\033[01;32m"
N="\033[0m"
#Clear screen before motd
clear > $motd
echo -e "
$B. $W
$B/#\ $W _ $B _ _
$B/###\ $W __ _ _ __ ___| |__ $B| (_)_ __ _ ___ __
$B/#####\ $W / _' | '__/ __| '_ \ $B| | | '_ \| | | \ \/ /
$B/##.-.##\ $W | (_| | | | (__| | | |$B| | | | | | |_| |> <
$B/##( )##\ $W \__,_|_| \___|_| |_|$B|_|_|_| |_|\__,_/_/\_\\
$B/#.-- --.#\ $W
$B/' '\
" >> $motd
echo -e "$G---------------------------------------------------------------" >> $motd
echo -e "$W Good $TIME$A $USERNAME$W! You're Logged Into $A$HOSTNAME$W! " >> $motd
echo -e "$G---------------------------------------------------------------" >> $motd
echo -e "$B KERNEL $G:$W $KERNEL $ARCH " >> $motd
echo -e "$B CPU $G:$W $CPU " >> $motd
echo -e "$B MEMORY $G:$W $MEMORY1 / $MEMORY2 " >> $motd
echo -e "$B LV USE $G:$W $DISC " >> $motd
echo -e "$B SWAP USE $G:$W `free -m | tail -n 1 | awk '{print $3}'` MB " >> $motd
echo -e "$G---------------------------------------------------------------" >> $motd
echo -e "$B LOAD AVG $G:$W $LOAD1, $LOAD5, $LOAD15 " >> $motd
echo -e "$B UPTIME $G:$W $upDays days $upHours hours $upMins minutes $upSecs seconds " >> $motd
echo -e "$B PROCESSES $G:$W You are running $PSU of $PSA processes " >> $motd
echo -e "$B HOSTNAME $G:$W $HOSTNAME " >> $motd
echo -e "$B PACMAN $G:$W $PACMAN packages can be updated " >> $motd
echo -e "$B USERS $G:$W `users | wc -w` users logged in " >> $motd
echo -e "$G---------------------------------------------------------------" >> $motd
echo -e " $W Please do not share your login and use sudo for root access " >> $motd
echo -e "$G---------------------------------------------------------------" >> $motd
echo -e "$N" >> $motd
Last edited by sjjones85 (2014-04-17 17:22:12)

Inxsible, my apologies, hope the thumbnail is better now. Thanks for the welcome too, although I've lurked as a reader for a while

Replace libsystemd with testing/systemd?...

pacman -Syu
:: Synchronizing package databases...
testing 30.2 KiB 71.0K/s 00:00 100%
core is up to date
extra is up to date
community 1766.4 KiB 103K/s 00:17 100%
archlinuxfr is up to date
mate is up to date
:: Starting full system upgrade...
:: Replace libsystemd with testing/systemd? [Y/n] n
:: Replace systemd-tools with testing/systemd? [Y/n] n
how to act?
tia!

1archgamenon2 wrote:
pacman -Syu
:: Synchronizing package databases...
testing 30.2 KiB 71.0K/s 00:00 100%
core is up to date
extra is up to date
community 1766.4 KiB 103K/s 00:17 100%
archlinuxfr is up to date
mate is up to date
:: Starting full system upgrade...
:: Replace libsystemd with testing/systemd? [Y/n] n
:: Replace systemd-tools with testing/systemd? [Y/n] n
how to act?
tia!
seems new systemd "testing" has libsystemd and systemd-tools inside it, just like systemd-git on AUR

Problems with GNOME After The Last Upgrade

I have too many problems these days with my Arch box.. And I don't know when or how these problems are solved but I'm really bored about having problem all the time. I don't know all of these are bugs but if they're I'm ready to enter some bug reports.
1) After the last update, Metacity doesn't start automatically. So everytime, I don't have my mouse theme, my thema of borders of the windows, the notes I took with gnome's note applet doesn't disappear.
2) gnome-power-manager is never the same that I used to.. I just found that killing and rerunning it is at least make it work. But it's menus and options is not rich as I was earlier times. It doesn't say that much as it did in the earlier times.

I've same problem with gnome-power-manager, it works only when i kill it with killall gnome-power-monitor and re-run it.
About metacity i don't have problem with it.

Incomplete logout with Gnome/systemd

Similar Messages

Maybe you are looking for