Launch Compiz in dbus-launch session.

Vapourstreak · 2011-02-08 18:30:56

As you can see from my older topic, I'm having trouble accessing my removable drives. I think I've narrowed it down to not being able to start Compiz, my Window Manager, in a dbus-launch session, as I could access the removable drives when I launched dbus-launch thunar.

I've tried changing the .xinitrc and adding dbus-launch after ck-launch-session and adding dbus-launch to the Daemons, both to no avail.

milso · 2011-02-08 19:32:25

I haven't seen you're other topic, but you're .xinitrc should look like:

exec dbus-launch ck-launch-session compiz

Vapourstreak · 2011-02-08 19:37:06

But this says put it after? The Not Authorized error while trying to access other drives is another problem I'm having, but yeah, I'll try putting it before. Thanks for the suggestion, I'll let you know how it goes.

milso · 2011-02-08 19:41:42

When I previously used thunar, placing dbus before worked fine.

Why are you unable to start compiz along with dbus-launch as stated in your first post? Any error outputs, etc?

Looking back at your other thread, I see you have your NTFS partition mounted under /mnt/windows, but have no access to it. You need to change file permissions as root by:

# chmod -R 777 /mnt/windows/

After you have permissions, you can just add a bookmark to the Thunar side panel to the directory.

Last edited by milso (2011-02-08 22:15:03)

Vapourstreak · 2011-02-08 20:50:04

I put the dbus-launch before the ck-launch-session, and it seems to have no effect. Still have to manually launch dbus-launch thunar, and still getting the Not Authorized errors.

Trying to change permissions, I got this:

chmod: cannot access `777': No such file or directory
chmod: cannot access `/mnt/windows/': No such file or directory

and I tried to point it to the mount point I set in fstab (/), and I got this:

