abrt detected a crash. Attached file: backtrace cmdline: /usr/bin/python -OO /usr/bin/gmixer -d component: gmixer executable: /usr/bin/gmixer kernel: 2.6.30.8-64.fc11.x86_64 package: gmixer-1.3-11.fc12 uuid: d8db10a4
Created attachment 374486 [details] File: backtrace
Closed as no one has provided additional info as requested. ( need info flag added over a month ago )
I never saw a need info flag on this bz nor any comment asking for anything, I can reproduce this at will, what info do you need?
I shouldn't have to ask for steps to reproduce a bug, this info should be provided as standard by the reporters.
Unable for reproduce anymore, my box updated Jan 20th so it looks liked it was fixed in gmixer-1.3-12.fc12.
This reproduces every time I log in on my F-13 system. Let me know what information you need to diagnose it.
Package: gmixer-1.3-15.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. All that I know was that I installed and rebooted into kernel 2.6.33.5-124.fc13.i686.
Package: gmixer-1.3-15.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Reboot system 2. 3. Comment ----- Noticed this was occuring on system startup. It's been happening for the last 3-4 startups at least (2 days or so). The only changes made recenly were VNC related. I've been settng vncserver to start automatically.
Package: gmixer-1.3-15.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Start LXDE in F13 as a kvm guest. 2. 3.
Package: gmixer-1.3-15.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Messing with TVtime 2. 3. Comment ----- Not sure what happened.
Package: gmixer-1.3-15.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Boot FC 13 2. Logon to Gnome desktop
Package: gmixer-1.3-15.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.boot the system 2. 3. Comment ----- it crashes as soon as gnome tries to load
Package: gmixer-1.3-15.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. started the jackd server... 2. 3.
Package: gmixer-1.3-15.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Maybe by booting a system without Soundcard installed (Mainboard ASUS CUV4X-DLS in my case) 2. it says it crashes right after login and desktop has loaded 3.
Package: gmixer-1.3-12.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Right-mouse click on the gmixer icon in the upper tray 2. From Devices menu option chose OSS Mixer 3. Comment ----- After re-installing gmixer package the crash happens now at boot time when the tray icons are initalized The gmixer icon doesn't show in the upper tray anymore, nor can it be launched from the Applications/Sound and Video/Mixers menu list
When launched from command line you get this message: ** (gmixer:2792): CRITICAL **: _wrap_gst_mixer_list_tracks: assertion `GST_IS_MIXER (self->obj)' failed Traceback (most recent call last): File "/usr/bin/gmixer", line 1168, in <module> GMixer(options.daemon, options.custom_mixer_cmd, options.pixmap) File "/usr/bin/gmixer", line 640, in __init__ self._build_gvolumes() File "/usr/bin/gmixer", line 1013, in _build_gvolumes sep.hide() UnboundLocalError: local variable 'sep' referenced before assignment
Package: gmixer-1.3-12.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. restart computer. Log in 2. 3.
Package: gmixer-1.3-15.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Booted system (Dell PowerEdge 2650) 2. 3. Comment ----- Received error upon boot completion (Dell PowerEdge 2650)
Package: gmixer-1.3-15.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted LXDE in a KVM 2. Crash message appeared 3.
Proposing this as blocker for F14 final and NTH for F14 Beta (in case we have to respin it). It should technically be a beta blocker according to the criteria as they stand, but I recommend we except it as it's a longstanding issue in gmixer for which we're unlikely to suddenly discover a fix, and it's not a *huge* crimp on the functionality of the spin. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
-- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Interestingly, although gmixer also crashed for me when running Beta RC3 off a USB stick, the gmixer installation on my (64-bit) desktop F14 installation works properly. The desktop was installed Aug 22, and is updated via updates-testing (last update about 4 hrs ago).
(In reply to comment #19) > Package: gmixer-1.3-15.fc14 > Architecture: x86_64 > OS Release: Fedora release 14 (Laughlin) > > > How to reproduce > ----- > 1. Booted LXDE in a KVM > 2. Crash message appeared > 3. Isn't the LXDE crash caused by slim? https://bugzilla.redhat.com/show_bug.cgi?id=552491 As for fixing gmixer, upstream hasn't responded to any bug reports ever :-( .
"Isn't the LXDE crash caused by slim?" LXDE spin uses LXDM, not slim. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** Bug 578235 has been marked as a duplicate of this bug. ***
I can't reproduce this bug, with just starting gmixer on the console. But when selecting /dev/mixer I get another bug: ** (gmixer:3832): CRITICAL **: _wrap_gst_mixer_list_tracks: assertion `GST_IS_MIXER (self->obj)' failed Traceback (most recent call last): File "/usr/bin/gmixer", line 939, in _change_device self._build_gvolumes() File "/usr/bin/gmixer", line 1013, in _build_gvolumes sep.hide() UnboundLocalError: local variable 'sep' referenced before assignment Not opening a new bug, because I don't use this extensiveley...
in the tested scenario (lxde live image) a gmixer process is actually still running even after you get the crash notification, but no gmixer applet appears in the tray. it seems like it's perhaps *part* of gmixer that's crashing, not the whole thing. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
(In reply to comment #26) > I can't reproduce this bug, with just starting gmixer on the console. > > But when selecting /dev/mixer I get another bug: > ** (gmixer:3832): CRITICAL **: _wrap_gst_mixer_list_tracks: assertion > `GST_IS_MIXER (self->obj)' failed > Traceback (most recent call last): > File "/usr/bin/gmixer", line 939, in _change_device > self._build_gvolumes() > File "/usr/bin/gmixer", line 1013, in _build_gvolumes > sep.hide() > UnboundLocalError: local variable 'sep' referenced before assignment That's #537803. I just tried to reproduce this with the current nightlies of lxde, but it didn't even start and all I saw was grub... Can anyone give me a pointer to a live cd, that has this issue?
The Beta. http://fedoraproject.org/get-prerelease and get the LXDE spin.
This was discussed at the 2010-10-01 blocker / NTH review meeting, and accepted as a nice-to-have.
(In reply to comment #32) > The Beta. > > http://fedoraproject.org/get-prerelease > > and get the LXDE spin. I get udev errors, and the spin doesn't even start here in qemu. Maybe I can reproduce it, when I upgrade my computer to F-14...
that's odd, it works fine here in a virt-manager VM, I tested it several times.
why not try writing it to a USB stick or CD and booting it on a real machine?
Package: gmixer-1.3-17.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Start pc 2. see abrt catch the backtrace
(In reply to comment #36) > why not try writing it to a USB stick or CD and booting it on a real machine? I didn't had the time to do so yet, but now it's reproducable on fc13 for me, so I'll have a look this week...
Package: gmixer-1.3-17.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.boot computer 2.log in 3.
Package: gmixer-1.3-17.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. I right clicked on the sound icon 2. I checked which device was being used 3. I closed the window
Package: gmixer-1.3-17.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.log in 2. 3.
Removing F14 NTH status as F14 is now out. Remaining open nice-to-have issues do NOT automatically become nice-to-have issues for Fedora 15. If you believe a Fedora 14 issue which was accepted as nice-to-have but not resolved in time for release should also qualify for nice-to-have status for Fedora 15, please re-propose it as nice-to-have for Fedora 15. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Package: gmixer-1.3-17.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Démarrage de la session, tout simplement 2. 3. Comment ----- Pas de son sur ma carte: Sound blaster Audigy 4 (SB0610)
Package: gmixer-1.3-17.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) Comment ----- Happens when I log into my desktop.
Package: gmixer-1.3-17.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Seems to have occurred after I adjusted one of the volume sliders.
Package: gmixer-1.3-17.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Dmarrage de la session, tout simplement 2. 3. Comment ----- Pas de son sur ma carte: Sound blaster Audigy 4 (SB0610)
Package: gmixer-1.3-17.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.install realtek-linux-audiopack-5.15 2.reboot system per instructions 3.
Package: gmixer-1.3-17.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. logged in 2. 3.
Package: gmixer-1.3-17.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.i dont now 2. 3.
Package: gmixer-1.3-17.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.everytime i login, this package crashes. 2. 3.
Package: gmixer-1.3-17.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. run gmixer 2. change device to "/dev/mixer (OSS Mixer)", which gives the following warning ** (gmixer:9624): CRITICAL **: _wrap_gst_mixer_list_tracks: assertion `GST_IS_MIXER (self->obj)' failed 3. quit gmixer 4. run gmixer -d
Created attachment 471655 [details] do not use mixer devices with empty track list The attached patch fixes the issue for me. Clemens --o<-- Subject: [PATCH] do not use mixer devices with empty track list According to the gstreamer documentation, list_tracks [1] can return an empty list, but gmixer tries to read it anyways and crashes. This patch works around the crash by not adding a mixer device with an empty track list in the first place. If an 'invalid' device was configured by an older version of gmixer, a different device will be selected automatically. This fixes: https://bugzilla.redhat.com/show_bug.cgi?id=542255 [1] http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-base-libs/html/gst-plugins-base-libs-gstmixer.html#gst-mixer-list-tracks
Package: gmixer-1.3-17.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Attempt to enable/disable front panel microphone in gmixer 2. 3.
Package: gmixer-1.3-17.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. The crash reported immediately after boot by the system. After that gmixer did not work.
Package: gmixer-1.3-17.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.run gmixer - cx18-0 alsa mixer 2. 3.
Package: gmixer-1.3-17.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. . 2. 3.
Well I noticed something usefull today. The crash I reported was mentioned by the system after boot because I had switched on (during boot) an EMU external midi keyboard. If this keyboard is off (during or after boot) there is no problem.
Package: gmixer-1.3-17.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Opened gmixer 2. In Devices menu option selected "/dev/mixer (OSS Mixer)" 3.
Package: gmixer-1.3-17.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Sorry - I'm not sure on all the details of how to reproduce this. It seems to be crashed when I bring up my system and log in. 2. 3.
Package: gmixer-1.3-17.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Booted up 2. 3.
Package: gmixer-1.3-17.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. I’ve clicked on ‘/dev/mixer (OSS Mixer)’ in the ‘Devices’ menu. 2. G-Mixer is still running (and working), but the ABRT dialog reported a crash.
Clemens' patch looks good: I did a build with it included and it hid a mixer which previously displayed this issue for me. I'll push a build with that patch included, please test.
gmixer-1.3-20.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/gmixer-1.3-20.fc15
gmixer-1.3-19.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/gmixer-1.3-19.fc14
gmixer-1.3-19.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gmixer'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/gmixer-1.3-19.fc14
Package: gmixer-1.3-17.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Login via vncviewer to remote (this F13 i386) machine 2. immediately after session start and desktop displays, I see gmixer crash
gmixer-1.3-19.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
(In reply to comment #70) > gmixer-1.3-19.fc14 has been pushed to the Fedora 14 stable repository. If > problems still persist, please make note of it in this bug report. Hi. I never had problems with gmixer-1.3-17.fc14, but ever since the update to gmixer-1.3-19.fc14 about 10 days ago, I encounter into several bugs: 1. *Every* time when I log in, every single time, when I click the Gmixer icon on the panel I get the report that gmixer has crashed and ABRT opens. Gmixer, however, keeps running and is accessible. 2. When I click on gmixer icon, the volume slider doesn't appear just below it anymore, but on the upper-left corner of the screen. 3. Clicking anywhere else on the screen while volume slider is opened doesn't shut it off, but only clicking on gmixer icon. During past 10 days, these same bugs were reported in the gmixer-1.3-19.fc14 thread. Those bugs never happened to me with gmixer-1.3-17.fc14. I downgraded gmixer package from 19 to 17 and everything works fine now. The only annoying thing is that notifications about available update to gmixer package keep appearing, while I don't want to upgrade it. Cheers.
all I did was apply clemens' patch. I did test it here and it seemed to work, but obviously it's not working for all. clemens, do you have any idea on this one? I un-CCed myself from the other bug since it's getting so many reports...
I can reproduce the bug. If I remove my patch the bug remains. As others have noted [1], this is likely due to the trayicon_transparency patch. [1] https://bugzilla.redhat.com/show_bug.cgi?id=678640#c37