You are not logged in.
Hello bunsenlabs community,
First of all, I want to thank the dev team and the community for this great distro.Although I have successfully managed to bring it to my taste, I am currently facing an autostart problem.
Searching about how I can have a keyboard layout indicator in tint2, I came across ibus and xxkb. I preferred xxkb, since ibus does a lot more than what I need. I followed this guide about installing & configuring graphical language switcher (xxkb).
Here goes the problem. The indicator does not run/appear at system startup. This is my autostart file. After many tries and some help from irc civilians, I have some conclusions:
1) xxkb is working like expected when I run "xxkb" in terminal,
2) The command "(sleep 1s && xxkb) &" is correct, since that when I run it directly in terminal, it works like expected,
3) When I change "xxkb" at the above command (2), in ~/.config/openbox/autostart file, with another application (eg. terminator, "(sleep 1s && terminator) &"), the "new" application launches at system startup.
Some maybe relevant information:
/etc/default/keyboard
~/.xsessionrc
I would appreciate it if you could provide me a solution to this problem, and not recommend me to install ibus for instance.
Thank you for your time,
mais
Last edited by mais (2016-03-23 17:09:26)
Offline
Is there a difference if you start it before or after tint2 in autostart? Does it appear (in the systray I presume) if you start it manually?
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
Can you check ~/.xsession-errors and/or `journalctl --user` for any indicative error messages?
Offline
Is there a difference if you start it before or after tint2 in autostart? Does it appear (in the systray I presume) if you start it manually?
I will place the "(sleep 1s && xxkb) &" command before tint2 to check if it will work, since that right now it is after tint2. No luck placing it before tint2, in autostart file. Yes, when I start it manually it appears in systray.
Can you check ~/.xsession-errors and/or `journalctl --user` for any indicative error messages?
~/.xsession-errors
`journalctl --user` - returned "No journal files were found."
Last edited by mais (2016-03-23 14:08:15)
Offline
Show us your xxkb configuration file please
Offline
mais, as an aside you may want to enable journaling for your systemd logging, it's pretty useful when debugging.
1. vi /etc/systemd/journal.conf
2. uncomment the lines 'storage' and 'compress'
3. Change storage to a value that you would like, such as persistent, volatile, or auto.
4. run the command
systemctl daemon-reload
If this doesn't work, you may just want to reboot fully.
5.Now cd to /var/log/journal/ <journal string>
This directory should now be created and contain the system.journal and the user's journal. If there is no /var/log/journal directory, make it, and reboot again.
now try using the journalctl command
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
Show us your xxkb configuration file please
XXkb.image.path: /home/mais/.config/xxkb
XXkb.group.base: 1
XXkb.group.alt: 2
XXkb.mainwindow.type: tray
XXkb.mainwindow.enable: yes
XXkb.mainwindow.appicon: yes
XXkb.mainwindow.border.width: 1
XXkb.mainwindow.label.enable: no
XXkb.mainwindow.border.color: white
XXkb.mainwindow.geometry: 20x20+0+0
XXkb.mainwindow.image.1: gb.xpm
XXkb.mainwindow.image.2: gr.xpm
XXkb.mainwindow.image.3:
XXkb.mainwindow.image.4:
XXkb.mainwindow._delete: no
XXkb.button.enable: no
XXkb.controls.focusout: no
XXkb.controls.two_state: no
XXkb.controls.add_when_start: yes
XXkb.controls.add_when_create: yes
XXkb.controls.add_when_change: no
I have also tried some alternative ways of starting an application on system startup, mentioned here, none worked :\
Last edited by mais (2016-03-23 16:07:28)
Offline
Can you post the image files you are using as well. ( I am no graphics guru)
Offline
Can you post the image files you are using as well. ( I am no graphics guru)
What do you mean? The actual gb.xpm and gr.xpm files? And if yes, how this can help me solve the mentioned problem? (if you just want the images for personal use just use pms, please!)
Last edited by mais (2016-03-23 16:46:21)
Offline
Yes, please.
I am a graphics newb.
I presume the easiest way would be to tar up your folder and make the tar file publicly available.
Offline
Could it be some sort of a path problem?
Could you add
which xxkb > /home/user/xxkb.log &
to autostart and see what happens. Another thing I'd try is much longer sleep, perhaps 10.
Last edited by brontosaurusrex (2016-03-23 16:50:19)
Offline
Could it be some sort of a path problem?
Could you addwhich xxkb > /home/user/xxkb.log &
to autostart and see what happens. Another thing I'd try is much longer sleep, perhaps 10.
I added this line "which xxkb > /home/mais/xxkb.log &", after the command "(sleep 1s && xxkb) &" and it returned this path -> /usr/bin/xxkb , inside the xxkb.log file.
Last edited by mais (2016-03-23 16:54:01)
Offline
Then the path is fine.
Longer sleep?
How is this?
(xxkb > /home/user/xxkb.log 2>&1) &
Last edited by brontosaurusrex (2016-03-23 17:07:02)
Offline
Then the path is fine. Longer sleep?
YUP thats it!
Thank you brontosaurusrex, and all for your time (you can mark this as solved).
Last edited by mais (2016-03-23 17:06:29)
Offline
Good, you need to rename the thread to "solved" yourself.
Offline