I've also been having crashes using kbabel in Sarge (see #289646). I've
had crashes with several po files now.
The behavior is somewhat eratic: when I first had the crash, I could
always reproduce it, now I find that sometimes the crash does not happen.
Very likely my crashes are related to
Processing commands for [EMAIL PROTECTED]:
tag 289646 - sid
Bug#289646: kbabel: crash with some .po file
Tags were: sid
Tags removed: sid
thanks dude
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs
tag 289646 - sid
thanks dude
The tag 'sid' for this bug is probably _not_ correct!
Yeah, I forgot to remove it after Riku's mail. In the future, please
feel free to do control@ handling yourself when you're confident :-)
(At least in KDE land.)
Cheers (and congrats for your AM ;-),
--
kdebase_3.3.2-1_i386.changes uploaded successfully to localhost
along with the files:
kdebase_3.3.2-1.dsc
kdebase_3.3.2-1.diff.gz
kappfinder_3.3.2-1_i386.deb
kate_3.3.2-1_i386.deb
kcontrol_3.3.2-1_i386.deb
kdebase-bin_3.3.2-1_i386.deb
kdebase-dev_3.3.2-1_i386.deb
Your message dated Sun, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#280358: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#269590: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#244547: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#243770: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#207130: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#207126: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#289454: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#280362: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#266106: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#261740: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#249162: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#247407: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#247243: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#237067: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#237065: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#189574: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#243770: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#243770: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#280795: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#284844: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#286373: fixed in kdebase 4:3.3.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, 23 Jan 2005 13:17:26 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#286587: fixed in kdebase 4:3.3.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
Package: konqueror
Version: 3.3.1-4
Severity: normal
In the google search bar (at the top of the konqueror window), some
caracters are not used in the search. For example, if I type C++, it will
display the following url
http://www.google.com/search?q=C++ie=UTF-8oe=UTF-8
which is a search for C
El Domingo, 23 de Enero de 2005 20:53, Jean Darcoux escribió:
As a solution, I recommand to replace characters like '+' by there
corresponding code (like %2B in the case of '+'). The later example should
then display the URL
http://www.google.com/search?q=C%2B%2Bie=UTF-8oe=UTF-8
The problem,
On Sun, Jan 23, 2005 at 05:57:15PM +, David Johnson wrote:
If I have a directory full of images and videos, Konqueror will happily
generate preview thumbnails for each one until it reaches a RealVideo file,
at which point it will stop generating thumbnails and sit there with the
progress
kdeaccessibility_3.3.2-1_i386.changes uploaded successfully to localhost
along with the files:
kdeaccessibility_3.3.2-1.dsc
kdeaccessibility_3.3.2-1.diff.gz
kmag_3.3.2-1_i386.deb
kmousetool_3.3.2-1_i386.deb
kmouth_3.3.2-1_i386.deb
kdeaccessibility_3.3.2-1_all.deb
Greetings,
Accepted:
kdeaccessibility_3.3.2-1.diff.gz
to pool/main/k/kdeaccessibility/kdeaccessibility_3.3.2-1.diff.gz
kdeaccessibility_3.3.2-1.dsc
to pool/main/k/kdeaccessibility/kdeaccessibility_3.3.2-1.dsc
kdeaccessibility_3.3.2-1_all.deb
to
El Domingo 23 Enero 2005 21:42, Alejandro Exojo escribió:
El Domingo, 23 de Enero de 2005 20:53, Jean Darcoux escribió:
As a solution, I recommand to replace characters like '+' by there
corresponding code (like %2B in the case of '+'). The later example
should then display the URL
On Sunday 23 Jan 2005 21:47, you wrote:
In konqueror, file associations, what do you have as rm/ram viewer
and embedder? If that app can't render the image for konqueror,
this bug should be assigned to it.
Totem is the default. It seems that it can't play the file because it doesn't
have the
kdeadmin_3.3.2-1_i386.changes uploaded successfully to localhost
along with the files:
kdeadmin_3.3.2-1.dsc
kdeadmin_3.3.2-1.diff.gz
kcmlinuz_3.3.2-1_i386.deb
kcron_3.3.2-1_i386.deb
kdat_3.3.2-1_i386.deb
kdeadmin-kfile-plugins_3.3.2-1_i386.deb
kpackage_3.3.2-1_i386.deb
Accepted:
kcmlinuz_3.3.2-1_i386.deb
to pool/main/k/kdeadmin/kcmlinuz_3.3.2-1_i386.deb
kcron_3.3.2-1_i386.deb
to pool/main/k/kdeadmin/kcron_3.3.2-1_i386.deb
kdat_3.3.2-1_i386.deb
to pool/main/k/kdeadmin/kdat_3.3.2-1_i386.deb
kdeadmin-kfile-plugins_3.3.2-1_i386.deb
to
You sent a message to the Bug tracking system which gave (in the
Subject line or encoded into the recipient at bugs.debian.org),
the number of a nonexistent Bug report (#97946).
This may be because that Bug report has been resolved for more than 28
days, and the record of it has been archived and
You sent a message to the Bug tracking system which gave (in the
Subject line or encoded into the recipient at bugs.debian.org),
the number of a nonexistent Bug report (#71870).
This may be because that Bug report has been resolved for more than 28
days, and the record of it has been archived and
You sent a message to the Bug tracking system which gave (in the
Subject line or encoded into the recipient at bugs.debian.org),
the number of a nonexistent Bug report (#181563).
This may be because that Bug report has been resolved for more than 28
days, and the record of it has been archived
You sent a message to the Bug tracking system which gave (in the
Subject line or encoded into the recipient at bugs.debian.org),
the number of a nonexistent Bug report (#122044).
This may be because that Bug report has been resolved for more than 28
days, and the record of it has been archived
You sent a message to the Bug tracking system which gave (in the
Subject line or encoded into the recipient at bugs.debian.org),
the number of a nonexistent Bug report (#99747).
This may be because that Bug report has been resolved for more than 28
days, and the record of it has been archived and
You sent a message to the Bug tracking system which gave (in the
Subject line or encoded into the recipient at bugs.debian.org),
the number of a nonexistent Bug report (#127948).
This may be because that Bug report has been resolved for more than 28
days, and the record of it has been archived
You sent a message to the Bug tracking system which gave (in the
Subject line or encoded into the recipient at bugs.debian.org),
the number of a nonexistent Bug report (#106937).
This may be because that Bug report has been resolved for more than 28
days, and the record of it has been archived
You sent a message to the Bug tracking system which gave (in the
Subject line or encoded into the recipient at bugs.debian.org),
the number of a nonexistent Bug report (#128195).
This may be because that Bug report has been resolved for more than 28
days, and the record of it has been archived
You sent a message to the Bug tracking system which gave (in the
Subject line or encoded into the recipient at bugs.debian.org),
the number of a nonexistent Bug report (#181357).
This may be because that Bug report has been resolved for more than 28
days, and the record of it has been archived
You sent a message to the Bug tracking system which gave (in the
Subject line or encoded into the recipient at bugs.debian.org),
the number of a nonexistent Bug report (#72333).
This may be because that Bug report has been resolved for more than 28
days, and the record of it has been archived and
You sent a message to the Bug tracking system which gave (in the
Subject line or encoded into the recipient at bugs.debian.org),
the number of a nonexistent Bug report (#72350).
This may be because that Bug report has been resolved for more than 28
days, and the record of it has been archived and
You sent a message to the Bug tracking system which gave (in the
Subject line or encoded into the recipient at bugs.debian.org),
the number of a nonexistent Bug report (#103439).
This may be because that Bug report has been resolved for more than 28
days, and the record of it has been archived
You sent a message to the Bug tracking system which gave (in the
Subject line or encoded into the recipient at bugs.debian.org),
the number of a nonexistent Bug report (#72407).
This may be because that Bug report has been resolved for more than 28
days, and the record of it has been archived and
You sent a message to the Bug tracking system which gave (in the
Subject line or encoded into the recipient at bugs.debian.org),
the number of a nonexistent Bug report (#75073).
This may be because that Bug report has been resolved for more than 28
days, and the record of it has been archived and
You sent a message to the Bug tracking system which gave (in the
Subject line or encoded into the recipient at bugs.debian.org),
the number of a nonexistent Bug report (#77853).
This may be because that Bug report has been resolved for more than 28
days, and the record of it has been archived and
You sent a message to the Bug tracking system which gave (in the
Subject line or encoded into the recipient at bugs.debian.org),
the number of a nonexistent Bug report (#79060).
This may be because that Bug report has been resolved for more than 28
days, and the record of it has been archived and
You sent a message to the Bug tracking system which gave (in the
Subject line or encoded into the recipient at bugs.debian.org),
the number of a nonexistent Bug report (#87412).
This may be because that Bug report has been resolved for more than 28
days, and the record of it has been archived and
You sent a message to the Bug tracking system which gave (in the
Subject line or encoded into the recipient at bugs.debian.org),
the number of a nonexistent Bug report (#89695).
This may be because that Bug report has been resolved for more than 28
days, and the record of it has been archived and
53 matches
Mail list logo
