[arch-general] moving away from gnome
I would like to move away from Gnome, which I don't need at all since I only need to launch: - emacs - conkeror - thunderbird - gnome-terminal and I don't even use the menu but Alt-f2 for that. The main problem though is that on this laptop (a dell latitude E6420) if I'm not using gnome I can't make it suspend properly. The strange thing is that if I am in a gnome-session closing the lid or calling suspend from the gnome menu everything works. But if I fire up awesome only then closing the lid doesn't work anymore. So the question is, what is gnome magically firing up that other window managers don't? 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?
lauantai, 25. helmikuuta 2012 19:07:21 Andrea Crotti kirjoitti:
So the question is, what is gnome magically firing up that other window managers don't?
Gnome and KDE, probably Xfce too has a build in powersaving daemon which they use to observe the system ACPI events like "laptop screen closed"-event or "AC adaptor plugged"-event. Windowmanagers don't have this, so you need to run the acpid daemon to monitor the system for those events and configure it to run a spesific script on each one. Start from here [1] and read some of the other pages linked to that wiki page like the acpid and pm-utils pages. [1]https://wiki.archlinux.org/index.php/Laptop
On Sat, Feb 25, 2012 at 8:07 PM, Andrea Crotti <andrea.crotti.0@gmail.com> wrote:
I would like to move away from Gnome, which I don't need at all since I only need to launch: - emacs - conkeror - thunderbird - gnome-terminal
and I don't even use the menu but Alt-f2 for that. The main problem though is that on this laptop (a dell latitude E6420) if I'm not using gnome I can't make it suspend properly.
The strange thing is that if I am in a gnome-session closing the lid or calling suspend from the gnome menu everything works.
But if I fire up awesome only then closing the lid doesn't work anymore.
So the question is, what is gnome magically firing up that other window managers don't?
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?
Probably gnome-settings-daemon
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
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 Sat, Feb 25, 2012 at 07:24:25PM +0000, Andrea Crotti wrote:
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?)
The "Suspend" menu item calls ConsoleKit over DBus; the method calls are listed at <https://wiki.archlinux.org/index.php/Allow_Users_to_Shutdown#Using_consolekit>. Note that the item does not 'execute' anything; DBus method calls are done by gnome-panel itself. You can use `dbus-send`, `gdbus call`, `qdbus`, Net::DBus, or whatever you like. -- Mantas Mikulėnas <grawity@gmail.com>
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.
On Sat, Feb 25, 2012 at 09:22:53PM +0200, 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.
gnome-settings-daemon does not have anything to do with GConf (which uses 'gconfd-2') nor dconf ('dconf-service'). It manages session-wide settings, such as display, power, or global keybindings.
Sure it launches that but is totally irrelevant here, it only manages Gnome's settings, just like the name suggests :D
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. -- Mantas Mikulėnas <grawity@gmail.com>
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 Sat, 2012-02-25 at 21:33 +0200, Jesse Juhani Jaara wrote:
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 Sat, 2012-02-25 at 19:07 +0000, Andrea Crotti wrote:
I would like to move away from Gnome [snip] So the question is, what is gnome magically firing up that other window managers don't? [snip]
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. ;)
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..
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.
Another issue is that thunderbird for example looks quite bad, there's something wrong with the fonts and the graphics apparently..
Mayby this helps https://wiki.archlinux.org/index.php/Font_Configuration
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...
On Sat, 2012-02-25 at 20:32 +0000, Andrea Crotti wrote:
Now the next problem is that networkmanager doesn't see any networks DAEMONS=(dbus acpid netfs wicd @alsa @bluetooth @crond @cupsd @iptables @ntpd @openvpn @sensors @sshd @syslog-ng)
There's no networkmanager started ;). I didn't use networkmanager before I tried to get a Wi-Fi USB thingy working. When I tested networmanager I add an entry to the daemons: DAEMONS=(69switch_xorg.conf hwclock syslog-ng !network !netfs crond acpid dbus networkmanager rtirq) - Ralf
On Sat, 2012-02-25 at 22:48 +0200, Jesse Juhani Jaara wrote:
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
FWIW nm did my network connections and without any reason Arch was screwed up. Since I've got nm installed it happens that from time to time the access to the Internet is dropped. [spinymouse@archlinux ~]$ su Password: [root@archlinux spinymouse]# killall networkmanager networkmanager: no process found [root@archlinux spinymouse]# networkmanager stop bash: networkmanager: command not found [root@archlinux spinymouse]# ifconfig eth0 up && netcfg pppoe
pppoe already connected [root@archlinux spinymouse]#
Pff, I've forgotten to run poff and pon. Anyway, such annoying bullshit only happens since networkmanger is installed and is used "beside". Without nm I didn't run into trouble. I only installed it to test if an USB Wi-Fi device should work using it. At least nm on my machine seems to be a guarantee to screw up connections and to force a reboot.
Hi Andrea, On Sat, Feb 25, 2012 at 9:32 PM, Andrea Crotti <andrea.crotti.0@gmail.com> 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:05 +0100, Tom Gundersen wrote:
Hi Andrea,
On Sat, Feb 25, 2012 at 9:32 PM, Andrea Crotti <andrea.crotti.0@gmail.com> 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
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 <andrea.crotti.0@gmail.com> 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 Sat, 2012-02-25 at 22:27 +0100, Ralf Mardorf wrote:
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 <andrea.crotti.0@gmail.com> 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 ;).
PPS: IOW commend it out!
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!)
I bet you have '5' at the end of your kernel commandline.
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 02/26/2012 10:01 AM, Jesse Jaara wrote:
I bet you have '5' at the end of your kernel commandline. You won that was it :)
On Sun, 26 Feb 2012 09:57:58 +0000 Andrea Crotti <andrea.crotti.0@gmail.com> 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 Sat, Feb 25, 2012 at 07:07:21PM +0000, Andrea Crotti wrote:
The strange thing is that if I am in a gnome-session closing the lid or calling suspend from the gnome menu everything works.
But if I fire up awesome only then closing the lid doesn't work anymore.
So the question is, what is gnome magically firing up that other window managers don't?
Among other things, `gnome-settings-daemon` (which manages power settings in GNOME 3). There is nothing magic about it; just typical XDG autostart items, which are listed in /etc/xdg/autostart/ + ~/.config/autostart/ for any XDG-compliant session manager. (Pay attention to "AutostartCondition" in the files when browsing.) -- Mantas Mikulėnas <grawity@gmail.com>
On 02/25/2012 12:07 PM, Andrea Crotti wrote:
I would like to move away from Gnome, which I don't need at all since I only need to launch: - emacs - conkeror - thunderbird - gnome-terminal
and I don't even use the menu but Alt-f2 for that. The main problem though is that on this laptop (a dell latitude E6420) if I'm not using gnome I can't make it suspend properly.
The strange thing is that if I am in a gnome-session closing the lid or calling suspend from the gnome menu everything works.
But if I fire up awesome only then closing the lid doesn't work anymore.
So the question is, what is gnome magically firing up that other window managers don't?
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?
I've been moving away from gnome too. But piece-by-piece while I learn how to replace the components I need. The first step I did was take the /usr/share/gnome-session/sessions/gnome-fallback.session file and put it in ~/.config/gnome-session/sessions/, then edit it to replace the window manager with openbox. You could do the same with awesome. FYI: I've found that some of the autostart applications that I want in /etc/xdg/autostart require the session name to be gnome gnome* or gnome-fallback to work properly. -Matt
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 -- Tasos Latsas gpg: 0x219810C9 http://www.kodama.gr https://github.com/tlatsas
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 Sun, 2012-02-26 at 06:50 +0100, Ralf Mardorf wrote:
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.
Oops, I haven't read the Wiki about the current situation, before I sent this email. I experienced Ion2 as a useful WM, but I wasn't aware of the issue mentioned in the Wiki. In Germany we call it "ins Fettnäpfchen treten". http://www.dict.cc/?s=ins+fettn%C3%A4pchen+treten
https://wiki.archlinux.org/index.php/Ion3
- Ralf
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? And when everything is done, is there an easy way to uninstall all the gnome things which I don't need anymore? (pacman -R gnome complains about many dependencies)
On Sun, Feb 26, 2012 at 11:12 AM, Andrea Crotti <andrea.crotti.0@gmail.com> 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? -- mike c
On 02/26/2012 03:32 PM, mike cloaked wrote:
On Sun, Feb 26, 2012 at 11:12 AM, Andrea Crotti <andrea.crotti.0@gmail.com> 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..
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
On 26 February 2012 11:56, Jesse Juhani Jaara <jesse.jaara@gmail.com> 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 Mon, Feb 27, 2012 at 11:20 AM, Calvin Morrison <mutantturkey@gmail.com> wrote:
On 26 February 2012 11:56, Jesse Juhani Jaara <jesse.jaara@gmail.com> wrote:
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 :-)
I use this in my ~/.bashrc to start X automatically: if [[ -z "$DISPLAY" ]] && [[ $(tty) = /dev/tty1 ]]; then . startx logout fi -- thiagoc "O povo não deveria temer o governo. O governo é quem deveria temer o povo." V de Vingança
On Sun, Feb 26, 2012 at 4:39 PM, Andrea Crotti <andrea.crotti.0@gmail.com> 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
participants (15)
-
Andrea Crotti
-
Calvin Morrison
-
David C. Rankin
-
Ionut Biru
-
Jan Steffens
-
Jesse Jaara
-
Jesse Juhani Jaara
-
Mantas M.
-
Matthew Monaco
-
mike cloaked
-
pete
-
Ralf Mardorf
-
Tasos Latsas
-
Thiago Coutinho
-
Tom Gundersen