Upgrade to pcmanfm 0.9.7 makes mrxvt pseudo-transparancy not work.

Question

Pcmanfm got updated when I did a "pacman -Suy".  I run mrxvt and transparancy
no longer works.  Before I was able to adjust the transparancy using hotkeys.  When
I enable transparancy, my terminals windows no longer refresh properly.  The
background doesn't get refreshed as it did with pcman 0.5.2-1.  So I killed the pcmanfm
process and started xfdesktop (xfce4 desktop manager), and the terminals worked
correctly.  Now I'm not sure if there is a new protocol or format for the Atoms on the
root window, but something is definitely wrong.  I was going to submit a bug request
but I'm not sure if it is something with mrxvt or pcmanfm.
A simple test to validate my claim is to run pcmanfm --desktop, then run mrxvt,
set a desktop backround image.  Inside the mrxvt setting press ctrl+shift+r.  Then
you can adjust the transparancy (when it works), with ctrl+shift+j
and ctrl+shift+k.  You can also display text on the terminal window, then hit ctrl+l
to clear the screen and the text no longer erases.  You can toggle the transparancy mode
with ctrl+shift+r and then hit ctrl+l to see results.
Does anyone have a solution?
Thanks...

Answer 1

Eksel wrote:
For the "Not Authorized" error :
With Udisks the file you have to edit instead of "usr/share/polkit-1/actions/org.freedesktop.devicekit.disks.policy" is  "usr/share/polkit-1/actions/org.freedesktop.udisks.policy"
You just have to replace <allow_any>no</allow_any> by <allow_any>yes</allow_any> for actions related to mount and unmount filesystem, devices, etc.
Then, it will not necessary to launch pcmanfm as "dbus-launch pcmanfm" (but it's necessary to launch dbus in your .xinitrc or autostart )
Works fine for me.
I found it unnecessary to edit those files. You really shouldn't edit them anyway because the changes will be overwritten on the next update of udisks. Here's what I did find necessary. In my .xinitrc, this didn't work:
exec ssh-agent dbus-launch ck-launch-session lxsession
I saw my USB drive but I couldn't mount it, receiving a "Not Authorized" error from pcmanfm. This did work though:
exec ssh-agent ck-launch-session dbus-launch lxsession
It seems that for some bizarre intangible reason, on my computer, the console kit daemon must be running BEFORE the dbus daemon is launched in order for PolicyKit's policies to work right. I actually thought it'd be the other way around. I'd like to see somebody else try these two different setups and see if they can reproduce what I've seen.
And by the way, kgas: dbus-launch was not at all meant to be started once for every single application. It was meant to be started once in the .xinitrc like how I have just written or like this:
eval `dbus-launch --sh-syntax --exit-with-session`
But of course that doesn't work because dbus-daemon must be started after the console kit daemon.
Last edited by ewtoombs (2010-07-17 06:17:15)