-=| Trent W. Buck, Thu, Mar 20, 2008 at 04:55:05PM +1100 |=- > On Wed, Mar 19, 2008 at 04:50:49PM +0200, Damyan Ivanov wrote: > > [...] sets XAUTHORITY to /home/root/.Xauthority. > > Ah, could it be the bad home directory? root's HOME is /root! > > > > Changing the code to > > home=`getent passwd $user | cut -d: -f6` > > XAUTHORITY=$home/.Xauthority > > This is a separate bug and should be split out: eeepc-acpi-scripts > assumes foo's home is /home/foo.
Fixed in Git already. > It's worth remembering that users can customize the scripts (since > they're conffiles), and that therefore it's probably best to aim for > > - understandability, so that a regular user can understand the > scripts enough to tweak them to taste; and > > - rightness, so that the average user doesn't need to make any > changes at all. Full ack. > For example, since I always use Ratpoison, I've customized my install > to talk directly to it (RP) instead of using the (much slower, > generic) aosd_cat. But it would probably be silly to add code to the > default scripts to detect and use Ratpoison, except possibly as a note > in /usr/share/doc/eeepc-acpi-scripts. I think corner cases may be added to the scripts, but commented out. Or better, do nothing when the special conditions are not present (ratpoison not detected). I guess it is not very hard to spot a running Gnome, Xfce, KDE or whatever and use their notification services, falling back to aosd_cat. Back to the original problem, notify() does not do anything when the display number printed by `who' contains no dots. :0 fails, :0.0 works. My experience showed that :0.0 only appears if I have some gnome-terminals running and if they are set to start 'login shells' (the default). This may explain why it worked for me. If I set gnoem-terminal to not start 'login shells', then it does not work here too. What does the output of `who' look like for you? -- dam JabberID: [EMAIL PROTECTED]
signature.asc
Description: Digital signature
