mixer_applet2 freezes session

[Christian Roessner]

Binary package hint: gnome-applets

Hi,

by just right-clicking on the mixer applet, the conext menu freezes and I have to switch to a real tty and restart gdm. I have done a backtrace from tty. See attachment please.

- Jaunty release, latest update on amd64

[Christian Roessner (christian-roessner-net)]

I do not know, if this belongs to this bug, but found it right after the report.

Maybe this could also be a problem with alsa?? Very hard to report this bug.

[ 175.064915] mixer_applet2[5334] trap stack segment ip:7fd9d0ebf576 sp:7fffdd635170 error:0
[ 201.382928] mixer_applet2[5667] trap stack segment ip:7f86f2b28576 sp:7fffff29e040 error:0
[ 318.110025] kvm: emulating exchange as write
[ 9155.553971] ------------[ cut here ]------------
[ 9155.553974] WARNING: at /build/buildd/linux-2.6.28/fs/sysfs/dir.c:462 sysfs_add_one+0x4c/0x50()
[ 9155.553975] sysfs: duplicate filename '14:4' can not be created
[ 9155.553977] Modules linked in: snd_pcm_oss(+) snd_mixer_oss sound cbc aes_x86_64 aes_generic binfmt_misc bnep kvm_intel kvm acpi_cpufreq video output bridge stp tun w83627ehf hwmon_vid sbp2 ppdev parport_pc lp parport mt352 arc4 ecb saa7134_dvb videobuf_dvb dvb_core saa7134_alsa mt20xx tea5767 tda9887 tda8290 tuner rt61pci crc_itu_t saa7134 rt2x00pci rt2x00lib snd_hda_intel ir_common led_class snd_pcm snd_seq compat_ioctl32 mac80211 snd_timer videodev snd_seq_device v4l1_compat v4l2_common videobuf_dma_sg cfg80211 pcspkr videobuf_core x38_edac snd soundcore tveeprom eeprom_93cx6 edac_core iTCO_wdt iTCO_vendor_support snd_page_alloc nvidia(P) usbhid ohci1394 skge ieee1394 sky2 raid10 raid456 async_xor async_memcpy async_tx xor raid1 raid0 multipath linear fbcon tileblit font bitblit softcursor fuse uhci_hcd ehci_hcd compcache lzo_decompress lzo_compress tlsf
[ 9155.554027] Pid: 10741, comm: modprobe Tainted: P 2.6.28-4-generic #11-Ubuntu
[ 9155.554028] Call Trace:
[ 9155.554033] [<ffffffff8024d7a7>] warn_slowpath+0xb7/0xf0
[ 9155.554037] [<ffffffff802f8afb>] ? iput+0x2b/0x70
[ 9155.554039] [<ffffffff8034535b>] ? sysfs_addrm_finish+0x4b/0x130
[ 9155.554041] [<ffffffff80344819>] ? __sysfs_add_one+0x39/0xb0
[ 9155.554045] [<ffffffff80408730>] ? idr_get_empty_slot+0x110/0x2d0
[ 9155.554047] [<ffffffff804089a2>] ? ida_get_new_above+0xb2/0x220
[ 9155.554051] [<ffffffff80344410>] ? sysfs_ilookup_test+0x0/0x20
[ 9155.554053] [<ffffffff802f92ac>] ? ifind+0xbc/0xc0
[ 9155.554056] [<ffffffff80344410>] ? sysfs_ilookup_test+0x0/0x20
[ 9155.554058] [<ffffffff803446fd>] ? sysfs_find_dirent+0x2d/0x40
[ 9155.554060] [<ffffffff80344a1c>] sysfs_add_one+0x4c/0x50
[ 9155.554062] [<ffffffff80345a3b>] sysfs_do_create_link+0x10b/0x160
[ 9155.554065] [<ffffffff80345aae>] sysfs_create_link+0xe/0x10
[ 9155.554068] [<ffffffff804a85d4>] device_add+0x214/0x480
[ 9155.554071] [<ffffffff8022bc30>] ? native_store_tr+0x0/0x10
[ 9155.554074] [<ffffffff804095f7>] ? kobject_init+0x37/0xa0
[ 9155.554076] [<ffffffff804a8859>] device_register+0x19/0x20
[ 9155.554078] [<ffffffff804a8946>] device_create_vargs+0xe6/0x100
[ 9155.554082] [<ffffffff804a89ab>] device_create+0x4b/0x50
[ 9155.554088] [<ffffffff8067eeb9>] ? _spin_lock+0x9/0x10
[ 9155.554093] [<ffffffffa0933235>] sound_insert_unit+0x105/0x1d0 [soundcore]
[ 9155.554099] [<ffffffffa093345d>] register_sound_special_device+0x9d/0x210 [soundcore]
[ 9155.554102] [<ffffffff80345330>] ? sysfs_addrm_finish+0x20/0x130
[ 9155.554111] [<ffffffffa09411d9>] snd_register_oss_device+0x229/0x2a0 [snd]
[ 9...

[Chris Coulson (chrisccoulson)]

Looks like a bug in the kernel (as evident by the warning). Re-assigning.

[Christian Roessner (christian-roessner-net)]

I am not quiet sure, if this Oops belongs to the mixer problem. It also could have been a problem with KVM/OSS, which happened at the same time (unfortunately :-) ). But as I said: Difficult to debug.

