You are not logged in.
When I run awesome with xinit (exec awesome), I get:
awesome: error while loading shared libraries: libxcb-util.so.0 (...)
Somebody else also had this problem, but I can't fix it. I tried both awesome-git from AUR and awesome from regular repositores.
What should I do? Thank you.
Also! My system is definitely up to date ![]()
Offline
Does awesome crash?
Are you in the same situation as described in the link you give? I mean you've been installing awesome package (and maybe dependencies) from other sources?
Offline
Does awesome crash?
Are you in the same situation as described in the link you give? I mean you've been installing awesome package (and maybe dependencies) from other sources?
I'm in the exactly situation. The other guy said he fixed it with a symlink, but I have no idea of how I can do that particular symlink.
Offline
Symlinking library files is not a solution.
The latest awesome package available in the [community] repo is built against libxcb-util.so.1 (and is working fine). Are you sure that's the repo you got it from?
Burninate!
Offline
Concerning symlinks: Did you read all the way through that thread (particularly post #4)?
And when you say your system is up-to-date, do you mean that you've recently rebuilt Awesome from source? That's often the culprit when it can't find libraries: Awesome itself is outdated. Try building from either the ABS tree or git. When it comes to WMs, many versions you'll find in personal repositories or the AUR exist to ostensibly make things easier for beginners, but ultimately hamper the learning process by cutting out important steps. It's almost always best to start from scratch, and learn the details about the window manager yourself.
Edit: Gcool kinda beat me to it. ![]()
Last edited by ANOKNUSA (2012-07-13 16:09:09)
Offline
As already a response says don't make any symlinks, it will just make the mess even more diffucult to troubleshoot. Try to track down if you've been adding packages related to awesome and libxcb from AUR and any other source, and try to clean up your system. Awesome was sent "down" to AUR for a time, before it reapeared in [community], but I don't know for how long you've been running awesome, or why it suddenly (if it did or you just installed it) broke.
Offline
I just built awesome from source, I git pull'd origin master, and make install'd, but I get a new error now:
/home/david/.config/awesome/rc.lua:41: attempt to index global 'beautiful' (a nil value)
/usr/local/share/awesome/lib/naughty.lua:312: attempt to index 'beautiful' (a nil value)
E: awesome: main.555: couldn't find any rc file
xinit: connection to X server lost
Offline
Is there a special reason for why don't run Awesome from main repos? I still don't understand:
- have you run Awesome for quite some time and suddenly it broke after som upgrade(or installation)?
- what installed package of Awesome broke? From main repos or some other source?
You get a new error and I don't even understand what version resultet in the old one.
Offline
Is there a special reason for why don't run Awesome from main repos? I still don't understand:
- have you run Awesome for quite some time and suddenly it broke after som upgrade(or installation)?
- what installed package of Awesome broke? From main repos or some other source?You get a new error and I don't even understand what version resultet in the old one.
Did you reay my first post? I said I got the same problem with both awesome-git from AUR and awesome from regular repos.
Offline
Check your error closely and you'll see why KimTjik asks. You rc.lua probably has syntax intended for the current stable version, while you're using the development version. If you want to stick with the git development version, you'll need to make these changes to your config.
Offline
You don't answer my question, but that's your choice, I'm not the one looking for help.
Anyway focus on the Awesome package from the community-repo and get that to work. It works perfectly well and doesn't give the error you report.
Offline
Oh, I get it, just fixed it by installed awesome not from git, but from tar.bz2 of latest stable version. The problem was, indeed, the configuration, thank you!
Offline
Don't forget to mark your thread as [SOLVED] in that case.
Burninate!
Offline