I'm also seeing artsd consuming all my CPU. Worse yet, I can't stop it. If
I kill the process it just respawns. Since artsd isn't mentioned in
inittab, I don't know how to prevent it from constantly respawning. I
closed every KDE program and killed kdeinit, but artsd keeps respawning.
This is
Your message dated Sun, 28 May 2006 19:31:26 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#369292: artsd crashes when playing any sound
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again.
I have to apologize. I just dist-upgraded and I realized that this bug
is in fact a bug of the ALSA system, specifically from libasound.
With the upgrade, the bug changed but it's still there. Anyway, I know
now that arts is NOT the problem
Package: libqt3-mt
Version: 3:3.3.6-2
Severity: important
Hi,
recently I reported a crash of kdevelop to it's -devel mailing list (I'm
using their svn version) and it was pointed out to me that the reason
for the crash is actually a patched Qt3. Thus I'm reporting this here,
the link to the bugre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: arts
Version: 1.5.3-1
Severity: Grave
Justification: No sound in KDE
Hi,
I'm Ramiro Cano.
Since the last dist-upgrade, artsd always crashes when trying to play
any sound. So, it happens that it begins to open KDE crash windows until
I close
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The problem I wrote this report for doesn't happen anymore.
Any administrator can close this thread.
Thank you for your work. Regards,
Ramiro Cano.
- --
+--++
|(o_ powered |Death Master|
|(o_ (o_
SVN commit 546042 by mornfall:
Split up the debian package into
adept-{manager,installer,updater,notifier}. Keep "adept" as a
metapackage. Pull this together into a 2.0.1 release.
_M. (directory)
A debian/adept-common.install
A debian/adept-installer.in
Your message dated Sun, 28 May 2006 11:02:27 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#356876: fixed in kdelibs 4:3.5.3-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, 28 May 2006 11:02:27 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#310873: fixed in kdelibs 4:3.5.3-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:
kdelibs-data_3.5.3-1_all.deb
to pool/main/k/kdelibs/kdelibs-data_3.5.3-1_all.deb
kdelibs-dbg_3.5.3-1_amd64.deb
to pool/main/k/kdelibs/kdelibs-dbg_3.5.3-1_amd64.deb
kdelibs4-dev_3.5.3-1_amd64.deb
to pool/main/k/kdelibs/kdelibs4-dev_3.5.3-1_amd64.deb
kdelibs4-doc_3.5.3-1_all.deb
to
kdelibs_3.5.3-1_amd64.changes uploaded successfully to localhost
along with the files:
kdelibs_3.5.3-1.dsc
kdelibs_3.5.3.orig.tar.gz
kdelibs_3.5.3-1.diff.gz
kdelibs_3.5.3-1_all.deb
kdelibs-data_3.5.3-1_all.deb
kdelibs4-doc_3.5.3-1_all.deb
kdelibs4c2a_3.5.3-1_amd64.deb
kdelibs4-dev_3
Probably you are the uploader of the following file(s) in
the Debian upload queue directory:
kdelibs_3.5.3-1.diff.gz
kdelibs_3.5.3-1.dsc
kdelibs_3.5.3-1_all.deb
kdelibs_3.5.3.orig.tar.gz
This looks like an upload, but a .changes file is missing, so the job
cannot be processed.
If no .chang
#
# bts-link upstream status pull for source package kdepim
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #328445
# * http://bugs.kde.org/show_bug.cgi?id=118926
# * remote status changed: (?) -> RESOLVED
# * remote
#
# bts-link upstream status pull for source package kdebase
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #350561
# * http://bugs.kde.org/show_bug.cgi?id=66941
# * remote status changed: UNCONFIRMED -> NEW
forwarde
Processing commands for [EMAIL PROTECTED]:
> #
> # bts-link upstream status pull for source package kdepim
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user [EMAIL PROTECTED]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
> # remote status report fo
Processing commands for [EMAIL PROTECTED]:
> #
> # bts-link upstream status pull for source package kdebase
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user [EMAIL PROTECTED]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
> # remote status report f
On Sunday, 28 May 2006 16:19, Pierre Habouzit wrote:
> > Since some time, konqueror randomly activates its access keys, which
> > is a bit annoying, since the displayed tags often hide parts that you
> the hotkey that activates accesskeys is 'control' just hit it a second
> time to disactivate them
Package: arts
Followup-For: Bug #369160
>Downgrading libasound2 (and not anything else) makes arts work again,
> so probably a libasound2 bug.
I tried it: It still doesn´t work so good. E.g. xmms does not work with
OSS Output.
Then I tried to to:
# killall artsd
# artsd
and got the error again:
Le Dim 28 Mai 2006 08:05, Ulrich Eckhardt a écrit :
> Package: konqueror
> Version: 3.5.2-2+b1
>
> Hi!
>
> Since some time, konqueror randomly activates its access keys, which
> is a bit annoying, since the displayed tags often hide parts that you
> are currently reading. Now, this is _nothing_ com
Package: konqueror
Version: 4:3.5.2-2+b1
Severity: normal
Copy some short text (for example an e-mail address: 201.8.87.253)
to the clipboard. Open konqueror and go to: http://ordb.org/submit/
Try to paste text into the host/ip address field (textarea) by
pressing Ctrl-V. Everythings works fine.
Your message dated Sun, 28 May 2006 12:04:31 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in NMU of arts 1.5.3-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 respo
Package: arts
Version: 1.5.3-1
Followup-For: Bug #369160
Downgrading libasound2 (and not anything else) makes arts work again, so
probably a libasound2 bug.
Regards, Thue
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture:
Package: arts
Version: 1.5.3-1
Followup-For: Bug #369160
This bug is the same as #369077.
Regards, Thue
-- 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 2.6.1
Package: arts
Version: 1.5.3-1
Followup-For: Bug #369160
I have the same problem on my system.
Regards, Thue
-- 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: konqueror
Version: 3.5.2-2+b1
Hi!
Since some time, konqueror randomly activates its access keys, which is a bit
annoying, since the displayed tags often hide parts that you are currently
reading. Now, this is _nothing_ compared to how annoying this is when you are
currently filling in
25 matches
Mail list logo