The only thing that I can say is that it must have to do with Audio, this can be

- Kernel
- ALSA (OSS emulation)
- Pulseaudio
- or the mixer applet itself.

Because you have reassigned it to linux, I attach a kernel-bug-report file.

[Christian Roessner (christian-roessner-net)]

As you can see in the log, today there is no Oops. But the mixer_applet crashed again. Hope you can find an answer. Good luck.

[Chris Coulson (chrisccoulson)]

Thanks. Are you actually using the old mixer applet, or the new volume control applet? The old mixer applet is deprecated i Jaunty and my understanding is that it will be no longer built with gnome-media soon.

[Christian Roessner (christian-roessner-net)]

This is from ps aux:

/usr/lib/gnome-applets/mixer_applet2 --oaf-activate-iid=OAFIID:GNOME_MixerApplet_Factory --oaf-ior-fd=31

Is removed the applet and re-inserted into the panel. Same mixer-applet. So I guess it is the newer one.

It has a horizontal volume slider, if clicking with left button on it. I then can choose the volume control without problems. So it really seems to be a bug in the applet, doesn´t it?

And one strange thing: If I try to fix the position of the applet in the panel, the applet crashes and needs reloading.

[...]

Just tried to make some screenshots and :-) can not get rid of the little window in the right upper corner. So I will kill it by PID.

See:

http://www.roessner-net.com/bilder/Bildschirmfoto1.png
http://www.roessner-net.com/bilder/Bildschirmfoto2.png

[Chris Coulson (chrisccoulson)]

That is still the old applet. The new applet should get spawned by gnome-session and will display in the notification area if you have any sound devices. If you have no sound devices, then it won't display.

The "mixer_applet" is basically deprecated and you should migrate to the new applet.

The new applet is called "gnome-volume-control-applet". What is the output of "pas aux | grep volume"?

[Chris Coulson (chrisccoulson)]

Obviously, I meant "ps aux | grep volume" in my last response

[Christian Roessner (christian-roessner-net)]

