In openSUSE 11.0, both VLC and Xine use either /media/sr0 or /dev/sr0 to address a dvd in the optical drive. The disk is automatically opened and run directly from the user’s home directory.
In both versions of 11.1 and 11.2, this will NOT occur. Both programs report that the device is unavailable…BUT, if you try this in root, then the device is instantly available and plays.
This strongly suggests a permission was broken in 11.1 and STILL has not been repaired.
PLEASE PLEASE FIX THIS TEAM…IT IS BEING REPORTED ON WEB BLOGS AND IF YOU SEARCH ON openSUSE and sr0, you will find examples quickly.
I applied ALL the download updates…It still behaves in EXACTLY the same way…and so does 11.2 at start up…In other words, the “fix”, whatever it is, has NOT been applied universally in 11.2…And I remain unconvinced it has been applllied in 11.1 either. Let’s face it, I know what I can or cannot do and after ALL updates are downloaded, installed and 11.1 is restarted because there is a kernel update, the problem with sr0 still remains…It needs a proper fix…
I agree, had to add myself to the pulse audio group for a difrent reason. And I dont know any other way because Im one of those users with no knowledge, i just have exp with suse
I have never filed a bug report simply because the bug was already around, known and being talked about during the release of 11.1
Frankly, I have no idea how to file a bug report and if anyone else on this page who is following this whole mess can do it, PLEASE DO IT AND QUICKLY.
Summa…sr0 just works in version 11. It does NOT in 11.1 and in the betas of 11.2 The workarounds suggested above are NOT what is required. This is a true bug that needs to be corrected at developer programming level simply because no user should be required to put in place a patch that should already be there and which prevents proper operation of the optical drive.
As an example of just how bad this problem is with sr0 permissions, here is another example:
I use Crossover Office. When installing Photoshop7, I use an upgrade and need to confirm I still own Photoshop4…so, in openSUSE 11, I take out the Photoshop7 disk, put in the Photoshop4 disk, it is detected, confirmed and taken out, Photoshop7 is put back in and away we go. But in both 11.1, and 11.2, the detection and reading of Photoshop4 cannot be completed under any circumstances and believe me I tried a variety of ways without actually moving into any code alterations. The permissions within sr0 are preventing this from happening and while I will try what has been suggested above, NO NORMAL USER SHOULD HAVE TO BE FORCED INTO THIS WHEN IT IS ALREADY PERFECTLY WORKING IN VERSION 11. The frustration of other users who are being told that the device does not exist when they know darn well that it does should have been well known to the openSUSE team by now surely…I mean this is ongoing now for about a year.
If I sound a bit frustrated and annoyed…yes I am. I really love this distribution, 11 is my present workspace. I wanted to upgrade to 11.1, but could not because of this sr0 problem…It now looks like I am facing the same blasted situation with 11.2…
Frankly, I have no idea how to file a bug report…
It’s through the good works of helpful, unselfish, collaborative folk like you that these bugs are fixed. So just pop along to the bug report page and click the button to file a bug report. Don’t be afraid. It’s within your capabilities I’m sure, because they’ve taken great care to make it utterly simple.
> Frankly, I have no idea how to file a bug report and if anyone else on
> this page who is following this whole mess can do it, PLEASE DO IT AND
> QUICKLY.
Have a look at Akoellh’s first reply to you in this thread - he points to
a good primer on entering bugs.
It’s generally best for the/a person experiencing the issue to report a
bug, rather than to go through an intermediary. If a developer has
questions or wants the reporter to try some things in order to further
diagnose the issue, going direct is the best way to ensure that they are
able to get their questions answered in a timely manner. Being dependent
on a middleman to pass information back and forth is very inefficient and
will certainly delay resolution of the problem.
Thanks Jim, I “fought” my way to reporting the bug and entered the bug area for 11.1, only to find that this particular item has turned up as critical and that it has been reported as such for perhaps 6 months with some blogs on the bugentry site getting really caustic about how such a dreadful bug in 11.1 has persisted. I absolutely KNOW the bug does not exist in 11.0,but it does still happen in my latest version of 11.1 with all patches applied, and it is still present in the beta of 11.2. I have not bothered to report again…the bug is known…and is still not fixed. Rather disheartening after what ? 8 months of a known bad problem. There are workarounds suggested like adding yourself to the cdrom group (and knowing me I have got that wrong, I will have to go back and print out the work around) but this is a critical bug, it is listed as such, it should NOT occur in 11.2 if it has been fixed in 11.1 and I can report that it DOES occur in 11.2. Sigh !!
I only found the bug while trying to use Xine and VLC, apparently from the bug reports, the bug is still there when you go to use K3b which I did not try and which would be an utter disaster. You can use K3b as root, but not as user.
I don’t think I can do any more…at least this matter is now raised at high levels.
> but this is a critical bug, it is listed as
> such, it should NOT occur in 11.2 if it has been fixed in 11.1 and I can
> report that it DOES occur in 11.2. Sigh !!
If you found an existing bug on it, add a comment to that bug at least
indicating that it is in 11.2, or if you’ve reported the bug in 11.2,
reference the other bug in the bug report.
When you say it’s now “raised at high levels”, what do you mean? We’re
not developers here (in general), so raising it to us here doesn’t get
the bug the visibility you seem to feel it needs. That needs to be done
in Bugzilla.
What I meant by “at high levels” is that the bug is already fully reported and commented on in bugzilla, which to me seemed to indicate that the bug was known about or at least reported at the levels of development knowledge …I guess I could add another comment since you think it is worth doing. The “critical” part refers to the actual rating it has been given in bugzilla which to me then makes the non-resolution of this bug even more astounding in that it has not been addressed/rectified as yet considering it has been known about for so long.
What has me interested is that there seems also to be some indication that the problem has been addressed or fixed, but I am uncertain of that interpretation. If that IS the case, then I guess it is even more important to get the bug report in again simply because it is STILL there.
My thanks for your help. This is the first time I have ever commented on a forum like this and it has been extremely useful and interesting.
> I guess I could add another comment since you think it is worth doing.
> The “critical” part refers to the actual rating it has been given in
> bugzilla which to me then makes the non-resolution of this bug even more
> astounding in that it has not been addressed/rectified as yet
> considering it has been known about for so long.
I haven’t looked at the bugs myself, but if the comment count is low the
assumption could be that it’s not affecting a lot of people, so the
priority has been set accordingly - if more people are affected by it,
those affected by it need to make sure that’s known (in the bug) so as to
raise the visibility and get the prioritization set at a level that
reflects appropriately.
> What has me interested is that there seems also to be some indication
> that the problem has been addressed or fixed, but I am uncertain of that
> interpretation. If that IS the case, then I guess it is even more
> important to get the bug report in again simply because it is STILL
> there.
Or to reopen the existing bug and indicate that it’s not fixed - whether
that’s because it’s reappeared as a regression or there’s a secondary
underlying cause that wasn’t part of the original fix.
> My thanks for your help. This is the first time I have ever commented
> on a forum like this and it has been extremely useful and interesting.
Glad to help out - I feel it’s important that users understand the
processes and systems that are in place to help ensure that things are
taken care of properly. I’m glad you’ve found this exchange useful and
interesting - and hope it has encouraged you to participate more.
Hello Jim…have just filed a full bug report on 11.2’s buglist and specified it as major. No problems…I also indicated clearly that the bug does not appear in 11.0, but does also occur in 11.1 with all patches applied. We now wait and see.
Thanks again for all your help and kind suggestions.
Tony
burning software and it cant find the phisical drive