Live data from Hacker News

Ubuntu 13.10 (Saucy Salamander)

releases.ubuntu.com

191–192 of 192 posts

Re: Ubuntu 13.10 (Saucy Salamander)

#191
post #115

Earlier quoted context omitted.

I have always found that continous upgrade eventually break the system. A clean install should be the recommended choice.

I have been updating my Lenovo laptop every 6 months since 7.03 and it's still going fine.

7.04 install upgraded to 13.10 here. Worst I had to do was apt-get -f install after an apt-get dist-upgrade. So six years now.

Re: Ubuntu 13.10 (Saucy Salamander)

#192
post #98

Earlier quoted context omitted.

IIRC I didn't finding any easy way of making xmodmap settings persist over reboot, so I just took had a script that runs "xmodmap ~/.Xmodmap" run at startup. (Of course then I switched to xfce on my laptop, which seems to run its own xmodmap command after its run startup scripts or something which overrides them, which is kinda annoying, haven't found a nice way to get around that).

Try putting your `xmodmap' command in `~/.xinitrc'. It gets read whenever the X server starts (`startx').

Thanks, but Xfce's startup applications list (which is just a frontend for ~/.config/autostart) is already executed after the X server starts, and after .xinitrc.

(Apologies if me saying 'runs at startup' was misleading -- obviously if I had tried to do it from a script that ran on boot, before X starts (rather than on session start) it could never have worked in the first place!).

Edit: now I've started thinking about it again, I've changed the autostart script to call another which sleeps for 10s before xmodmap, which seems to have fixed the problem.

Post reply on HN