Accepted:
kamera_3.2.1-1_i386.deb
to pool/main/k/kdegraphics/kamera_3.2.1-1_i386.deb
kcoloredit_3.2.1-1_i386.deb
to pool/main/k/kdegraphics/kcoloredit_3.2.1-1_i386.deb
kdegraphics-dev_3.2.1-1_i386.deb
to pool/main/k/kdegraphics/kdegraphics-dev_3.2.1-1_i386.deb
kdegraphics-kfile-plugins_3.2.1
kdegraphics_3.2.1-1_i386.changes uploaded successfully to localhost
along with the files:
kdegraphics_3.2.1-1.dsc
kdegraphics_3.2.1.orig.tar.gz
kdegraphics_3.2.1-1.diff.gz
kamera_3.2.1-1_i386.deb
kcoloredit_3.2.1-1_i386.deb
kdegraphics-dev_3.2.1-1_i386.deb
kdegraphics-kfile-plugins_3.
Package: kdebase
Version: 3.1.4
Severity: normal
Followup-For: Bug #225576
It wanted to compile the source of kdebase, but it was solved. It had
a mixture of testing and unstable. The version of Qt was old, but it
was updated.
Thanks Debian Qt/KDE Maintainers.
-- System Information:
Debian Rele
Processing commands for [EMAIL PROTECTED]:
> reopen 235216
Bug#235216: konqueror: MIME Support
Bug reopened, originator not changed.
> stop
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
Your message dated Fri, 5 Mar 2004 21:05:58 -0600
with message-id <[EMAIL PROTECTED]>
and subject line Bug#236369: Missing Debian wallpaper on welcome screen
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
reopen 235216
stop
I messed this up, shouldn't have been working on it so late at night. I
copied/pasted all the nametemplate stuff which means its all appended
with .html. duh!
Chris
signature.asc
Description: Digital signature
Your message dated Fri, 05 Mar 2004 18:17:02 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#235015: fixed in kdeaccessibility 3.2.1-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
Package: kdm
Version: 4:3.2.1-1
Severity: wishlist
Tags: sid
I really wish I could have the old Debian wallpaper back on the
welcome screen. The current blue wallpaper is ... boring.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (
Accepted:
kdeaccessibility_3.2.1-1.diff.gz
to pool/main/k/kdeaccessibility/kdeaccessibility_3.2.1-1.diff.gz
kdeaccessibility_3.2.1-1.dsc
to pool/main/k/kdeaccessibility/kdeaccessibility_3.2.1-1.dsc
kdeaccessibility_3.2.1-1_all.deb
to pool/main/k/kdeaccessibility/kdeaccessibility_3.2.1-1_all.
kdeadmin_3.2.1-1_i386.changes uploaded successfully to localhost
along with the files:
kdeadmin_3.2.1-1.dsc
kdeadmin_3.2.1.orig.tar.gz
kdeadmin_3.2.1-1.diff.gz
kcmlinuz_3.2.1-1_i386.deb
kcron_3.2.1-1_i386.deb
kdat_3.2.1-1_i386.deb
kdeadmin-kfile-plugins_3.2.1-1_i386.deb
kpackage_3.2
kdeaccessibility_3.2.1-1_i386.changes uploaded successfully to localhost
along with the files:
kdeaccessibility_3.2.1-1.dsc
kdeaccessibility_3.2.1.orig.tar.gz
kdeaccessibility_3.2.1-1.diff.gz
kmag_3.2.1-1_i386.deb
kmousetool_3.2.1-1_i386.deb
kmouth_3.2.1-1_i386.deb
kdeaccessibility_3.
Accepted:
kcmlinuz_3.2.1-1_i386.deb
to pool/main/k/kdeadmin/kcmlinuz_3.2.1-1_i386.deb
kcron_3.2.1-1_i386.deb
to pool/main/k/kdeadmin/kcron_3.2.1-1_i386.deb
kdat_3.2.1-1_i386.deb
to pool/main/k/kdeadmin/kdat_3.2.1-1_i386.deb
kdeadmin-kfile-plugins_3.2.1-1_i386.deb
to pool/main/k/kdeadmin/kd
Package: kdesktop
Version: 4:3.1.3-1
Severity: normal
Followup-For: Bug #189553
I just want to get notified when this is resolved ;-) It's a very rare issue and
I already killed the kdesktop_lock process so I can't send you the debug info.
Nothing is logged in syslog or on VT1.
-- System Informa
Package: kmail
Version: 4:3.1.5-1
Severity: wishlist
Hi
I don't know if this is something to go on the wishlist or if it's already a
Bug.
Now that many registrars have started to make idn domains available to the
large kmail should comvert such
internationalized domainnames to a correct punnyc
Package: kwin
Version: 4:3.1.5-2
Severity: normal
Intermittently (but very often), kwin would not honour explicitly specified
window geometries. For example, I frequently run (from the KDE menu using
the "Run Command..." command)
mlterm -geometry 80x28
But the geometry of the resulting window
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Your message dated Fri, 05 Mar 2004 16:41:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in KDE 3.2, which just entered unstable
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
Hi.
> I see 4 ways to solve this bug:
The fifth, which I'd recommend, is moving the icon into
/usr/share/apps/kflog/icons/hicolor/22x22/actions/save_all.png
KFlog should still be able to find it, and it won't get in the way of
anyone else. This change is IMHO well worth pushing upstream, an
Alejandro Exojo wrote:
When installing kflog, dpkg complains because an icon appears both in
kdevelop3-data and in kflog:
[...]
trying to overwrite
`/usr/share/icons/hicolor/22x22/actions/save_all.png', which is also in
package kdevelop3-data
"Save all" is a pretty standard action so I imag
Your message dated Fri, 05 Mar 2004 06:02:13 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#230203: fixed in kdebase 4:3.2.1-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 Fri, 05 Mar 2004 06:02:13 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#210431: fixed in kdebase 4:3.2.1-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 Fri, 05 Mar 2004 06:02:13 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#139733: fixed in kdebase 4:3.2.1-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 Fri, 05 Mar 2004 06:02:13 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#137940: fixed in kdebase 4:3.2.1-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 Fri, 05 Mar 2004 06:02:13 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#230203: fixed in kdebase 4:3.2.1-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 Fri, 05 Mar 2004 06:02:13 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#231442: fixed in kdebase 4:3.2.1-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 Fri, 05 Mar 2004 06:02:13 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#142540: fixed in kdebase 4:3.2.1-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 Fri, 05 Mar 2004 06:02:13 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#227677: fixed in kdebase 4:3.2.1-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 Fri, 05 Mar 2004 06:02:13 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#230203: fixed in kdebase 4:3.2.1-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 Fri, 05 Mar 2004 06:02:13 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#233562: fixed in kdebase 4:3.2.1-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 Fri, 05 Mar 2004 06:02:13 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#235216: fixed in kdebase 4:3.2.1-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 Fri, 05 Mar 2004 06:02:13 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#236078: fixed in kdebase 4:3.2.1-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.1-1_i386.deb
to pool/main/k/kdebase/kappfinder_3.2.1-1_i386.deb
kate_3.2.1-1_i386.deb
to pool/main/k/kdebase/kate_3.2.1-1_i386.deb
kcontrol_3.2.1-1_i386.deb
to pool/main/k/kdebase/kcontrol_3.2.1-1_i386.deb
kdebase-bin_3.2.1-1_i386.deb
to pool/main/k/kdebase/kdebase
kdebase_3.2.1-1_i386.changes uploaded successfully to localhost
along with the files:
kdebase_3.2.1-1.dsc
kdebase_3.2.1.orig.tar.gz
kdebase_3.2.1-1.diff.gz
kappfinder_3.2.1-1_i386.deb
kate_3.2.1-1_i386.deb
kcontrol_3.2.1-1_i386.deb
kdebase-bin_3.2.1-1_i386.deb
kdebase-dev_3.2.1-1_i3
On Fri, Mar 05, 2004 at 01:10:13AM -0600, Wayne Schroeder wrote:
> The auth.log (messages or syslog either) prints anything out when you
> login. It just lets you right in.
>
> libpam-runtime0.72-35
> libpam0g 0.76-15
you need a newer libpam-runtime.
drop the hammer on the next girl you screw...
http://cusp.ffdsd4d.com/vp5
No more of this sort of material. Honoured in 24-48 hours.
http://archetypical.amilsdcx.com/a.html
buick duopoly bock shipbuild acclamation determinant tomography snack keyed nil
veteran confederate
drop the hammer on the next girl you screw...
http://condemnate.ffdsd4d.com/vp5
No more of this sort of material. Honoured in 24-48 hours.
http://ignorant.amilsdcx.com/a.html
amoco bourbon barnett firearm hornbeam sudanese bombay coffman affect g
cheyenne electorate
uI
The auth.log (messages or syslog either) prints anything out when you
login. It just lets you right in.
libpam-runtime0.72-35
libpam0g 0.76-15
kdelibs4 3.1.5-1
---[ /etc/pam.d/kdm ]---
#
# /etc/pam.d/kdm - specify the PAM beha
drop the hammer on the next girl you screw...
http://chris.ffdsd4d.com/vp5
No more of this sort of material. Honoured in 24-48 hours.
http://testament.amilsdcx.com/a.html
evaluable clergymen erik kronecker quillwort clime purine fir mahayanist pardon
agribusiness barbaric
66 matches
Mail list logo
