On 02/25/2012 07:22 PM, Jesse Juhani Jaara wrote:

lauantai, 25. helmikuuta 2012 20:19:31 Jan Steffens kirjoitti:

...

Probably gnome-settings-daemon The GNOME Settings Daemon is responsible for setting various parameters of a GNOME Session and the applications that run under it. Short: is the GConf X settings daemon.

Sure it launches that but is totally irrelevant here, it only manages Gnome's settings, just like the name suggests :D

Alright good, then I'll shut down all these things, fire up awesome and try to get everything working.. But another thing, is there a way to find out what command is exactly run when pressing things in the gnome-panel? (For example when I launch suspend from the gnome-panel, what is it executed?)

On 02/25/2012 01:24 PM, Andrea Crotti wrote:

But another thing, is there a way to find out what command is exactly run when pressing things in the gnome-panel? (For example when I launch suspend from the gnome-panel, what is it executed?)

catching a suspend command might be difficult, but for everything else, you should be able to open an xterm or gnome terminal and look at: 'ps axf' -- David C. Rankin, J.D.,P.E.

lauantai, 25. helmikuuta 2012 21:26:51 Mantas M. kirjoitti:

The actions upon lid closing are part of GNOME's settings. In GNOME 3.1, power management is done by the "power" plugin of gnome-settings-daemon.

Sure in Gnome, but we are talking about power-management outside Gnome here, which DOES work without any Gnome stuff (Haters, substitute word stuff with 'crap') ^_^

On 02/25/2012 07:54 PM, Ralf Mardorf wrote:

The OP asked for what GNOME does to fulfill his needs.

My interpretation of the original post is, that the OP decided to use a WM without the DE GNOME, so you are talking about what he has experienced with GNOME and what he should adopt if he moves away from GNOME.

You're talking about power-management done by GNOME too.

;)

Exactly, I really don't need any of these processes running behind my back, and I prefer to know what is going on on my machine.. I did actually run most of my time on destkop machines without a full DE (fluxbox/awesome and others), only on the laptop is a bit more tricky. Anyway I fixed the power management, with acpid configured properly everything is fine. Now the next problem is that networkmanager doesn't see any networks, and wicd tries to connect but the password is refused. I think this again has something to do with ConsoleKit and the policies, is that correct? Another issue is that thunderbird for example looks quite bad, there's something wrong with the fonts and the graphics apparently..

On 02/25/2012 08:12 PM, Jesse Juhani Jaara wrote:

lauantai, 25. helmikuuta 2012 20:06:28 Andrea Crotti kirjoitti:

...

Now the next problem is that networkmanager doesn't see any networks, and wicd tries to connect but the password is refused. I think this again has something to do with ConsoleKit and the policies, is that correct? Don't know if this has anything to with Networkmanager's way of functioning, but if you launch awesome trought .xinitrc you have 'ck-launch-session awe..' in there instead of just 'awesome'. And if you created a file to launch awesome from the loginmanager you have that there too.

Even more weird, with these daemons DAEMONS=(dbus acpid netfs wicd @alsa @bluetooth @crond @cupsd @iptables @ntpd @openvpn @sensors @sshd @syslog-ng) and this in inittab: id:3:initdefault: # Boot to X11 # id:5:initdefault: after rebooting GDM still fires up!! But how come? What is firing it up? And now I'm not even able anymore to choose gnome-classic as session :/ Might be worth to try with a new user, which doesn't have strange settings stored...

lauantai, 25. helmikuuta 2012 21:46:03 Ralf Mardorf kirjoitti:

On Sat, 2012-02-25 at 20:32 +0000, Andrea Crotti wrote:

...

netfs wicd @alsa

There's no networkmanager started ;). But he told he has also tried wicd and he has wicd in the daemons list :D

Hi Andrea, On Sat, Feb 25, 2012 at 9:32 PM, Andrea Crotti wrote:

and this in inittab: id:3:initdefault: # Boot to X11 # id:5:initdefault:

after rebooting GDM still fires up!! But how come? What is firing it up?

Depends on what else is in your inittab file. By default nothing in inittab will start gdm, but there are plenty of guides out there suggesting how to do that. -t

On Sat, 2012-02-25 at 22:13 +0100, Ralf Mardorf wrote:

On Sat, 2012-02-25 at 22:05 +0100, Tom Gundersen wrote:

...

Hi Andrea,

On Sat, Feb 25, 2012 at 9:32 PM, Andrea Crotti wrote:

...

and this in inittab: id:3:initdefault: # Boot to X11 # id:5:initdefault:

after rebooting GDM still fires up!! But how come? What is firing it up?

Depends on what else is in your inittab file. By default nothing in inittab will start gdm, but there are plenty of guides out there suggesting how to do that.

-t

I don't have GNOME installed, but I decided to use GDM.

Isn't there such an entry as I've got:

[spinymouse@archlinux ~]$ grep gdm /etc/inittab x:5:respawn:/usr/sbin/gdm -nodaemon

- Ralf

PS: I've got different Linux distros installed, don't care about the runlevel ;).

On 02/25/2012 09:13 PM, Ralf Mardorf wrote:

I don't have GNOME installed, but I decided to use GDM.

Isn't there such an entry as I've got:

[spinymouse@archlinux ~]$ grep gdm /etc/inittab x:5:respawn:/usr/sbin/gdm -nodaemon

- Ralf

I had that line, but my interpretation was that if the initdefault is 5 then do that. Apparently the initdefault line was not taken into consideration. Now I rebooted again and with this line id:3:initdefault: arch still boots in init 5, but at least it doesn't fire up GDM now. So how on earth is it possible that it boots in init 5 even if I declare the default to be 3? The wireless is also solved now, awesome launched with ck-launch-session works perfectly :) (Almost there, thanks everyone!)