croessner@desktop ~ $ ps aux | grep volume
1000 5097 0.0 0.3 245140 12944 ? S 19:22 0:00 gnome-volume-control-applet
1000 5099 0.0 0.0 45516 3304 ? S 19:22 0:00 /usr/lib/gvfs/gvfs-hal-volume-monitor
1000 5101 0.0 0.0 46368 2812 ? S 19:22 0:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
1000 5416 0.0 0.0 7492 904 pts/0 R+ 19:23 0:00 grep --colour=auto volume
croessner@desktop ~ $ ps aux | grep mixer
1000 5119 0.1 0.5 351472 21048 ? Sl 19:22 0:00 /usr/lib/gnome-applets/mixer_applet2 --oaf-activate-iid=OAFIID:GNOME_MixerApplet_Factory --oaf-ior-fd=38
1000 5429 0.0 0.0 7496 1004 pts/0 S+ 19:23 0:00 grep --colour=auto mixer

But as you can see, I only see _one_ mixer applet, although the newer version is in the process list.

[Chris Coulson (chrisccoulson)]

Can you delete the mixer applet from your panel, as you shouldn't need it with the gnome-volume-control-applet really. Is the new gnome-volume-control-applet not appearing in your notification area?

[Christian Roessner (christian-roessner-net)]

Ok, I removed the old mixer applet from the panel and logged out from gnome. pkill -u 1000 and login again. Now, I do not have any mixer symbols anymore. And xsession-errors has this:

** (gnome-volume-control-applet:7268): WARNING **: Connection failed
x-session-manager[7093]: WARNING: Application 'gnome-volume-control-applet.desktop' failed to register before timeout

[Christian Roessner (christian-roessner-net)]

Today I killed the PID and started this applet in a console:

gnome-volume-control-applet
** (gnome-volume-control-applet:5674): DEBUG: Updating client: index=0 name='ConsoleKit Session /org/freedesktop/ConsoleKit/Session1'
** (gnome-volume-control-applet:5674): DEBUG: Updating client: index=3 name='XSMP Session on gnome-session as 10a3a8a403a9aec49a123237114544246400000049570037'
** (gnome-volume-control-applet:5674): DEBUG: Updating client: index=4 name='EsounD client (UNIX socket client)'
** (gnome-volume-control-applet:5674): DEBUG: Updating client: index=5 name='GNOME Volume Control'
** (gnome-volume-control-applet:5674): DEBUG: Updating sink: index=0 name='alsa_output.pci_8086_293e_sound_card_0_alsa_playback_0' description='HDA Intel - AD198x Analog' map='front-left,front-right'
** (gnome-volume-control-applet:5674): DEBUG: Changing volume for sink: n=2 vol=59678
** (gnome-volume-control-applet:5674): DEBUG: Channel 0 v=59678
** (gnome-volume-control-applet:5674): DEBUG: Channel 1 v=59678
** (gnome-volume-control-applet:5674): DEBUG: Updating source: index=0 name='alsa_input.pci_1131_7134_sound_card_0_alsa_capture_0' description='SAA7134 - SAA7134 PCM'
** (gnome-volume-control-applet:5674): DEBUG: Updating source: index=1 name='alsa_output.pci_8086_293e_sound_card_0_alsa_playback_0.monitor' description='Monitor of HDA Intel - AD198x Analog'
** (gnome-volume-control-applet:5674): DEBUG: Updating source: index=2 name='alsa_input.pci_8086_293e_sound_card_0_alsa_capture_0' description='HDA Intel - AD198x Analog'
** (gnome-volume-control-applet:5674): DEBUG: Updating client: index=6 name='Native client (UNIX socket client)'
** (gnome-volume-control:5676): DEBUG: Updating client: index=0 name='ConsoleKit Session /org/freedesktop/ConsoleKit/Session1'
** (gnome-volume-control:5676): DEBUG: Updating client: index=3 name='XSMP Session on gnome-session as 10a3a8a403a9aec49a123237114544246400000049570037'
** (gnome-volume-control:5676): DEBUG: Updating client: index=4 name='EsounD client (UNIX socket client)'
** (gnome-volume-control:5676): DEBUG: Updating client: index=5 name='GNOME Volume Control'
** (gnome-volume-control:5676): DEBUG: Updating client: index=6 name='GNOME Volume Control'
** (gnome-volume-control:5676): DEBUG: Updating sink: index=0 name='alsa_output.pci_8086_293e_sound_card_0_alsa_playback_0' description='HDA Intel - AD198x Analog' map='front-left,front-right'
** (gnome-volume-control-applet:5674): DEBUG: Updating client: index=6 name='GNOME Volume Control'
** (gnome-volume-control:5676): DEBUG: Updating source: index=0 name='alsa_input.pci_1131_7134_sound_card_0_alsa_capture_0' description='SAA7134 - SAA7134 PCM'
** (gnome-volume-control:5676): DEBUG: Updating source: index=1 name='alsa_output.pci_8086_293e_sound_card_0_alsa_playback_0.monitor' description='Monitor of HDA Intel - AD198x Analog'
** (gnome-volume-control:5676): DEBUG: Updating source: index=2 name='alsa_input.pci_8086_293e_sound_card_0_alsa_capture_0' description='HDA Intel - AD198x Analog'
** (gnome-volume-control:5676): DEBUG: setting theme ubuntu
** (gnome-volume-control:5676): DEBUG: deleted the custom theme dir
** (gnome-volume-control:5676): DEBUG: Create mo...

