public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problems after upgrading
Date: Tue, 30 May 2006 18:38:38 -0700	[thread overview]
Message-ID: <7573e9640605301838l266629nd226aa9e7919c206@mail.gmail.com> (raw)
In-Reply-To: <447A8A7F.708@gmail.com>

On 5/28/06, Colleen Beamer <colleen.beamer@gmail.com> wrote:
> Hi all,
>
> Yesterday, among the packages in my upgrade list was kde-3.5.  After
> getting the problem with perl-cleaner solved (thanks to the help on this
> list), the upgrade went apparently smoothly.
>
> According to what I read in some of the Gentoo documentation after
> booting into kde-3.5, I had to rebuild some of the packages against
> kde-3.5 in order for them to work, for example amarok.  The rebuild of
> this went fine.  I can listen to my music collection with amarok.  I can
> play CD's with kscd.  The problem seems to be with kaudio creator.  And
> it is acting erratically.
>
> First, when I tried to rip a cd, it wouldn't encode it, nor would it let
> me configure the encoder (oggenc).  I'm not sure how, but somehow, I got
> passed that, but the application would freeze part way through the
> ripping process.  When I got the message that the application was not
> responding and I responded affirmatively when asked if I wanted to
> terminate it, ps -ax still showed the application as running and I
> couldn't kill it with kill -9.  At this point, if I continued using the
> computer without a reboot, inevitably some other application would
> freeze up on me.  However, if I rebooted and didn't use kaudiocreator
> again, everything seems to be fine.
>
> This time, I did check the list archives, but didn't notice anything
> relevant.  I checked the bug list as well and there appears to be a
> couple of kdemultimedia bugs that have been reported.  Whether or not my
> problem has something to do with the kdemultimedia bugs, I'm not sure.
> However, if anyone has any ideas here, I am open to suggestions.

Nothing obvious comes to mind, except checking dmesg (or
/var/log/messages) for anything ominous occuring at the time of the
trouble.  You could also check ~/.xsession-errors for any error
messages from application(s).

-Richard
-- 
gentoo-user@gentoo.org mailing list



      reply	other threads:[~2006-05-31  1:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-29  5:45 [gentoo-user] Problems after upgrading Colleen Beamer
2006-05-31  1:38 ` Richard Fish [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7573e9640605301838l266629nd226aa9e7919c206@mail.gmail.com \
    --to=bigfish@asmallpond.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox