Accepted:
kdeaccessibility_3.2.2-1.diff.gz
to pool/main/k/kdeaccessibility/kdeaccessibility_3.2.2-1.diff.gz
kdeaccessibility_3.2.2-1.dsc
to pool/main/k/kdeaccessibility/kdeaccessibility_3.2.2-1.dsc
kdeaccessibility_3.2.2-1_all.deb
to pool/main/k/kdeaccessibility/kdeaccessibility_3.2.2-1_all.
kdeaccessibility_3.2.2-1_i386.changes uploaded successfully to localhost
along with the files:
kdeaccessibility_3.2.2-1.dsc
kdeaccessibility_3.2.2.orig.tar.gz
kdeaccessibility_3.2.2-1.diff.gz
kmag_3.2.2-1_i386.deb
kmousetool_3.2.2-1_i386.deb
kmouth_3.2.2-1_i386.deb
kdeaccessibility_3.
Package: knode
Version: 4:3.2.1-1
Severity: important
Tags: sid
If you save multiple attachments, the name filled into the save as
dialog box is always the name of the first attachment, so if you just
click "save" everywhere it overwrites the first attachment.
Very annoying.
-- System Informatio
Here's a patch for the /dev/urandom and imake mess from #240329. It
only changes genkdmconf.c to generate a kdmrc containing
RandomDevice=/dev/urandom. It is completely untested, but I think it
should fix the problem.
Have fun with it.
cheers
domi
Kjetil Kjernsmo writes:
> Hi all! It is cool that this will be fixed upstream for the next
> version, but it wasn't clear to me whether the maintainers intend to
> add this feature to the current debian packages, so that we will see
> it in sarge...?
> It seems like a trivial patch to me, and wo
Hi all!
It is cool that this will be fixed upstream for the next version, but it
wasn't clear to me whether the maintainers intend to add this feature
to the current debian packages, so that we will see it in sarge...?
It seems like a trivial patch to me, and would be very nice to have
now...
Your message dated Sun, 11 Apr 2004 15:33:10 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#240773: fixed in kdebase 4:3.2.2-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 11 Apr 2004 15:33:10 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#239297: fixed in kdebase 4:3.2.2-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 11 Apr 2004 15:33:09 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#236795: fixed in kdebase 4:3.2.2-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 11 Apr 2004 15:33:08 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#236515: fixed in kdebase 4:3.2.2-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 11 Apr 2004 15:33:08 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#236422: fixed in kdebase 4:3.2.2-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 11 Apr 2004 15:33:08 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#225157: fixed in kdebase 4:3.2.2-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 11 Apr 2004 15:33:08 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#195052: fixed in kdebase 4:3.2.2-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 11 Apr 2004 15:33:08 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#198661: fixed in kdebase 4:3.2.2-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 11 Apr 2004 15:33:08 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#218035: fixed in kdebase 4:3.2.2-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 11 Apr 2004 15:33:08 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#235216: fixed in kdebase 4:3.2.2-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 11 Apr 2004 15:33:08 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#236480: fixed in kdebase 4:3.2.2-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 11 Apr 2004 15:33:08 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#236700: fixed in kdebase 4:3.2.2-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 11 Apr 2004 15:33:08 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#236750: fixed in kdebase 4:3.2.2-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 11 Apr 2004 15:33:08 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#236750: fixed in kdebase 4:3.2.2-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 11 Apr 2004 15:33:09 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#236795: fixed in kdebase 4:3.2.2-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 11 Apr 2004 15:33:10 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#240980: fixed in kdebase 4:3.2.2-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sun, 11 Apr 2004 15:33:10 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#242381: fixed in kdebase 4:3.2.2-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Accepted:
kappfinder_3.2.2-1_i386.deb
to pool/main/k/kdebase/kappfinder_3.2.2-1_i386.deb
kate_3.2.2-1_i386.deb
to pool/main/k/kdebase/kate_3.2.2-1_i386.deb
kcontrol_3.2.2-1_i386.deb
to pool/main/k/kdebase/kcontrol_3.2.2-1_i386.deb
kdebase-bin_3.2.2-1_i386.deb
to pool/main/k/kdebase/kdebase
kdebase_3.2.2-1_i386.changes uploaded successfully to localhost
along with the files:
kdebase_3.2.2-1.dsc
kdebase_3.2.2.orig.tar.gz
kdebase_3.2.2-1.diff.gz
kappfinder_3.2.2-1_i386.deb
kate_3.2.2-1_i386.deb
kcontrol_3.2.2-1_i386.deb
kdebase-bin_3.2.2-1_i386.deb
kdebase-dev_3.2.2-1_i3
Package: kpdf
Version: 4:3.2.1-1
Severity: normal
Tags: sid
Hi -
My kpdf is spitting out lots of diagnostic info, to stdout, as it renders.
Mainly lots of this:
CLIPPING: 1 POLYS
- POLY 0: (0/1089) (842/1089) (842/0) (0/0) (0/1089)
FILLING: 1 POLYS
- POLY 0: (21/1106) (862/1106) (862/17) (21/1
Dominique Devriese wrote:
Chris Cheney writes:
I wonder how DEV_RANDOM is getting set to /dev/random, the Imakefile
doesn't mention /dev/random at all. A grep of kdebase for
/dev/random turns up nothing for me, but it must be getting set
somehow. :<
Yes, well, what I've noticed yesterday, is
On Sat, 2004-04-10 at 04:46, Chris Cheney wrote:
> Yes, I forgot to fix the bug because for some reason Ross decided to
> close the bug on kdelibs with his hicolor-icon-theme upload! I reopened
> it once I realized he had done so but I didn't catch it until after I
> had already uploaded kdelibs 3.
Hi,
installing package libidn11-dev, closing all konqueror windows and reopen one
will fix this immediately without recompiling anything.
HS
Processing commands for [EMAIL PROTECTED]:
> package konqueror
Ignoring bugs not assigned to: konqueror
> forwarded 237990 http://bugs.kde.org/show_bug.cgi?id=79427
Bug#237990: konqueror can't handle idn type domainnames
Noted your statement that Bug has been forwarded to
http://bugs.kde.org/sho
Chris Cheney writes:
> On Sun, Apr 11, 2004 at 01:41:49AM +0200, Dominique Devriese wrote:
>> ( note: '-DDEV_RANDOM=\"/dev/random\"' )
>>
>> I have spent a bit of time figuring out where this is coming from,
>> and apparently, it is generated with the Imakefile stuff in
>> kdebase/kdm/backend ( th
Your message dated Sun, 11 Apr 2004 02:42:08 -0500
with message-id <[EMAIL PROTECTED]>
and subject line /usr/bin/update-menus: Unknown error,
message=replacewith($string, $replace, $with)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 11 Apr 2004 02:43:20 -0500
with message-id <[EMAIL PROTECTED]>
and subject line menu: update-menu 2.1.10 fails on some menu entries
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the ca
On April 10, 2004 06:52 pm, Chris Cheney wrote:
> On Sat, Apr 10, 2004 at 12:36:45PM -0400, slaven peles wrote:
> > Actually there is still a menu/KDE problem present. When I try to
> > update-menus I get following output:
> > localhost:/root# update-menus
> > sh: line 1: /usr/bin/kdm-update-menu:
34 matches
Mail list logo
