Description of problem: A basic install of RHEL5 client beta 2 with the office productivity and developer set of software. The PC is a brand new Dell optiplex 745 with a core 2 duo processor with VT switched on in the bios (the rest of the bios settings are at their default values). As soon as I insert an (original pressed) audio CD, totem loads - it looks like it's trying to get CDDB data or something - it shows all the track numbers and looks like it's about to start playing the first track, but then the bottom few centimetres of the screen goes blank, then everything goes blank. The mouse pointer comes and goes a few times on the middle of the blank screen, but evenutally goes for ever and I have to do a hard reset of the PC. Version-Release number of selected component (if applicable): How reproducible: Every time. Steps to Reproduce: 1. Boot PC 2. Log in with standard user privs 3. Wait for login to finish. 4. Insert standard audio cd. Actual results: PC crashes. Expected results: Audio CD player software willl launch, download CDDB data and begin playing CD. Additional info: We do not have direct access to port 80 outside the campus, it must go through a web proxy cache. I've not configured this - I don't know if that is having any influence on the problem.
Totem doesn't check CDDB, or Musicbrainz anymore, so it must be something different. Could you please gather a backtrace of the crash following the instructions at http://fedoraproject.org/wiki/StackTraces
I couldn't reproduce the crash here on a beta2 system - totem started playing just fine. It didn't display song titles, though.
Created attachment 142456 [details] dmesg output for optiplex 745 The thing that I notice about the boot up process on this system is that it gets stuck on the ata3 and ata4 "probes" and eventually times out.
I've not acquired a backtrace of the crash (I can't work out how to do it based on the documentation in the wiki and I don't have time to delve into it at the moment). I did however try a new install on an identical, brand new Optiplex 745 and got exactly the same result. I created the attachment of the dmesg in case there is anything in there which is relevant.
Without a stack trace, we can't determine where the problem lies. As Matthias couldn't reproduce the problem on recent versions, I'll close this as obsolete. Please reopen if you can gather a backtrace (it should be automatic when Totem crashes, you'd get the bug report tool) with Beta 2 or newer.
When Totem crashes, the operating system crashes, so unless something is written to a file somewhere, any debug info will be gone.
The operating system crashes? Are you saying the kernel locks up? That sounds more like a hardware or a driver issue.
Does other cd player apps have the same issue? e.g. gnome-cd, or the kde cd player. Does cd ripping work (cdparanioa, sound-juicer)?
The problem occurs only if totem is automatically launched when the CD is inserted and the CD icon appears on the desktop. If I launch totem first, then insert the CD, an icon for the disc appears on the desktop, with the name "Audio Disc" and I get a popup saying Totem could not play 'cdda:///dev/scd0'. No URI handler implemented for "cdda". Totem then refuses to play the CD. The "Movie" menu has the following items: Open... Open Location... Play Disc 'Audio Disc' ----------- Eject ----------- 1. scd0 ----------- Play/Pause ----------- Quit However, "Play Disc 'Audio Disc'" is greyed out, and so is "Eject". If i select "1. scd0" or "Play/Pause, then I get the popup message again. I can't get Totem to play the CD. Once the disc is mounted on the desktop though, I can quit Totem and I can launch the CD Player from the "Sound & Video" menu and it will download track names from CDDB and play them without a hitch. I can also do the same using rythmbox, although it does not download track names. I can also extract the tracks using sound juicer, although like rythmbox, it doesn't download track names. Similarly, if I start cd-player before inserting the CD, when I insert it, CD player displays track names, and I can start playing the tracks. However, the moment I press the stop button on CD player, I see the CD icon on the desktop, and Totem launches, tries to play the CD then the system crashes.
What's the actual command that was launched? Please check in the output of "ps aux" which command was used to launch totem. I tried to reproduce the problem, and wasn't able to. Is the CD you're inserting a CD Extra, or one with a data track?
totem cdda:///dev/hdc doesn't work. CDDA used to be very special-cased in Totem, and I guess we need to bring this back. Oh, I wish for Rhythmbox was able to play Audio CDs from the CLI. Matthias, could you devel ack+ please?
As I inserted the CD, I kept a terminal window open and continually issued ps auxw | grep totem The line that showed up, just before the crash showed the command as totem /dev/scd0 The main CD I've been using is a plain pressed audio CD.
"totem /dev/scd0" works just fine in my tests. I've file http://bugzilla.gnome.org/show_bug.cgi?id=382955 to track the "totem cdda:///dev/hdc" doesn't work. n.lam, could you please try to gather a backtrace of the crash using gdb, by launching "totem /dev/scd0" by hand? As none of us can reproduce the crasher you're seeing, we won't be able to fix it without getting a backtrace of the crash.
Created attachment 143011 [details] capture of gdb session on totem /dev/scd0 Through the "Removable Drives and Media Preferences", I've unchecked the "Play audio CD discs when inserted" option, so I can now insert audio CDs without totem launching (if no other application is accessing the CD). The CD still gets mounted, and shows up on the desktop. From a terminal window I've initiated totem via gdb, then run it with /dev/scd0 as the argument. Unfortunately the script output didn't get written to file before the OS crashes, though I don't know if that output will be useful to anyone anyway. But if I can be provided with information on some other way of running totem so that I get a core dump or something that is recoverable after the crash, then I'll be able to send something to you. Let me know if any of you can give me any pointers on what to do.
Reassigning to the kernel, as it seems that the whole machine is crashing, Totem is just the trigger.
Yes the whole machine is crashing. X windows almost totally disappears. The only thing left is the mouse pointer with the little blue swirl around it, and this flashes on and off every 5 seconds or so - but the pattern is not regular. While in this state, the mouse pointer responds to mouse movement, but keyboard combinations like ctrl+alt+backspace or ctrl+alt+delete or ctrl+alt+F1 don't do anything. After some time, maybe a couple of minutes, this behaviour stops, and I'm left with a fully blank screen, and apparently no input being responded to, so I just reboot. I'm not sure if this has any relation to the extremely slow boot that I experience on these PCs. Please see the first dmesg attachment and let me know if you think it needs to be reported as a separate bug - basically it needs to go trhough two 30 second timeouts during boot up.
Are we able to reproduce this on any other systems? Without more details, I can't QE ack.
Bastian, when changing component, you should reassign to the component owner. Otherwise, the bug falls off everyones radar.
The SATA timeouts are a different problem and are not causing this issue, we are working on resolving the slow boot time for R5 GA. John - We need to reproduce this problem in house as I am not sure what state the system is left in without a backtrace. No Dev ACK until I get a backtrace to review.
Dell Optiplex systems are not certified on RHEL. Dell support will need to be contacted with any problems. Closing this issue out as NOTABUG.