On 02/26/2012 12:01 PM, Jesse Jaara wrote:

I bet you have '5' at the end of your kernel commandline.

or he has both 3 and 5 enabled in inittab :D -- Ionuț

On Sun, 26 Feb 2012 09:57:58 +0000 Andrea Crotti wrote:

On 02/25/2012 09:13 PM, Ralf Mardorf wrote:

...

I don't have GNOME installed, but I decided to use GDM.

Isn't there such an entry as I've got:

[spinymouse@archlinux ~]$ grep gdm /etc/inittab x:5:respawn:/usr/sbin/gdm -nodaemon

- Ralf

I had that line, but my interpretation was that if the initdefault is 5 then do that. Apparently the initdefault line was not taken into consideration.

Now I rebooted again and with this line id:3:initdefault:

arch still boots in init 5, but at least it doesn't fire up GDM now. So how on earth is it possible that it boots in init 5 even if I declare the default to be 3?

You have removed gdm from "/etc/rc.conf" at the bottom Pete . -- Linux 7-of-9 3.2.7-1-ARCH #1 SMP PREEMPT Tue Feb 21 09:51:29 CET 2012 x86_64 AMD Phenom(tm) 9600B Quad-Core Processor AuthenticAMD GNU/Linux

On Sun, 2012-02-26 at 02:41 +0200, Tasos Latsas wrote:

On 25/02/12 21:07, Andrea Crotti wrote: [...]

...

I would also like to try xmonad finally, but I've never been able to configure it yet. I have an ~/.xmonad/xmonad.hs file (the default one copied) that compiles perfectly, but if I try a startx the screen just stays blank, without logging any error in the Xorg.0.log.

Any idea of what it could be?

FYI from the Xmonad FAQ [1]:

"XMonad is a minimal window manager, meaning it doesn't set a background, start a status bar, display a splash screen or play a soothing sound effect when it starts up."

See [2][3] for more info on how to configure it.

[1] http://www.haskell.org/haskellwiki/Xmonad/Frequently_asked_questions [2] http://www.haskell.org/haskellwiki/Xmonad [3] https://wiki.archlinux.org/index.php/Xmonad

Years ago I used Ion2. You might take a look at Ion3. It's another frame based WM. http://en.wikipedia.org/wiki/Ion_%28window_manager%29 https://wiki.archlinux.org/index.php/Ion3 - Ralf

On 02/26/2012 03:32 PM, mike cloaked wrote:

On Sun, Feb 26, 2012 at 11:12 AM, Andrea Crotti wrote:

...

I'm getting very close to a final solution :)

So now the only thing left to do is to make sure that these are executed (this is my .xprofile):

if [ -x "$(which gpg-agent)" ]; then if test -f $HOME/.gpg-agent-info&& \ kill -0 $(cut -d: -f 2 $HOME/.gpg-agent-info) 2>/dev/null then GPG_AGENT_INFO=$(cat $HOME/.gpg-agent-info) export GPG_AGENT_INFO else eval $(gpg-agent --daemon) echo $GPG_AGENT_INFO>$HOME/.gpg-agent-info fi fi

source $HOME/.bash_profile xbindkeys -f $HOME/.xbindkeysrc& bitlbee -F -c $HOME/.bitlbee.conf

Very strangely now even if the gpg-agent is not appearing to be on, the gpg key looks cached anyway. Is it the consolekit doing something maybe?

So I'm not sure if I should move them to .xinitrc or to use GDM.. Probably GDM would be easier and I can configure also the auto-login, but does it starts many other things that I don't need? Would it not be easier to switch to KDM or one of the other login managers rather than use GDM if you have moved away from Gnome?

Is kdm in kde-workspace-base? If yes it also has quite a lot of dependencies which I don't really need. And actually I think I can survive very well without any login manager. I just need to set up correctly my .xinitrc, and then give on e startx every time I reboot my machine (so every 3-4 weeks). With ck-lauch-session I solved the policykit issues so I don't see what else I'm missing not using a login manager..

On 26 February 2012 11:56, Jesse Juhani Jaara wrote:

sunnuntai, 26. helmikuuta 2012 16:39:31 Andrea Crotti kirjoitti:

...

Is kdm in kde-workspace-base? Yeh it is. kdebase-workspace is the correct name of the pkg tought If yes it also has quite a lot of dependencies which I don't really need. And actually I think I can survive very well without any login manager. I just need to set up correctly my .xinitrc, and then give on e startx every time I reboot my machine (so every 3-4 weeks). There is slim which only depends on gtk2 (mayby some other minor libs needed by anyother gtk app too) and cdm which is a conole mode login manager :D

I suggest you just use your tty. once you login, just run xinit. it works fantastically for me :-)

On Sun, Feb 26, 2012 at 4:39 PM, Andrea Crotti wrote:

...

Would it not be easier to switch to KDM or one of the other login managers rather than use GDM if you have moved away from Gnome?

Is kdm in kde-workspace-base? If yes it also has quite a lot of dependencies which I don't really need. And actually I think I can survive very well without any login manager. I just need to set up correctly my .xinitrc, and then give on e startx every time I reboot my machine (so every 3-4 weeks).

With ck-lauch-session I solved the policykit issues so I don't see what else I'm missing not using a login manager..

It's a free choice! Just that I use KDM and it works fine so made the suggestion - but if you can work without a login manager and it gives you what you need that is fine too. -- mike c