From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Description of problem: Sound-juicer starts up but then nothing works. The menu entries seem to have no functionality. Version-Release number of selected component (if applicable): sound-juicer-2.13.1-2 How reproducible: Always Steps to Reproduce: 1. start sound-juicer Actual Results: menu entries are threre but no one has any functionality Expected Results: the menu entries should perform their task Additional info: When starting in a console a lot of similar lines appear like the following: .... (sound-juicer:3148): libglade-WARNING **: could not find signal handler 'prefs_e dit_profile_clicked'. (sound-juicer:3148): libglade-WARNING **: could not find signal handler 'on_sele ct_all_activate'. (sound-juicer:3148): libglade-WARNING **: could not find signal handler 'on_edit _preferences_cb'. (sound-juicer:3148): libglade-WARNING **: could not find signal handler 'on_seek _press'. ** (sound-juicer:3148): WARNING **: No HAL devices found for UDI '/org/freedeskt op/Hal/devices/storage_serial_2492203262' ** (sound-juicer:3148): WARNING **: Error getting media type -------------- The following packages regarding libglade are installed: libglade2-2.5.1-3 pygtk2-libglade-2.8.2-2
These bugs are being closed since a large number of updates have been released after the FC5 test1 and test2 releases. Kindly update your system by running yum update as root user or try out the third and final test version of FC5 being released in a short while and verify if the bugs are still present on the system .Reopen or file new bug reports as appropriate after confirming the presence of this issue. Thanks
Can you still reproduce this? I certainly can't on FC5. The "Error getting media type" is a pretty "normal" error that you get when, e.g., there's no CD in the drive. The libglade "could not find signal handler" warnings look more serious, like there's something wrong with your installation. I really can't reproduce this at all, whether on FC5test2, FC5test3, or the final version.
No, I can't reproduce this. It seems to work now.
Great! Closing bug.