By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 2522

Summary:	KsCD causes massive hang after setting CD-ROM device
Product:	TDE	Reporter:	Kristopher <gamrat.kristopher>
Component:	tdemultimedia	Assignee:	Timothy Pearson <kb9vqf>
Status:	NEEDINFO ---
Severity:	normal	CC:	bugwatch, gamrat.kristopher, kb9vqf, michele.calgaro
Priority:	P5
Version:	R14.0.x [Trinity]
Hardware:	Other
OS:	Linux
Compiler Version:		TDE Version String:
Application Version:		Application Name:

Description Kristopher 2015-09-05 21:30:33 CDT

Upon launching KsCD, I get a dialog box saying it can't read my CD-ROM device and asking me to check the device permissions. Once I get in to KsCD, I open the settings and change the CD-ROM drive from the default /dev/cdrom to my systems actual CD-ROM drive (in case it matters, it's /dev/sr0 and my user is in the cdrom group that owns it). Immediately upon clicking Apply, the system locks up so tightly that the arrow won't move, and I can't switch to a VT. The only option I have is to hit the power button and wait for the system to shut down -- there is no visual or audio queue that it's shutting down, other than the flashing hard disk light. Upon logging back in, if I try to launch KsCD, I get the same lock up before KsCD even appears.

There is no mention of KsCD in my ~/.xsession-errors file after the crash (I did copy it from a VT before logging back in). The only way to get KsCD back is to delete ~/.trinity/share/config/kscdrc , but it again displays the device permissions error, and changing it back once again produces the lock up.

I am able to set the correct device and play CDs under Amarok, so I can confirm that the CD-ROM drive is not the issue.

Comment 1 Timothy Pearson 2015-09-05 23:36:16 CDT

Any chance you could log in to the locked up machine via ssh and see what is actually happening (e.g. look at dmesg)?  The fact that the entire X11 session has locked up indicates something is going wrong at a much deeper level that TDE itself, although it is quite possible KsCD is triggering a system-level bug somehow.

Comment 2 Kristopher 2015-09-06 08:11:07 CDT

(In reply to Timothy Pearson from comment #1)
> Any chance you could log in to the locked up machine via ssh and see what is
> actually happening (e.g. look at dmesg)?  The fact that the entire X11
> session has locked up indicates something is going wrong at a much deeper
> level that TDE itself, although it is quite possible KsCD is triggering a
> system-level bug somehow.

I don't have another machine I can ssh from, so that's a no-go on checking remotely. Also, Xorg.log.old does not mention a crash.

Comment 3 Michele Calgaro 2015-09-06 09:39:45 CDT

> and I can't switch to a VT
Almost sounds like a kernel bug to me.
Have you tried to kill the X server (Ctrl+Alt+Backspace)?

Comment 4 Kristopher 2015-09-06 12:11:58 CDT

(In reply to Michele Calgaro from comment #3)
> > and I can't switch to a VT
> Almost sounds like a kernel bug to me.
> Have you tried to kill the X server (Ctrl+Alt+Backspace)?

That has not worked for me in years, even when Xorg isn't complete frozen, nor does it work during the KsCD lockup.

I did make a discovery when I was trying that: If I launch KsCD *after* already playing a CD in Amarok, KsCD launches normally and is able to play the CD. If I close KsCD, eject the CD, then launch KsCD again, I will then get the lock-up described in the initial bug report. In other words, the lockup seems to occur if KsCD is the cause of the initial scan of the disc, but does *not* occur if the disc has already been scanned by another application (even if that other application is a TDE app like Amarok).

Comment 5 Michele Calgaro 2015-09-07 10:16:39 CDT

> In other words, the lockup seems to occur if KsCD is the cause of the initial
> scan of the disc,
Which is what leaves me perplexed. If a program hangs, it should not take down the whole system, you should at least be able to switch to a VT.
When this cannot be done, usually it is the symptoms of something bigger.
Does the "Raising Elephants Is So Utterly Boring" work when the system hangs?

Comment 6 Kristopher 2015-09-07 16:05:19 CDT

(In reply to Michele Calgaro from comment #5)
<snip>
> Does the "Raising Elephants Is So Utterly Boring" work when the system hangs?

I'm not sure what you mean by that...?

Comment 7 Michele Calgaro 2015-09-11 08:46:12 CDT

>> Does the "Raising Elephants Is So Utterly Boring" work when the system hangs?
> I'm not sure what you mean by that...?
It's a sequence of keys that you can press to safely shutdown your system when it freezes, unless you have hit a major kernel bug.
See here
http://unix.stackexchange.com/questions/31818/what-to-do-when-a-linux-desktop-freezes  (the second answer)
or here
https://en.wikipedia.org/wiki/Magic_SysRq_key

Comment 8 Michele Calgaro 2018-08-03 22:33:17 CDT

Is this still valid?