Salix Forums

The hid-microsoft module is already part of the installation initrd.

Here is lsmod output with the Dell keyboard (a PS2 keyboard) connected:

Module                  Size  Used by
snd_seq_dummy           1479  0 
snd_seq_oss            30116  0 
snd_seq_midi_event      5708  1 snd_seq_oss
snd_seq                52486  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device          5473  3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss            40089  0 
snd_mixer_oss          17282  2 snd_pcm_oss
ipv6                  275315  22 
lp                      9781  0 
fuse                   66651  3 
radeon                906280  2 
ttm                    52981  1 radeon
firewire_ohci          27301  0 
firewire_core          51107  1 firewire_ohci
drm_kms_helper         27035  1 radeon
usbhid                 36859  0 
processor              25982  2 
hid                    77723  1 usbhid
r8169                  37529  0 
mii                     3906  1 r8169
drm                   177345  4 radeon,ttm,drm_kms_helper
thermal_sys            13862  1 processor
i2c_algo_bit            5055  1 radeon
snd_hda_codec_hdmi     22985  1 
shpchp                 26821  0 
snd_hda_codec_realtek   293594  1 
rtc_cmos                9374  0 
rtc_core               14471  1 rtc_cmos
i2c_i801                8230  0 
intel_agp              10824  0 
intel_gtt              14862  1 intel_agp
agpgart                28874  4 ttm,drm,intel_agp,intel_gtt
i2c_core               19769  5 radeon,drm_kms_helper,drm,i2c_algo_bit,i2c_i801
ppdev                   6021  0 
hwmon                   1473  2 radeon,thermal_sys
rtc_lib                 1978  1 rtc_core
parport_pc             21214  1 
parport                30087  3 lp,ppdev,parport_pc
button                  5013  0 
evdev                   9813  9 
sg                     26495  0 
snd_hda_intel          21915  3 
snd_hda_codec          71748  3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
snd_hwdep               6254  1 snd_hda_codec
snd_pcm                73762  4 snd_pcm_oss,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_timer              19671  2 snd_seq,snd_pcm
snd                    58334  16 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore               5681  2 snd
snd_page_alloc          7297  2 snd_hda_intel,snd_pcm

An update on keyboard shortcuts: it's a non-problem, because although CTRL-O or whatever has no effect, just O on its own does; and that's actually better, functionally speaking. I've tested this in Brasero and Writer, running an xfce session. I bet it works under xmonad too. So this is just a bit of an oddity, and probably common to all versions of Salix. I've just noticed it now because I'm trying to wean myself off mouse use to stave off RSI.

@hcl
well, as I wrote in my previous post, the hid-microsoft module is already there, so no idea why it doesn't work for you.

Hello for all, at first.

I've switched from 13.1.2 Xfce version to 13.37RC1.
I'm using Polish (Poland) locale: "pl_PL.utf8" with "qwerty pl" keyboard, set by the installer at run time.

What I've observed is some sort of text coding problem(?).
As it was in 13.1.2 version, it's also in RC1 ("pl_PL.utf8"). A small menu "glitch" is still visible:

Salix -> System -> Gslapt_rest_of_name

... and how it looks:

Gslapt MenedĹźer PakietĂłw

Should be (pl_PL.utf8):

Gslapt Menedżer Pakietów

... and this can be easily repaired by file edit -> Desktop_file (actually 2 of them) from "/usr/share/application" directory.

So, I think, this could be repaired before stable release will rise. Simple fix.

But it's something more, still with Polish locale:

* create some document using 13.1.3 or 13.37RC1, say, ".pdf" or ".txt"
* name it with Polish diacritical marks:

ęóąśłżźćń.txt
óó.txt

On Salix (13.1.3 or 13.37RC1), they are showing as expected, but after transfer to Debian (newest stable, pen-drive used), they are looking like this:

?�???????.txt
��.txt

Now, if I take them back into Salix, they are OK again.

Now, let's try this:
* the same file; edit name on Debian, from:

��.txt ("óó.txt" is correct)

into:

ó�.txt

* move file into Salix (13.1.3 or 13.37RC1) using pen-drive or even via LiveCD mode - and you have this:

ó�.txt

Without "�" amendments on my Debian installation, Salix will properly re-recognize this "óó.txt" name.
Repair that file name on Debian - this will reverse situation.

Any idea how to deal with this?

Problem is correlated with file names only, contents of ".txt" document are still correct.
All "ęóąśłżźćń" marks inside the document are intact.

I suppose, I'm not only one with this puzzle.

Terminal says:

Code: Select all

[~]$ locale
LANG=pl_PL.utf8
LC_CTYPE="pl_PL.utf8"
LC_NUMERIC="pl_PL.utf8"
LC_TIME="pl_PL.utf8"
LC_COLLATE=C
LC_MONETARY="pl_PL.utf8"
LC_MESSAGES="pl_PL.utf8"
LC_PAPER="pl_PL.utf8"
LC_NAME="pl_PL.utf8"
LC_ADDRESS="pl_PL.utf8"
LC_TELEPHONE="pl_PL.utf8"
LC_MEASUREMENT="pl_PL.utf8"
LC_IDENTIFICATION="pl_PL.utf8"
LC_ALL=
[~]$

This:

Code: Select all

setxkbmap pl

...is not working.
I do not know how it looks on other distributions - for a moment, but I feel, this is related with this:

Code: Select all

LC_COLLATE=C

--> should be(?):

Code: Select all

LC_COLLATE=pl_PL.utf8

If yes, then any advise how to properly repair it - will be very comforting and appreciated

Other things with 13.37RC1:

* after first start, screen saver is up and running - but it started ~4 sec. after mouse action, ~minute after log in into Xfce session, screensaver is set into default 10 min.; mouse movement brings expected behavior

----------
* as usually

: write/edit something with Mousepad and sometimes he does not respond for close button or Exit order (seen on Debian too); similar story happens with "Gcolor2" - the color picker

Cheers!

@hcl
was it the 32bit or the 64bit iso that you used? We identified a problem with the 64bit iso which could lead to modules to being loaded. It will be fixed in the next RC.

@Olivine
if you want to correct any problems with gslapt translations (or for any piece of software), please contact the respective project's developer(s). In this case, please contact the gslapt developer.

You locale problems are probably caused by using a utf8 locale in salix, but a non-utf8 locale with the other distribution. As the standard is utf8, you need to reconfigure debian to use utf8.

@gapan

* Polish locale:
I will take a closer look at my Debian machine at the earliest opportunity.
The Debian installation was carried out from the default Installer settings, in Polish.
I must admit that I was not expecting anything... unusual...

* Gslapt:
Corrected "gslapt.mo" file is already created, as well as new Desktop files for Polish locale.
I will contact shortly with the "Gslapt" package maintainer.

Thank you for your response, gapan.

~ Olivine

@gapan

I used the 64 bit ISO. I tried the RC2 ISO and the keyboard problem is fixed. Thanks!

hcl wrote:@gapan

I used the 64 bit ISO. I tried the RC2 ISO and the keyboard problem is fixed. Thanks!

Thank you for testing!

Salix Forums

Salix Xfce 13.37RC1

Re: Salix Xfce 13.37RC1

Re: Salix Xfce 13.37RC1

Re: Salix Xfce 13.37RC1

Re: Salix Xfce 13.37RC1

Re: Salix Xfce 13.37RC1

Re: Salix Xfce 13.37RC1

Re: Salix Xfce 13.37RC1

Re: Salix Xfce 13.37RC1

Re: Salix Xfce 13.37RC1