wrong locale in kpackage kde 3.3.2
hello,
I have noticed that every time I install a package from kpackage it gives the
following warnings:
perl:warning:Setting locale failed.
perl:warning:Please check that your locale settings:
LANGUAGE=(unset)
LC_ALL="en_US"
LANG=(unset)
are supported and installed on your system
perl:warning:Falling back to the standard locale ("C").
This is what I have in my system locale settings:
# cat /etc/profile
# /etc/profile: system-wide .profile file for the Bourne shell (sh(1))
# and Bourne compatible shells (bash(1), ksh(1), ash(1), ...).
PATH="/usr/local/bin:/usr/bin:/bin:/usr/bin/X11"
if [ "$BASH" ]; then
PS1='[EMAIL PROTECTED]:\w\$ '
else
if [ "`id -u`" -eq 0 ]; then
PS1='# '
else
PS1='$ '
fi
fi
export PATH PS1
umask 022
#
# Imposto la localizzazione
[EMAIL PROTECTED]
export LANG
[EMAIL PROTECTED]
export LC_CTYPE
[EMAIL PROTECTED]
export LC_ALL
# cat /etc/locale.gen
# This file lists locales that you wish to have built. You can find a list
# of valid supported locales at /usr/share/i18n/SUPPORTED. Other
# combinations are possible, but may not be well tested. If you change
# this file, you need to rerun locale-gen.
#
# XXX GENERATED XXX
#
# NOTE!!! If you change this file by hand, and want to continue
# maintaining manually, remove the above line. Otherwise, use the command
# "dpkg-reconfigure locales" to manipulate this file. You can manually
# change this file without affecting the use of debconf, however, since it
# does read in your changes.
[EMAIL PROTECTED] ISO-8859-15
[EMAIL PROTECTED] ISO-8859-15
I have no idea why kpackage seems to ignore locale system settings.
--
On this laptop no Windows system survives and LINUX POWER reigns UNLIMITED.
Successfully Microsoft free since December 2002.
GnuPG key ID: 28A61681
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
CMOS settings getting lost when user who is group "nvram" logs into KDE
Hello, For a customer I installed a Linux Scan Workstation with Debian Sarge. It is some Wortmann Terra Server with SiS 661 chipset with a motherboard that seems to be from ASUS (lspci output at the end of the mail). It all worked pretty well despite one problem: When the user logs into KDE 3.3.2 using KDM, and then logs out again with rebooting the machine, on the next start the BIOS of the machine (an American Megatrends one) complains that it cannot read the CMOS settings anymore. This doesn't happen when the user just boots into KDM and then uses KDM's menu to reboot the machine, i.e. when he doesn't log into KDE. This also doesn't happen when the user use the "safe" session (dunno the exact english name in KDM) which only gives an xterm. And it also doesn't happen when the user is not a member of the group "nvram" although even when he is, a "lsmod | grep nvram" after KDE was started gives no result. But it does also happen, when the user does not log out normally but just switches off the machine and switches it on again then. Currently I removed the user from the group "nvram" as a work-around, without knowing the exact cause of the problem. I am almost ready to file this under esoteric problems with non properly supported hardware, but I still would like to know what the heck is happening here. Who at all is accessing nvram during start of KDE? I de-installed "klaptopdaemon" which didn't make a difference. Any hints where to search? I am about to file this as a bug report, but before I would like to get some feedback on it. Maybe someone has an idea. I am using a standard Debian kernel 2.6.10-1-686 on that machine. Processor is a Pentium 4 with 2.4 GhZ. scanstation:~# lspci :00:00.0 Host bridge: Silicon Integrated Systems [SiS] 661FX/M661FX/M661MX Host (rev 11) :00:01.0 PCI bridge: Silicon Integrated Systems [SiS]: Unknown device 0003 :00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO] (rev 25) :00:02.1 SMBus: Silicon Integrated Systems [SiS]: Unknown device 0016 :00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] :00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] Sound Controller (rev a0) :00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) :00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) :00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller :00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91) :01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661FX/M661FX/M661MX/741/M741/760/M760 PCI/AGP (I also have a lspci -vv output here) Regards, -- Martin SteigerwaldMail: [EMAIL PROTECTED] Systemadministrator Fon: +49 (0)911 30999-0 team(ix) GmbH Fax: +49 (0)911 30999-99 Süd-West-Park 35, 90449 Nürnberg, Deutschland
Kleopatra KMail S/MIME gpgsm, what's going on?
Kleopatra still depends on the virtual gpgsm package, which is not provided by any packages. Does anybody know if there are any plans to alleviate this issue? I read the notes in http://lists.debian.org/debian-kde/2004/09/msg00102.html But really? Shouldn't this just work? Anders -- - Debian/Unstable - KDE 3.3.2 - KMail 1.7.2 - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kleopatra KMail S/MIME gpgsm, what's going on?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I agree with you, it "should", but the package maintainers have not yet made it work. I followed the explicit instructions, http://kmail.kde.org/kmail-pgpmime-howto.html#gnupg except that I put the little gpg-agent script into ~/.kde/env/ which I found by doing a grep for "gpg-agent" under /etc/*/ on a lark and found that that directory gets run if it exists in the comments for the global KDE startup scripts. But I agree with you, it "should" just work. And, given the quality of the Debian maintainers generally, it will. Personally, I like the simple inline OpenPGP style, but I didn't write the RFC that defines the MIME encapsulation. On Thursday 10 February 2005 06:58, Anders Ellenshøj Andersen was heard to say: > Kleopatra still depends on the virtual gpgsm package, which is not > provided by any packages. Does anybody know if there are any plans > to alleviate this issue? > > I read the notes in > http://lists.debian.org/debian-kde/2004/09/msg00102.html > > But really? Shouldn't this just work? - -- September 11th, 2001 The proudest day for gun control and central planning advocates in American history -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iQEVAwUBQgtazy9Y35yItIgBAQIG8gf9EYwHComeAEevZ4Q55CTW+0t2qHBHJayS JaiwDYJCqK+IRFKVCMfrMPWk0+7s9r5cus+uMT4c+0XZcHPk/JG6JHIWO4Q7ygu5 EyTLRpeIc7BZLeDbygTPTm7x0NRIvU6GCrBacnt7hJTv7AQs2MyfOGxkvoatayxT s2pUlVZxtSrsJtiBWsGe9IMX0LQd/nDngevfgyIjPSLKXiNH0TufWhuGlkD6rpTh AgeMVtiNS5eUEdW8avaxG6yfJCT9WSBBfC8i9Nf/oZIXVQGRBiomSFdqAkGAoQSb sZDDVr2/Pv34YkTbIWpIkO6jgtKbO34LCQgfztVQ80Kwghu0lYVsQg== =ygUJ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
unsubscribe
Em Qui 10 Fev 2005 09:58, Anders Ellenshøj Andersen escreveu: > Kleopatra still depends on the virtual gpgsm package, which is not provided > by any packages. Does anybody know if there are any plans to alleviate this > issue? > > I read the notes in > http://lists.debian.org/debian-kde/2004/09/msg00102.html > > But really? Shouldn't this just work? > > Anders > > -- > - Debian/Unstable - KDE 3.3.2 - KMail 1.7.2 - -- Guilherme Rocha Analista de Sistemas e Serviços Sul Soluções Informática Ltda. http://www.sulsolucoes.com.br +55-71-240-2026/240-3975
Re: Printing with Konqueror. Small font size
On Wednesday 09 February 2005 02:55 pm, Cousin Stanley wrote:
> | I did mean a PDF "printed" out of Konqueror,
> | just in case I wasn't clear.
> |
> | So Konqueror => PDF => Printer works OK,
> |
> | but Konqueror => Printer gets the small fonts?
>
> Curt
>
>I did open the .pdf file in Konqueror
>and print from it
>
>You have it right for me
>
> o konq > print > pdf .. { ok }
>
> o konq > print > man:xyzzy { small fonts }
>
> o konq > print > html . { small fonts }
>
>However, Cousin Leo has posted now
>that the pdf also is printing small fonts
>on his system
I think what Leo was talking about was opening the web page in Konqueror (the
same one that gives small fonts when you print to paper), selecting Print...
from the File menu, and then choosing Print to File (PDF) as the printer to
use. Then see if the resulting pdf has small fonts in it.
Josh
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CMOS settings getting lost when user who is group "nvram" logs into KDE
On Thursday 10 February 2005 06:56, Martin Steigerwald wrote: > Hello, > > For a customer I installed a Linux Scan Workstation with > Debian Sarge. It is some Wortmann Terra Server with SiS 661 > chipset with a motherboard that seems to be from ASUS (lspci > output at the end of the mail). > > It all worked pretty well despite one problem: > > When the user logs into KDE 3.3.2 using KDM, and then logs > out again with rebooting the machine, on the next start the > BIOS of the machine (an American Megatrends one) complains > that it cannot read the CMOS settings anymore. > > This doesn't happen when the user just boots into KDM and > then uses KDM's menu to reboot the machine, i.e. when he > doesn't log into KDE. > > This also doesn't happen when the user use the "safe" > session (dunno the exact english name in KDM) which only > gives an xterm. > > And it also doesn't happen when the user is not a member of > the group "nvram" although even when he is, a "lsmod | grep > nvram" after KDE was started gives no result. > > But it does also happen, when the user does not log out > normally but just switches off the machine and switches it > on again then. > > Currently I removed the user from the group "nvram" as a > work-around, without knowing the exact cause of the problem. > > I am almost ready to file this under esoteric problems with > non properly supported hardware, but I still would like to > know what the heck is happening here. Who at all is > accessing nvram during start of KDE? I de-installed > "klaptopdaemon" which didn't make a difference. > > Any hints where to search? I am about to file this as a bug > report, but before I would like to get some feedback on it. > Maybe someone has an idea. > > I am using a standard Debian kernel 2.6.10-1-686 on that > machine. [Snip] I noticed a new (I believe it was experimental) kernel option that enabled the use of the "supposedly" unused portion of the CMOS ram. I "think" that came out with the 2.6.10 kernel, but I am unsure as to exactly which releases have it. It sounds like that option is enabled in the kernel you are using, and somehow KDE is corrupting the CMOS ram data. I don't understand why that option would be enabled in any standard kernel. Removing the user (all users, perhaps) from nvram (non-volatile ram) seems like the proper solution. I wouldn't call it a work-around at all. Unless I completely misunderstand what's going on, I don't think that kernel option should be enabled in the first place, and if it is, most, if not all users, should not be members of the nvram group. N.P. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wrong locale in kpackage kde 3.3.2
On Friday 04 February 2005 20:51, Mauro Darida wrote:
> I have noticed that every time I install a package from kpackage it
> gives the following warnings:
> perl:warning:Setting locale failed.
> perl:warning:Please check that your locale settings:
> LANGUAGE=(unset)
> LC_ALL="en_US"
> LANG=(unset)
> are supported and installed on your system
> perl:warning:Falling back to the standard locale ("C").
>
> This is what I have in my system locale settings:
> # cat /etc/profile
> # /etc/profile: system-wide .profile file for the Bourne shell (sh(1))
> # and Bourne compatible shells (bash(1), ksh(1), ash(1), ...).
[...]
> #
> # Imposto la localizzazione
> [EMAIL PROTECTED]
> export LANG
> [EMAIL PROTECTED]
> export LC_CTYPE
> [EMAIL PROTECTED]
> export LC_ALL
AFAIK /etc/profile is not read when you log in through KDM.
The proper place to set default LANG and LANGUAGE is /etc/environment.
If you want per user settings, I think ~/.kde/env/ is the
proper place.
Cheers,
FJP
pgpsTjot1Tbx2.pgp
Description: PGP signature
Re: Kleopatra KMail S/MIME gpgsm, what's going on?
Am Donnerstag, 10. Februar 2005 12:58 schrieb Anders Ellenshøj Andersen: > Kleopatra still depends on the virtual gpgsm package, which is not provided > by any packages. Does anybody know if there are any plans to alleviate this > issue? > > I read the notes in > http://lists.debian.org/debian-kde/2004/09/msg00102.html > > But really? Shouldn't this just work? It does, read http://lists.debian.org/debian-kde/2005/01/msg00436.html and be happy :) The kleopatra package maintainer simply did not update the package description or does not realize that the solution is now much simpler that it was last september. The gpgsm maintainer probably only want to put it into Debian when gnupg2 is finally released (if this will ever happen). However, I am not quite sure how it was able to enter Sarge like this. HS
Re: wrong locale in kpackage kde 3.3.2
Am Freitag, 4. Februar 2005 20:51 schrieb Mauro Darida:
> I have noticed that every time I install a package from kpackage it gives
> the following warnings:
> perl:warning:Setting locale failed.
> perl:warning:Please check that your locale settings:
> LANGUAGE=(unset)
> LC_ALL="en_US"
> LANG=(unset)
> are supported and installed on your system
> perl:warning:Falling back to the standard locale ("C").
apt-get install locale
dpkg-reconfigure locale
HS
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kleopatra KMail S/MIME gpgsm, what's going on?
On Thursday 10 February 2005 19:04, Hendrik Sattler wrote: > > But really? Shouldn't this just work? > > It does, read > http://lists.debian.org/debian-kde/2005/01/msg00436.html > and be happy :) But you still have to use experimental packages. It doesn't work out of the box. I hope you can forgive me for not being completely happy until that happens. Anders -- - Debian/Unstable - KDE 3.3.2 - KMail 1.7.2 - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kleopatra KMail S/MIME gpgsm, what's going on?
Am Donnerstag, 10. Februar 2005 21:33 schrieb Anders Ellenshøj Andersen: > On Thursday 10 February 2005 19:04, Hendrik Sattler wrote: > > > But really? Shouldn't this just work? > > > > It does, read > > http://lists.debian.org/debian-kde/2005/01/msg00436.html > > and be happy :) > > But you still have to use experimental packages. It doesn't work out of the > box. I hope you can forgive me for not being completely happy until that > happens. Then you have to wait for the release of GnuPG-2.0, good luck ;) GnuPG-1.4 was just released and I doubt that GnuPG-2.0 will be released before Sarg ...wait, I take that back ;) Either you take kleopatra out of Sarge because it's uninstallable or you live with the external repository. HS
Re: wrong locale in kpackage kde 3.3.2
On Thursday 10 February 2005 19:04, Frans Pop wrote:
> On Friday 04 February 2005 20:51, Mauro Darida wrote:
> > I have noticed that every time I install a package from kpackage it
> > gives the following warnings:
> > perl:warning:Setting locale failed.
> > perl:warning:Please check that your locale settings:
> > LANGUAGE=(unset)
> > LC_ALL="en_US"
> > LANG=(unset)
> > are supported and installed on your system
> > perl:warning:Falling back to the standard locale ("C").
> >
> > This is what I have in my system locale settings:
> > # cat /etc/profile
> > # /etc/profile: system-wide .profile file for the Bourne shell (sh(1))
> > # and Bourne compatible shells (bash(1), ksh(1), ash(1), ...).
> [...]
> > #
> > # Imposto la localizzazione
> > [EMAIL PROTECTED]
> > export LANG
> > [EMAIL PROTECTED]
> > export LC_CTYPE
> > [EMAIL PROTECTED]
> > export LC_ALL
>
> AFAIK /etc/profile is not read when you log in through KDM.
> The proper place to set default LANG and LANGUAGE is /etc/environment.
And never set LC_ALL! It makes all other LC_* LANG setting being
ignored. Use LANG instead!
From setlocale:
... For glibc, first (regardless of category), the
environment variable LC_ALL is inspected, next the environment variâ
able with the same name as the category (LC_COLLATE, LC_CTYPE,
LC_MESSAGES, LC_MONETARY, LC_NUMERIC, LC_TIME) and finally the enviâ
ronment variable LANG. The first existing environment variable is
used. ...
Try:
LC_ALL=de_DE.UTF-8 LC_COLLATE=C LANG=en_US.UTF-8 locale
for 'bad' side effect of LC_ALL.
Achim
>
> If you want per user settings, I think ~/.kde/env/ is the
> proper place.
>
> Cheers,
> FJP
>
--
To me vi is Zen. To use vi is to practice zen. Every command is
a koan. Profound to the user, unintelligible to the uninitiated.
You discover truth everytime you use it.
-- [EMAIL PROTECTED]
KDM/X crashes intermittenly on exit
I've been trying to pin this down a little better, but it's intermittent nature makes it hard to draw any conclusions. Running Sarge with the latest KDE (3.3.2) and X (4.3.0.dfsg.1-10). 90% of the time kdm works fine, logging in and logging out. the other 10% of the time when logging out, instead of kdm coming back to the login screen, X shuts down and I'm returned to the F1 console. kdm can be restarted and works fine, eventually repeating the error. The XFree log shows only: Fatal server error: Caught signal 11. Server aborting no errors or warnings prior to that. kdm log contains the following: kdm: :0[10797]: IO Error in XOpenDisplay Feb 10 18:38:11 lindev kdm[15694]: Display :0 cannot be opened Feb 10 18:38:11 lindev kdm[15694]: Unable to fire up local display :0; disabled In the course of the last 10 hours I logged on and off 6 times, the first 5 times went normally, the 6th time the problem appeared. I might be days before it reoccurs, or it might be the next time I log off. Not sure if it's a kdm or an X issue, but I *think* it appeared with the last update of kdm. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
