GNOME Bugzilla – Bug 463147
[2.18 only?] crash in Volume Control: starting skype
Last modified: 2008-06-01 20:45:33 UTC
What were you doing when the application crashed? starting skype Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 36601856 vsize: 36601856 resident: 18341888 share: 15630336 rss: 18341888 rss_rlim: 4294967295 CPU usage: start_time: 1186146275 rtime: 19 utime: 14 stime: 5 cutime:2 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/mixer_applet2' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208723120 (LWP 3007)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 152559
Thread 1 (Thread -1208723120 (LWP 3007))
----------- .xsession-errors (41 sec old) --------------------- localuser:ckg being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2767 error getting update info: Cannot open/read repomd.xml file for repository: fedora ** Message: <info> You are now connected to the wireless network '2WIRE778'. --------------------------------------------------
*** Bug 466167 has been marked as a duplicate of this bug. ***
*** Bug 466217 has been marked as a duplicate of this bug. ***
*** Bug 466227 has been marked as a duplicate of this bug. ***
*** Bug 467511 has been marked as a duplicate of this bug. ***
*** Bug 467531 has been marked as a duplicate of this bug. ***
*** Bug 467575 has been marked as a duplicate of this bug. ***
*** Bug 468357 has been marked as a duplicate of this bug. ***
*** Bug 468974 has been marked as a duplicate of this bug. ***
*** Bug 469016 has been marked as a duplicate of this bug. ***
*** Bug 469219 has been marked as a duplicate of this bug. ***
*** Bug 464045 has been marked as a duplicate of this bug. ***
*** Bug 464562 has been marked as a duplicate of this bug. ***
*** Bug 464712 has been marked as a duplicate of this bug. ***
*** Bug 465751 has been marked as a duplicate of this bug. ***
*** Bug 466318 has been marked as a duplicate of this bug. ***
*** Bug 466563 has been marked as a duplicate of this bug. ***
*** Bug 467986 has been marked as a duplicate of this bug. ***
*** Bug 468185 has been marked as a duplicate of this bug. ***
*** Bug 471057 has been marked as a duplicate of this bug. ***
*** Bug 470632 has been marked as a duplicate of this bug. ***
*** Bug 470555 has been marked as a duplicate of this bug. ***
*** Bug 470290 has been marked as a duplicate of this bug. ***
*** Bug 470085 has been marked as a duplicate of this bug. ***
*** Bug 471678 has been marked as a duplicate of this bug. ***
*** Bug 473800 has been marked as a duplicate of this bug. ***
*** Bug 474006 has been marked as a duplicate of this bug. ***
*** Bug 472278 has been marked as a duplicate of this bug. ***
*** Bug 473475 has been marked as a duplicate of this bug. ***
*** Bug 474359 has been marked as a duplicate of this bug. ***
*** Bug 474279 has been marked as a duplicate of this bug. ***
*** Bug 474682 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 475417 has been marked as a duplicate of this bug. ***
*** Bug 475433 has been marked as a duplicate of this bug. ***
*** Bug 475491 has been marked as a duplicate of this bug. ***
*** Bug 475722 has been marked as a duplicate of this bug. ***
*** Bug 476075 has been marked as a duplicate of this bug. ***
*** Bug 476097 has been marked as a duplicate of this bug. ***
*** Bug 476746 has been marked as a duplicate of this bug. ***
*** Bug 476777 has been marked as a duplicate of this bug. ***
*** Bug 479678 has been marked as a duplicate of this bug. ***
*** Bug 479975 has been marked as a duplicate of this bug. ***
*** Bug 477277 has been marked as a duplicate of this bug. ***
*** Bug 477669 has been marked as a duplicate of this bug. ***
*** Bug 477996 has been marked as a duplicate of this bug. ***
*** Bug 478288 has been marked as a duplicate of this bug. ***
*** Bug 479266 has been marked as a duplicate of this bug. ***
*** Bug 479876 has been marked as a duplicate of this bug. ***
*** Bug 480652 has been marked as a duplicate of this bug. ***
*** Bug 480674 has been marked as a duplicate of this bug. ***
*** Bug 480775 has been marked as a duplicate of this bug. ***
*** Bug 480913 has been marked as a duplicate of this bug. ***
*** Bug 480942 has been marked as a duplicate of this bug. ***
*** Bug 481131 has been marked as a duplicate of this bug. ***
*** Bug 481346 has been marked as a duplicate of this bug. ***
*** Bug 483024 has been marked as a duplicate of this bug. ***
*** Bug 481538 has been marked as a duplicate of this bug. ***
*** Bug 481816 has been marked as a duplicate of this bug. ***
*** Bug 481866 has been marked as a duplicate of this bug. ***
*** Bug 481972 has been marked as a duplicate of this bug. ***
*** Bug 482368 has been marked as a duplicate of this bug. ***
*** Bug 482867 has been marked as a duplicate of this bug. ***
*** Bug 484338 has been marked as a duplicate of this bug. ***
*** Bug 473251 has been marked as a duplicate of this bug. ***
*** Bug 474600 has been marked as a duplicate of this bug. ***
*** Bug 474738 has been marked as a duplicate of this bug. ***
*** Bug 477671 has been marked as a duplicate of this bug. ***
*** Bug 478778 has been marked as a duplicate of this bug. ***
*** Bug 479263 has been marked as a duplicate of this bug. ***
*** Bug 480136 has been marked as a duplicate of this bug. ***
It seem a bug in ALSA hda-intel driver or linux kernel ACPI driver especially on my two ASUS main boards with intel chip and realtek codec. It seems the alsa driver that can't identify the audio codec configuration form BIOS correctly causes this gnome volumn contorl crash.
This bug is happend by Gizmo Project too.
*** Bug 484641 has been marked as a duplicate of this bug. ***
*** Bug 486591 has been marked as a duplicate of this bug. ***
*** Bug 487672 has been marked as a duplicate of this bug. ***
*** Bug 486300 has been marked as a duplicate of this bug. ***
*** Bug 485040 has been marked as a duplicate of this bug. ***
*** Bug 485049 has been marked as a duplicate of this bug. ***
*** Bug 486290 has been marked as a duplicate of this bug. ***
*** Bug 487076 has been marked as a duplicate of this bug. ***
*** Bug 487186 has been marked as a duplicate of this bug. ***
*** Bug 487328 has been marked as a duplicate of this bug. ***
*** Bug 487536 has been marked as a duplicate of this bug. ***
*** Bug 487690 has been marked as a duplicate of this bug. ***
*** Bug 487704 has been marked as a duplicate of this bug. ***
*** Bug 487887 has been marked as a duplicate of this bug. ***
*** Bug 487910 has been marked as a duplicate of this bug. ***
*** Bug 487846 has been marked as a duplicate of this bug. ***
*** Bug 488015 has been marked as a duplicate of this bug. ***
*** Bug 488018 has been marked as a duplicate of this bug. ***
*** Bug 488108 has been marked as a duplicate of this bug. ***
*** Bug 488367 has been marked as a duplicate of this bug. ***
*** Bug 487450 has been marked as a duplicate of this bug. ***
*** Bug 487342 has been marked as a duplicate of this bug. ***
*** Bug 486866 has been marked as a duplicate of this bug. ***
*** Bug 485451 has been marked as a duplicate of this bug. ***
*** Bug 487637 has been marked as a duplicate of this bug. ***
*** Bug 487589 has been marked as a duplicate of this bug. ***
*** Bug 487581 has been marked as a duplicate of this bug. ***
*** Bug 487569 has been marked as a duplicate of this bug. ***
*** Bug 487564 has been marked as a duplicate of this bug. ***
*** Bug 487551 has been marked as a duplicate of this bug. ***
*** Bug 488102 has been marked as a duplicate of this bug. ***
*** Bug 488305 has been marked as a duplicate of this bug. ***
*** Bug 487900 has been marked as a duplicate of this bug. ***
*** Bug 487897 has been marked as a duplicate of this bug. ***
*** Bug 487776 has been marked as a duplicate of this bug. ***
*** Bug 488430 has been marked as a duplicate of this bug. ***
I have the debuginfo packages installed, but I can't currently reproduce the crash. In case it matters, lspci lists my audio controller as: 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) That's actually the audio controller from an Intel ICH8R. It uses the snd_hda_intel driver.
*** Bug 488559 has been marked as a duplicate of this bug. ***
Okay, I got it to crash again. Apparently it will only crash once per GNOME session. Here's the backtrace with the debug symbols I have installed: Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 279363584 vsize: 279363584 resident: 18026496 share: 14368768 rss: 18026496 rss_rlim: 18446744073709551615 CPU usage: start_time: 1192911977 rtime: 20 utime: 20 stime: 0 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/mixer_applet2' Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 46912496381616 (LWP 3194)] 0x00000033dc00d945 in waitpid () from /lib64/libpthread.so.0
+ Trace 171786
Thread 1 (Thread 46912496381616 (LWP 3194))
*** Bug 488641 has been marked as a duplicate of this bug. ***
*** Bug 488910 has been marked as a duplicate of this bug. ***
*** Bug 489121 has been marked as a duplicate of this bug. ***
*** Bug 488452 has been marked as a duplicate of this bug. ***
*** Bug 488614 has been marked as a duplicate of this bug. ***
*** Bug 488786 has been marked as a duplicate of this bug. ***
*** Bug 489377 has been marked as a duplicate of this bug. ***
*** Bug 489475 has been marked as a duplicate of this bug. ***
*** Bug 489789 has been marked as a duplicate of this bug. ***
*** Bug 489792 has been marked as a duplicate of this bug. ***
*** Bug 489802 has been marked as a duplicate of this bug. ***
*** Bug 489784 has been marked as a duplicate of this bug. ***
*** Bug 488659 has been marked as a duplicate of this bug. ***
*** Bug 488381 has been marked as a duplicate of this bug. ***
*** Bug 489834 has been marked as a duplicate of this bug. ***
*** Bug 489820 has been marked as a duplicate of this bug. ***
*** Bug 490043 has been marked as a duplicate of this bug. ***
*** Bug 490035 has been marked as a duplicate of this bug. ***
*** Bug 490006 has been marked as a duplicate of this bug. ***
*** Bug 489990 has been marked as a duplicate of this bug. ***
*** Bug 489971 has been marked as a duplicate of this bug. ***
*** Bug 490168 has been marked as a duplicate of this bug. ***
*** Bug 490210 has been marked as a duplicate of this bug. ***
*** Bug 490242 has been marked as a duplicate of this bug. ***
*** Bug 490275 has been marked as a duplicate of this bug. ***
*** Bug 490561 has been marked as a duplicate of this bug. ***
This bug is associated most likely with skype trying to impose its own settings on the Capture Mux. The Volume Control g.a. crashes repeatedly and reliably in approx. 30% cases. Sometimes if it hasn't crashed settings of the capture channel are altered so skype is unusable until I unblock the mux input (this symptom might be unrelated). The latter problem rarely occurred on FC 6 as well but it got worse now (or my new computer is faster/ whatever). The workaround I found was to get rid of the Volume Control gnome-applet (sorry guys it is unusable in the current form) and create a launcher which starts "xterm alsamixer". Having alsamixer I'm able to adjust the volume. (there are other tools available as well). When skype starts (or rather makes a call - for example to "Skype Test Call") you can observe how alsamixer shows changing volume of the Capture Mux channel. If you guys really cannot replicate the problem I may run the applet in gdb and try getting more info. However I think that somebody who designed/wrote the applet or has time to inspect the source code should be able to easily pinpoint the root cause of the issue knowing what has already been observed. Regards, Adam
*** Bug 490767 has been marked as a duplicate of this bug. ***
*** Bug 490750 has been marked as a duplicate of this bug. ***
*** Bug 490676 has been marked as a duplicate of this bug. ***
*** Bug 490664 has been marked as a duplicate of this bug. ***
*** Bug 490494 has been marked as a duplicate of this bug. ***
*** Bug 490440 has been marked as a duplicate of this bug. ***
*** Bug 490116 has been marked as a duplicate of this bug. ***
*** Bug 490119 has been marked as a duplicate of this bug. ***
*** Bug 489857 has been marked as a duplicate of this bug. ***
*** Bug 489829 has been marked as a duplicate of this bug. ***
*** Bug 489737 has been marked as a duplicate of this bug. ***
*** Bug 489642 has been marked as a duplicate of this bug. ***
*** Bug 489610 has been marked as a duplicate of this bug. ***
*** Bug 489609 has been marked as a duplicate of this bug. ***
*** Bug 489567 has been marked as a duplicate of this bug. ***
*** Bug 489476 has been marked as a duplicate of this bug. ***
*** Bug 489376 has been marked as a duplicate of this bug. ***
*** Bug 488999 has been marked as a duplicate of this bug. ***
*** Bug 488983 has been marked as a duplicate of this bug. ***
*** Bug 488980 has been marked as a duplicate of this bug. ***
*** Bug 488975 has been marked as a duplicate of this bug. ***
*** Bug 488871 has been marked as a duplicate of this bug. ***
*** Bug 488792 has been marked as a duplicate of this bug. ***
*** Bug 488764 has been marked as a duplicate of this bug. ***
*** Bug 488688 has been marked as a duplicate of this bug. ***
*** Bug 488677 has been marked as a duplicate of this bug. ***
*** Bug 487314 has been marked as a duplicate of this bug. ***
*** Bug 485230 has been marked as a duplicate of this bug. ***
*** Bug 490871 has been marked as a duplicate of this bug. ***
What I wrote in my previous post needs to be clarified. The workaround which I suggested (using alsamixer) screws up skype completly. So we have to live with Volume Control applet when I am to use skype on Linux. One day I will move to "ekiga" and say goodbye to skype but I need to do more testing. Further observations and a workaround: What crashes Volume Control applet is most likely adding a new channel to Playback which is done by skype when it starts (remember that I mentioned that the applet always crashes on skype's start). I didn't have time to debug but my gut feeling is that this is the root cause. The new channel is "Playback PCM". When Volume Control is started after reboot it only shows Playback Master. Sometimes Recording Capture is muted (what I mentioned already and is a separate issue having probably more to do with /sbin/salsa). I did the following test: 1. started skype (it altered the alsa mixer settings) 2. su - 3. alsactl save 4. reboot 5. started the Volume Control applet 7. su - 6. alsactl restore The Volume Control applet crashed in the same way it crashes with skype. Tweaking it so it works (without asking too many questions): 0. start skype and call "alsactl save" as root 1. Comment out calling /sbin/salsa from /etc/rc.d/init.d/halt get rid of salsa: mv /sbin/salsa /sbin/salsa.bak This is probably not needed but I don't like salsa messing around. Where does it restore settings? I haven't found the place where it is called from. Anyway this is NOT working properly and I decided to get rid off salsa with no adverse effects on the startup scripts. 2. Add "alsactl restore" to /etc/rc.d/rc.local Note that while true; do alsactl restore; done doesn't appear to crash the applet once the additional Playback PCM channel has been added. Also read this (they came across the same tweak): http://fcp.surfsite.org/modules/newbb/viewtopic.php?topic_id=41949&forum=10&post_id=190681
Thanks a lot for your very helpful comment! (In reply to comment #168) > The workaround which I suggested (using alsamixer) screws up skype completly. Can we say the bug is most likely in ALSA then ? (-driver, -libs, utils?) > What crashes Volume Control applet is most likely adding a new channel to > Playback which is done by skype when it starts (remember that I mentioned that > the applet always crashes on skype's start). I didn't have time to debug but my > gut feeling is that this is the root cause. This is likely to cause trouble, since this is not a common use case! (usually the number of control is static). I wonder if it's a correct practice in ALSA (alsamixer should not crash if this was really supported) > I did the following test: > 1. started skype (it altered the alsa mixer settings) > 2. su - > 3. alsactl save > 4. reboot > 5. started the Volume Control applet > 7. su - > 6. alsactl restore > The Volume Control applet crashed in the same way it crashes with skype. Can you attach the /var/lib/alsa/asound.state or /etc/asound.names before and after starting skype. > 1. Comment out calling /sbin/salsa from /etc/rc.d/init.d/halt > get rid of salsa: > mv /sbin/salsa /sbin/salsa.bak What is "this" salsa? OSS emulation? (there are multiple project called salsa around ALSA) Thanks again
1. The bug is not related to ALSA proper. The bug is in Volume Control gnome applet. 2. The assumption that anything what ALSA's API lets changing (including the number of controls) will not be changed is wrong. Specifically the number of controls is not static. And this is exactly what happens here - skype changes that number. BTW I haven't said that alsamixer crashes. Alsamixer running when skype starts prevents skype from doing its job and skype doesn't work (looks like it cannot access the audio input). 3. Alsa state before and after starting skype will be attached to the bug record in the next step. You may use these files to reproduce the problem by calling "alsactl -f <whatever> restore" 4. salsa is a program supposed to save and restore the state of alsa mixer on Fedora 7. Had it worked correctly the Volume Control bug would have appeared only once on a particular machine (on the first run of skype). I got rid of it as a precaution since I want to pre-set the mixer configuration using alsactl and I don't want anything to mess up with these settings. Here is what salsa says about itself: [root@localhost ~]# /sbin/salsa --help ALSA volume settings handler, Copyright 2007 Red Hat, Inc. This software may be freely redistributed under the terms of the GNU public license. Usage: salsa [options] [card number] Options: -l - Load volume settings -s - Save volume settings Card number: ## - An affected card. If it isn't specified, configure all installed sound cards.
Created attachment 98009 [details] alsa mixer state after starting skype
Created attachment 98010 [details] alsa mixer state before starting skype
*** Bug 491009 has been marked as a duplicate of this bug. ***
*** Bug 491005 has been marked as a duplicate of this bug. ***
*** Bug 490983 has been marked as a duplicate of this bug. ***
*** Bug 490978 has been marked as a duplicate of this bug. ***
*** Bug 491076 has been marked as a duplicate of this bug. ***
*** Bug 489527 has been marked as a duplicate of this bug. ***
*** Bug 489560 has been marked as a duplicate of this bug. ***
*** Bug 489844 has been marked as a duplicate of this bug. ***
*** Bug 490714 has been marked as a duplicate of this bug. ***
*** Bug 489941 has been marked as a duplicate of this bug. ***
*** Bug 478900 has been marked as a duplicate of this bug. ***
*** Bug 458345 has been marked as a duplicate of this bug. ***
*** Bug 491244 has been marked as a duplicate of this bug. ***
*** Bug 491374 has been marked as a duplicate of this bug. ***
*** Bug 491489 has been marked as a duplicate of this bug. ***
*** Bug 491500 has been marked as a duplicate of this bug. ***
*** Bug 491569 has been marked as a duplicate of this bug. ***
*** Bug 491561 has been marked as a duplicate of this bug. ***
*** Bug 491560 has been marked as a duplicate of this bug. ***
*** Bug 491625 has been marked as a duplicate of this bug. ***
*** Bug 491657 has been marked as a duplicate of this bug. ***
*** Bug 491879 has been marked as a duplicate of this bug. ***
*** Bug 491919 has been marked as a duplicate of this bug. ***
*** Bug 491853 has been marked as a duplicate of this bug. ***
*** Bug 491697 has been marked as a duplicate of this bug. ***
*** Bug 491675 has been marked as a duplicate of this bug. ***
*** Bug 491719 has been marked as a duplicate of this bug. ***
*** Bug 491782 has been marked as a duplicate of this bug. ***
*** Bug 491813 has been marked as a duplicate of this bug. ***
*** Bug 491856 has been marked as a duplicate of this bug. ***
*** Bug 491867 has been marked as a duplicate of this bug. ***
*** Bug 491877 has been marked as a duplicate of this bug. ***
*** Bug 491972 has been marked as a duplicate of this bug. ***
*** Bug 491996 has been marked as a duplicate of this bug. ***
*** Bug 492037 has been marked as a duplicate of this bug. ***
*** Bug 491771 has been marked as a duplicate of this bug. ***
*** Bug 492053 has been marked as a duplicate of this bug. ***
*** Bug 492155 has been marked as a duplicate of this bug. ***
*** Bug 492163 has been marked as a duplicate of this bug. ***
*** Bug 492174 has been marked as a duplicate of this bug. ***
*** Bug 492296 has been marked as a duplicate of this bug. ***
*** Bug 492295 has been marked as a duplicate of this bug. ***
*** Bug 492279 has been marked as a duplicate of this bug. ***
*** Bug 492256 has been marked as a duplicate of this bug. ***
*** Bug 492254 has been marked as a duplicate of this bug. ***
*** Bug 492229 has been marked as a duplicate of this bug. ***
*** Bug 492384 has been marked as a duplicate of this bug. ***
*** Bug 492382 has been marked as a duplicate of this bug. ***
*** Bug 492421 has been marked as a duplicate of this bug. ***
*** Bug 492429 has been marked as a duplicate of this bug. ***
*** Bug 492438 has been marked as a duplicate of this bug. ***
*** Bug 492443 has been marked as a duplicate of this bug. ***
*** Bug 492459 has been marked as a duplicate of this bug. ***
*** Bug 492461 has been marked as a duplicate of this bug. ***
*** Bug 492490 has been marked as a duplicate of this bug. ***
*** Bug 492547 has been marked as a duplicate of this bug. ***
*** Bug 492612 has been marked as a duplicate of this bug. ***
*** Bug 492648 has been marked as a duplicate of this bug. ***
*** Bug 492682 has been marked as a duplicate of this bug. ***
*** Bug 492713 has been marked as a duplicate of this bug. ***
*** Bug 492728 has been marked as a duplicate of this bug. ***
*** Bug 492877 has been marked as a duplicate of this bug. ***
*** Bug 492790 has been marked as a duplicate of this bug. ***
*** Bug 492936 has been marked as a duplicate of this bug. ***
*** Bug 493077 has been marked as a duplicate of this bug. ***
*** Bug 493078 has been marked as a duplicate of this bug. ***
*** Bug 493106 has been marked as a duplicate of this bug. ***
*** Bug 493578 has been marked as a duplicate of this bug. ***
*** Bug 493376 has been marked as a duplicate of this bug. ***
*** Bug 493666 has been marked as a duplicate of this bug. ***
*** Bug 494689 has been marked as a duplicate of this bug. ***
*** Bug 494720 has been marked as a duplicate of this bug. ***
*** Bug 494929 has been marked as a duplicate of this bug. ***
*** Bug 495692 has been marked as a duplicate of this bug. ***
*** Bug 495774 has been marked as a duplicate of this bug. ***
*** Bug 495807 has been marked as a duplicate of this bug. ***
*** Bug 496121 has been marked as a duplicate of this bug. ***
*** Bug 497261 has been marked as a duplicate of this bug. ***
*** Bug 497262 has been marked as a duplicate of this bug. ***
*** Bug 497561 has been marked as a duplicate of this bug. ***
*** Bug 497595 has been marked as a duplicate of this bug. ***
*** Bug 497614 has been marked as a duplicate of this bug. ***
this looks a lot like bug 448867 to me
*** Bug 493947 has been marked as a duplicate of this bug. ***
*** Bug 494009 has been marked as a duplicate of this bug. ***
*** Bug 494140 has been marked as a duplicate of this bug. ***
*** Bug 497713 has been marked as a duplicate of this bug. ***
*** Bug 496756 has been marked as a duplicate of this bug. ***
*** Bug 497792 has been marked as a duplicate of this bug. ***
*** Bug 498476 has been marked as a duplicate of this bug. ***
*** Bug 498427 has been marked as a duplicate of this bug. ***
*** Bug 497948 has been marked as a duplicate of this bug. ***
*** Bug 498067 has been marked as a duplicate of this bug. ***
*** Bug 498106 has been marked as a duplicate of this bug. ***
*** Bug 498236 has been marked as a duplicate of this bug. ***
*** Bug 498623 has been marked as a duplicate of this bug. ***
*** Bug 498950 has been marked as a duplicate of this bug. ***
*** Bug 499348 has been marked as a duplicate of this bug. ***
*** Bug 499353 has been marked as a duplicate of this bug. ***
*** Bug 499629 has been marked as a duplicate of this bug. ***
*** Bug 500027 has been marked as a duplicate of this bug. ***
*** Bug 501790 has been marked as a duplicate of this bug. ***
*** Bug 501841 has been marked as a duplicate of this bug. ***
*** Bug 502233 has been marked as a duplicate of this bug. ***
*** Bug 502296 has been marked as a duplicate of this bug. ***
*** Bug 500585 has been marked as a duplicate of this bug. ***
*** Bug 502349 has been marked as a duplicate of this bug. ***
*** Bug 502361 has been marked as a duplicate of this bug. ***
at a first glance, i have only seen feodra 2.18 reports so far. can anybody reproduce this with another distribution than fedora, or with fedora 8?
*** Bug 502413 has been marked as a duplicate of this bug. ***
*** Bug 503826 has been marked as a duplicate of this bug. ***
*** Bug 507589 has been marked as a duplicate of this bug. ***
*** Bug 507475 has been marked as a duplicate of this bug. ***
*** Bug 507306 has been marked as a duplicate of this bug. ***
*** Bug 507154 has been marked as a duplicate of this bug. ***
*** Bug 506486 has been marked as a duplicate of this bug. ***
*** Bug 506196 has been marked as a duplicate of this bug. ***
*** Bug 505679 has been marked as a duplicate of this bug. ***
*** Bug 504792 has been marked as a duplicate of this bug. ***
*** Bug 504615 has been marked as a duplicate of this bug. ***
(In reply to comment #171) > Created an attachment (id=98009) [edit] > alsa mixer state before starting skype > Thanks! the two attached files shows cleary that the control are dynamic! This is most likely to cause trouble, both in alsa-mixer and gnome mixer! For instance, "PCM" only appears after skype is started. This is really interesting and might explain other crashes (mainly bug 471133)
I'm keeping the system updated with the automatic updater and the crash did not appear since more than one month at today. Skype is now working correctly.
*** Bug 512890 has been marked as a duplicate of this bug. ***
marc-andré, i wonder whether we should mark bug 471133 as a duplicate and close this as NOTGNOME (only reports from fedora 7 so far). settings status to NEEDINFO. please reopen if anybody can reproduce this with another distribution than fedora, or with fedora 8!
(In reply to comment #296) > marc-andré, i wonder whether we should mark bug 471133 as a duplicate and > close this as NOTGNOME (only reports from fedora 7 so far). Hi! that might be a possibility. I don't think ALSA controls are meant to be dynamic. It's likely to cause crashes since this case is not well known and tested. It's probably a bug in some ALSA driver in Fedora. Anyway, it looks like there is something to fix in GNOME side: NOTGNOME looks not appropriate to me. (WONTFIX, may be :)
*** Bug 514579 has been marked as a duplicate of this bug. ***
*** Bug 514908 has been marked as a duplicate of this bug. ***
*** Bug 513930 has been marked as a duplicate of this bug. ***
*** Bug 510685 has been marked as a duplicate of this bug. ***
*** Bug 516801 has been marked as a duplicate of this bug. ***
*** Bug 519396 has been marked as a duplicate of this bug. ***
*** Bug 518389 has been marked as a duplicate of this bug. ***
*** Bug 521306 has been marked as a duplicate of this bug. ***
*** Bug 520921 has been marked as a duplicate of this bug. ***
*** Bug 520546 has been marked as a duplicate of this bug. ***
*** Bug 521951 has been marked as a duplicate of this bug. ***
*** Bug 520620 has been marked as a duplicate of this bug. ***
no new duplicates for more than two months now (we also block reports from <=2.19.x since two months). looks like this really was a 2.18 bug, closing as obsolete. if anybody CAN reproduce this with GNOME 2.22, please DO reopen this bug. thanks in advance.