public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: meino.cramer@gmx.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: Shutting down process hangs - how to proceed?
Date: Sun, 20 Sep 2009 18:15:52 +0200	[thread overview]
Message-ID: <20090920161552.GC5807@solfire> (raw)
In-Reply-To: <h95k6j$aq8$1@ger.gmane.org>

walt <w41ter@gmail.com> [09-09-20 18:14]:
> On 09/19/2009 07:17 PM, meino.cramer@gmx.de wrote:
> >walt<w41ter@gmail.com>  [09-09-20 04:13]:
> >>On 09/19/2009 05:07 PM, meino.cramer@gmx.de wrote:
> >>>walt<w41ter@gmail.com>   [09-09-20 02:03]:
> >>>>On 09/19/2009 05:31 AM, meino.cramer@gmx.de wrote:
> >>>>
> >>>>>Nonetheless I added the UNLOAD_ON_STOP="no" to 
> >>>>>/etc/conf.d/alsasound
> >>>>>and we will see what happens.
> >>>>
> >>>>Did you try stopping the alsa service manually?
> >>>>
> >>>>#/etc/init.d/alsasound stop
> >>>>
> >>>
> >>>This gave me errors, since my Webcam's audio part isn't implemented 
> >>>as
> >>>full audio device, but it does not hang:
> 
> >...but this "problem" was there long before the system cannot be
> >shutdown anymore and I think it is not clean but the root of all
> >evil....
> 
> Well, in any case you should be able to eliminate those error messages
> if you delete /etc/asound.* and then repeat the alsactl store.
> 

solfire:/home/mccramer>l /etc/asound.state
-rw-r--r-- 1 root root 10122 2009-08-06 18:05 /etc/asound.state
solfire:/home/mccramer>sudo rm -f /etc/asound.state
solfire:/home/mccramer>sudo alsactl store
alsactl: get_control:249: Cannot read control '2,0,0,Mic Capture Volume,0': Invalid argument
solfire:/home/mccramer>


-- 
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.




  reply	other threads:[~2009-09-20 16:16 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-19  1:39 [gentoo-user] Shutting down process hangs - how to proceed? meino.cramer
2009-09-19  1:57 ` Dale
2009-09-19  2:08   ` meino.cramer
2009-09-19  2:42     ` Dale
2009-09-19  9:27     ` Mick
2009-09-19 11:11       ` Pupino
2009-09-19 11:25         ` meino.cramer
2009-09-19 11:47           ` pk
2009-09-19 12:31             ` meino.cramer
2009-09-19 20:17               ` Mick
2009-09-19 21:59               ` [gentoo-user] " walt
2009-09-20  0:07                 ` meino.cramer
2009-09-20  1:09                   ` walt
2009-09-20  2:17                     ` meino.cramer
2009-09-20 16:13                       ` walt
2009-09-20 16:15                         ` meino.cramer [this message]
2009-09-20 17:16                           ` walt
2009-09-21  2:40                             ` meino.cramer
2009-09-21 17:30                               ` walt
2009-09-21 17:43                                 ` meino.cramer
2009-09-21 17:52                                   ` Pupino
2009-09-21 18:30                   ` walt
2009-09-19 14:08           ` [gentoo-user] " Pupino
2009-09-19 13:16       ` covici
2009-09-20 16:23         ` meino.cramer
2009-09-20 16:42           ` covici
2009-09-20 18:46             ` Dale
2009-09-20 19:17               ` covici
2009-09-20 20:00                 ` Dale
2009-09-19 12:25 ` Frank Steinmetzger
2009-09-19 12:47   ` meino.cramer

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=20090920161552.GC5807@solfire \
    --to=meino.cramer@gmx.de \
    --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