hi,
i tagged it moreinfo, because your bug is difficult to reproduce. knode works
for me too. i prefered to set moreinfo than unreproducible as you can
reproduce it on 7 systems. It's also to know, if you've got the bug in latest
3.5.2-1. it was useful :) since this tag, you've added
Package: kdepim
Version: 4:3.5.1-1
Severity: wishlist
Tags: l10n patch
It is attached to this bug report.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux
Package: kdebase
Version: 4:3.5.1-1
Severity: wishlist
Tags: l10n patch
It is attached to this bug report.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.16
package kappfinder kate kcontrol kdebase kdebase-bin kdebase-data kdebase-dbg
kdebase-dev kdebase-doc kdebase-doc-html kdebase-kio-plugins kdepasswd
kdeprint kdesktop kdm kfind
Hello,
I'm getting errors when I try to build current unstable kdelibs with GCC 4.1,
It seems that the error is caused with the patch 27_kdnssd_avahi.diff.
These are the errors:
Making all in dnssd
make[3]: Entering directory
`/home/josep/src/kde/svn/kde35/kdelibs/obj-i486-linux-gnu/dnssd'
Oh and it's even been reported there already:
http://bugs.kde.org/show_bug.cgi?id=118167
According to the report the bug isn't that bad, cause this is only a bad
address that is being used by the media/system ioslave layer.
Try typing just camera:/ in the address bar.
I have the very same problem with my Canon PowerShot G3 (PTP mode).
The camera has two modes of communication: PTP and Normal.
When tried normal the camera didn't even get detected, but it might be
also HAL or hardware specific.
However my distro is Slackware running KDE 3.5.2, so this seems
SVN commit 527359 by vriezen:
Prepare for next stable in two weeks
CCMAIL: [EMAIL PROTECTED]
I've released rc1 for kmplayer 0.9.2. This should become the stable one
in two weeks string-freeze-period
(http://kmplayer.kde.org/pkgs/kmplayer-0.9.2-rc1.tar.bz2).
AFAIR only two new strings were
Processing commands for [EMAIL PROTECTED]:
forwarded 356142 http://bugs.kde.org/show_bug.cgi?id=125115
Bug#356142: knode: Fatal IO error: client killed
Noted your statement that Bug has been forwarded to
http://bugs.kde.org/show_bug.cgi?id=125115.
End of message, stopping processing here.
On Friday 07 April 2006 07:51, Hendrik Sattler wrote:
$ unset LC_COLLATE
$ locale
[...]
LC_COLLATE=de_DE.UTF-8
[...]
$ echo -e A\na\nB\nb | sort
a
A
b
B
It works here also with just an unset LC_COLLATE. I would not
set it unless it needs to differ from LANG
wr:~/b/av$ echo $LC_COLLATE
Matej Cepl wrote:
Rafael RodrÃguez wrote:
since a couple of days ago i've noted that all kde orderings are sensible
to caps. Kmail folders, kopete groups... everything!
What has changed and how can i fall back to the old behaviour?
Same here -- and yes, I don't like it either. Any ideas?
Rafael RodrÃguez wrote:
What has changed and how can i fall back to the old behaviour?
For me it was screwed up locale with the latest upgrade of debian/sid. Make
sure you have correct locale (command locale in xterm).
Matej
--
GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 07 April 2006 20:14, Matej Cepl was heard to say:
For me it was screwed up locale with the latest upgrade of
debian/sid. Make sure you have correct locale (command locale in
xterm).
So, is this wrong or right? Some of us just don't know
13 matches
Mail list logo
