SliTaz Forum
You are not logged in.
Pages: 1
Hi,
Yesterday I "upgraded" packages slitaz-tools (960), tazpkg(866), lxpanel (0.6.2), lxsession (0.4.6.1), lxsession-edit (0.2.0).
The last three were not really upgrades, just installation of "rebuilt" versions.
And now my .Xdefaults file is not sourced at login. For now, I've worked around this by adding [c]xrdb -merge $HOME/.Xdefaults[/c] in my applications.conf . But this looks like a bug, probably in lxsession. What do you think?
Offline
Sorry to have to bump this post, but the recent forum flooding has pushed it to the third page of the forum root. Since .Xdefaults is a very standard and ubiquitous config file, I think it must be sourced at login whatever the specificities of SliTaz: it used to be until recently, and no commit seems to have intentionally removed this behavior. Hence my suspicion of a bug.
Is someone able to dig this?
Offline
First result for me in search: https://wiki.archlinux.org/index.php/X_resources tells me: Using ~/.Xdefaults is deprecated...
Do you have ~/.Xresources file? Personally I symlinked one file to another, and... Don't know, for me it seems all working.
Offline
Same here:
[c]~$ ls -l .Xresources
lrwxrwxrwx 1 tux users 10 avril 29 2015 .Xresources -> .Xdefaults[/c]
Maybe I should do some tests in a Live SliTaz.
Offline
What the useful settings you stored inside it?
(Resolution? I using auto value returned by X.
Xterm font and colors? I prefer Sakura.
Xcursor theme? Maybe. But seems it configured now in the different way with the session manager.)
Offline
Mainly, xterm settings, and XFig settings.
There are also the default settings from skel (fltk and Xcursor).
Offline
Pages: 1
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.53 MiB (Peak: 1.77 MiB) ]