[Chris Coulson (chrisccoulson)]

Christian - I think the applet not appearing when you log in is related to this bug: http://bugzilla.gnome.org/show_bug.cgi?id=568320

[Christian Roessner (christian-roessner-net)]

Indeed this bug report descibes my situation. I followed the authors idea of commenting out the specified line. I got the following in .xsession-errors:

** (gnome-volume-control-applet:5187): WARNING **: Connection failed
N: main.c: Called SUID root and real-time and/or high-priority scheduling was requested in the configuration. However, we lack the necessary privileges:
N: main.c: We are not in group 'pulse-rt', PolicyKit refuse to grant us the requested privileges and we have no increase RLIMIT_NICE/RLIMIT_RTPRIO resource limits.
N: main.c: For enabling real-time/high-priority scheduling please acquire the appropriate PolicyKit privileges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user.

So I decided to add the user to pulse-rt. If this is, what you want, then a fix is simple, else maybe PolicyKit needs changes, but I am quiet new to PolicyKit and have not used the manger too much, yet :-) After logging in again with new group settings, the mixer is doing fine. No more freezes. So the main bug report is closeable in my opinion.

Only thing that is left over is the digital output option in the output tab. Do you want me to open a new bug report on this topic? I guess so :-)

[Chris Coulson (chrisccoulson)]

The author of that report was me ;)

Anyway, I'll keep this report open for now for the mixer_applet issue, but it will get closed once the mixer_applet is no longer shipped (which I think is going to happen sometime during this cycle).

If you have any other issues with the gnome-volume-control-applet, it would be best for you to open separate bug reports for those.

[Christian Roessner (christian-roessner-net)]

Oh sorry :-) Did not really look for the author, just for the report.

But unfortunately I have to report this morning that the fix provided in the gnome bug tracker does not work each time. I do not know why, but this morning the applet was not displayed again. I killed it and restarted it. So I hope, the gnome devs already know about it and will fix it.

[Christian Roessner (christian-roessner-net)]

The fix done in gnome-volume-control-applet.desktop and as described in http://bugzilla.gnome.org/show_bug.cgi?id=568320 does _not_ fix the problem that the applet does not appear in the panel. Maybe my machine is too fast.

Do you think, there is an other option for X-GNOME-Autostart-Phase= which would handle this?

[Chris Coulson (chrisccoulson)]

There is another bug report for that (bug 319443)

[Christian Roessner (christian-roessner-net)]

Thanks a lot!! It´s working! :-)

[Sebastien Bacher (seb128)]

could you try if that's still an issue in current jaunty?

[Sebastien Bacher (seb128)]

The mixer has been rewritten in karmic