[dk@Vapourstreak-USB ~]$ sudo chmod -r 777 /mnt/
chmod: cannot access `777': No such file or directory

And wouldn't putting the NTFS partition in my bookmarks instead of starting thunar in a dbus-launch session kind of be a workaround, as I wouldn't be able to access any other removable disk unless I start dbus-launch thunar?

Cause if I just launch Thunar directly, or through Chrome or something, the sidebar just has shortcuts to my Home folder and File System, without any disks, but when I launch it using dbus-launch thunar, it shows trash and removable drives, too.

milso · 2011-02-08 22:16:59

Apologies, I edited my original post, the recursive function requires a -R, case sensitive.

Vapourstreak · 2011-02-09 03:40:43

Nope, still doesn't work. It changes the permissions, but it still gives me the Not Authorized error, and I still have to start thunar with a dbus-launch thunar command.

Any more help?

hokasch · 2011-02-09 11:39:31

Are you by chance using inittab method to autostart X on boot? If so, you will have to switch to something else with latest consolekit (Start X on Boot)

Vapourstreak · 2011-02-09 12:53:24

Yeah I'm using the inittab method, but I'll try that, and report back, thanks!

EDIT: Wait, what? Sorry, I think I misunderstood, LOL. What exactly do I have to do/read?

EDIT2: Wait, reread it, no, I'm using the inittab method to run SLiM at startup, not X directly, and .xinitrc for SLiM to launch compiz ccp.

Last edited by Vapourstreak (2011-02-09 12:57:58)

hokasch · 2011-02-09 13:00:26

Sorry, I think I misunderstood, LOL. What exactly do I have to do/read?

The linked wiki page, note on /etc/inittab method. I switched to mingetty + bash profile, see the same wiki page.

Edit: ah ok, there were some problems with slim + consolekit, not sure if resolved, in any case make sure to merge pacnew files

Last edited by hokasch (2011-02-09 13:03:29)

Vapourstreak · 2011-02-09 13:20:13

Yeah I've just read through like, a bajillion topics on this, and I'm guessing this will solve the Not Authorized error? How about the dbus-launch one? Will it fix that too? I always need to start dbus-launch thunar to even see my drives, so I'll need to figure out how to launch compiz ccp in a dbus-launch session or something.

Thanks for the help, btw!

netawater · 2011-07-13 11:47:28

Vapourstreak wrote:

Yeah I've just read through like, a bajillion topics on this, and I'm guessing this will solve the Not Authorized error? How about the dbus-launch one? Will it fix that too? I always need to start dbus-launch thunar to even see my drives, so I'll need to figure out how to launch compiz ccp in a dbus-launch session or something.
Thanks for the help, btw!

you should try enter X just by startx, and put exec dbus-launch ck-launch-session "your WM name"

Unia · 2011-07-13 12:17:35

I start my Compiz Standalone through the compiz-alone-utils package in AUR. I use SLiM too and have compiz-alone-session in my .xinitrc, no problems with dbus-launch at all. (though I use Nautilus)

SiD · 2011-10-31 11:41:59

Same problem here, any news about this?

I tried startx and SLiM.

.xinitrc

exec dbus-launch ck-launch-session compiz ccp

with other WM (PekWM) it works. Didn't try the compiz-alone-utils package from AUR so far ... would be nice to get this working without the package from AUR.

EDIT://
ok, tried compiz-alone-utils from AUR, but it does not work. :-(

exec dbus-launch ck-launch-session compiz-alone-session

Last edited by SiD (2011-10-31 11:53:40)

Mr.Elendig · 2011-10-31 13:06:07

SiD wrote:

Same problem here, any news about this?
I tried startx and SLiM.
.xinitrc
exec dbus-launch ck-launch-session compiz ccp
with other WM (PekWM) it works. Didn't try the compiz-alone-utils package from AUR so far ... would be nice to get this working without the package from AUR.

EDIT://
ok, tried compiz-alone-utils from AUR, but it does not work. :-(
exec dbus-launch ck-launch-session compiz-alone-session

exec ck-launch-session dbus-launch

The other way around will not work.

Also, use LXDM instead of slim. Slim is not maintained and buggy.
LXDM also has the sadvantage of taking care of dbus and consolekit for you.

SiD · 2011-10-31 13:16:10

Mr.Elendig wrote:

exec ck-launch-session dbus-launch
The other way around will not work.

I tried that first.

Mr.Elendig wrote:

Also, use LXDM instead of slim. Slim is not maintained and buggy.
LXDM also has the sadvantage of taking care of dbus and consolekit for you.

Maybe I will take a look at LXDM ...

P.S.
Why does it work with other WMs but not with compiz?

Arch Linux

#1 2011-02-08 18:30:56

Launch Compiz in dbus-launch session.

#2 2011-02-08 19:32:25

Re: Launch Compiz in dbus-launch session.

#3 2011-02-08 19:37:06

Re: Launch Compiz in dbus-launch session.

#4 2011-02-08 19:41:42

Re: Launch Compiz in dbus-launch session.

#5 2011-02-08 20:50:04

Re: Launch Compiz in dbus-launch session.

#6 2011-02-08 22:16:59

Re: Launch Compiz in dbus-launch session.

#7 2011-02-09 03:40:43

Re: Launch Compiz in dbus-launch session.

#8 2011-02-09 11:39:31

Re: Launch Compiz in dbus-launch session.

#9 2011-02-09 12:53:24

Re: Launch Compiz in dbus-launch session.

#10 2011-02-09 13:00:26

Re: Launch Compiz in dbus-launch session.

#11 2011-02-09 13:20:13

Re: Launch Compiz in dbus-launch session.

#12 2011-07-13 11:47:28

Re: Launch Compiz in dbus-launch session.

#13 2011-07-13 12:17:35

Re: Launch Compiz in dbus-launch session.

#14 2011-10-31 11:41:59

Re: Launch Compiz in dbus-launch session.

#15 2011-10-31 13:06:07

Re: Launch Compiz in dbus-launch session.

#16 2011-10-31 13:16:10

Re: Launch Compiz in dbus-launch session.

Board footer