You are not logged in.
I just commented out my entry for guake in ~/.config/openbox/autostart because there were two entries there in tint2. I read the wiki, and it does mention /etc/xdg/autostart/ as a handy place to check, but there was no listing for guake in that directory. So my question is, what exactly is starting guake?
~/.config/openbox/autostart:
## Autostart File ##
##xcompmgr (compositor)
#(sleep 1s && xcompmgr) &
#not using xcompmg because in OB, it definitely introduces screen tearing
##compton (compositor)
#(sleep 1s && compton) & #what I was using. Tearing problems
(sleep 1s && compton -bfzcCG --backend glx --vsync opengl-swc --paint-on-overlay -D5 -r6 -l-8 -t-8) & #This did solve tearing problem, but may make bl2 unplayable. #actually, it didn't effect bl2.
##Screensaver
(sleep 1s && xscreensaver -no-splash) &
##guake dropdown terminal
#(sleep 1s && guake) & #I disabled this because their were two entries in openbox for guake in tint2. I don't know what is starting guake now.
##tint2 panel
(sleep 1s && tint2) &
##Background
(sleep 1s && nitrogen --restore) &
##numlock
(sleep 1s && numlockx) &
##Mount stuff automatically
(sleep 7s && udiskie --tray) &
##start conky
#conky -c /home/convergence/.conkyrc #this messes everything up!
## NetworkManager Frontend
#(sleep 7s && nm-applet) &Here is a thread that seemed relevant: https://bbs.archlinux.org/viewtopic.php?id=114803
I used the command " ps -o user,pid,ppid,command -ax" found in this thread to find out what the parent PID is of guake, and it was bash, started by my current user. That's not very helpful!
Edit: As you can see, I take notes in my own config files so that I can remember why I made the changes that I did. I edited this entry post because apparently one of my notes had some foul language.
Last edited by Convergence (2015-02-13 19:38:23)
It's a very deadly weapon to know what you're doing
--- William Murderface
Offline
Looking at the file list it seems there is a dbus .service file that comes with guake. Have you tried disabling or masking that?
Offline
Do you start X with "startx"? Please post your "~/.xinitrc" file.
...and what's up with all the "sleep"ing? ![]()
Offline
...and what's up with all the "sleep"ing?
That is a default used and recommended by many distros that use openbox by default. Why they do this is beyond me - it is completely absurd.
EDIT: apparently it's also in our wiki. The way that is worded suggests that openbox's autostart isn't actually run by a shell but rather parsed by openbox itself. It also further suggests that openbox might fail to start things if they are all started simultaneously. Two more reasons I'll never use an autostart file for openbox. Just use xinitrc.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
@dodo3773: I think you nailed it. I verified the existence of /usr/share/dbus-1/services/org.guake.Guake.service. I honestly don't understand Dbus and how it relates to systemd. I'll read this: http://www.freedesktop.org/wiki/IntroductionToDBus/ when I get a chance. I switched from windows to Linux a long time ago. I learned quite a bit back then, but then stopped learning (I'm not in a tech field), and Linux kept evolving. I'm a total freakin n00b. ![]()
@drcouzelis: I don't use startx. I use KDM because I need to share my computer with my wife, and I think she would have an anxiety attack if she was confronted with a command line.
@Trilby: I think that xinitrc is only parsed if X is started manually. I use a DM (a necessity). PS, should I mark this solved? I haven't tested it yet (because I don't know how), but I suspect that Dodo3773 was correct
Thanks everyone for responding.
Last edited by Convergence (2015-02-17 21:00:09)
It's a very deadly weapon to know what you're doing
--- William Murderface
Offline