[opensuse] Leap not recognizing blank dvds or cds
I was going to burn an iso image, and apparently the last time I did it was when I still had 13.2 (that was to burn the iso dvd for installing leap). So this time, while running 42.1, I put in a new blank dvd, and nothing. It won't read. Leap doesn't see anything in the drive. So I tried to put in a blank cd, and it still doesn't see anything. So I put in a cd that has data on it, and no problem, it reads just fine. So I booted into 13.2, and put in the same blank dvd to check, and no problem. In 13.2, the system reads that there is a blank dvd in the drive. Any ideas? Here are some of the technical details: # dmesg | grep dvd [ 2.379159] sr 4:0:0:0: [sr0] scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray # wodim --devices wodim: Overview of accessible drives (1 found) : ------------------------------------------------------------------------- 0 dev='/dev/sg4' rwrw-- : 'ATAPI' 'iHAS124 B' ------------------------------------------------------------------------- -- George Box: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB Laptop #2: 42.1 | KDE Plasma 5 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-07-02 02:45, tech@reachthetribes.org wrote:
# wodim --devices wodim: Overview of accessible drives (1 found) : ------------------------------------------------------------------------- 0 dev='/dev/sg4' rwrw-- : 'ATAPI' 'iHAS124 B' -------------------------------------------------------------------------
Uninstall wodim and install cdrecord instead. That for starters. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 07/02/2016 05:55 PM, Carlos E. R. wrote:
On 2016-07-02 02:45, tech@reachthetribes.org wrote:
# wodim --devices wodim: Overview of accessible drives (1 found) : ------------------------------------------------------------------------- 0 dev='/dev/sg4' rwrw-- : 'ATAPI' 'iHAS124 B' -------------------------------------------------------------------------
Uninstall wodim and install cdrecord instead. That for starters.
Ok, I can do that before I actually burn anything. For now, though, I did a little more experimenting. 3 different CD/DVD read/write drives on 2 different computers - my laptop #1 and my desktop. 2 of the drives are installed, and one is external. On opensuse LEAP 42.1, in all 3 cases of different drives, the device notifier will not pop up or recognize that a blank cd or dvd is in the drive and ready to be burned. However, in opensuse 13.2, in all 3 drives, the exact same blank cd and dvd did pop up in the device notifier saying that there is a blank in the drive and ready to be burned. It worked here. Also in all 3 drives, a data dvd, cd, or dvd movie (or anything that had any kind of data on it) pops up in the device notifier and works, both in 13.2 and in Leap. Has anyone else out there popped in a blank dvd or cd in your computer while running Leap, and it doesn't read it? -- George Box: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB Laptop #2: 42.1 | KDE Plasma 5 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
tech@reachthetribes.org composed on 2016-07-02 22:33 (UTC+0800):
Has anyone else out there popped in a blank dvd or cd in your computer while running Leap, and it doesn't read it?
Using what environment? Every openSUSE release offers multiple choices. Are you using IceWM? Enlightenment? LXDE? Xfce? Cinnamon? Mate? Other? e.g., I open KDE3's K3B, find the iso I want to burn, stick a blank in, and K3B burns it. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/02/2016 11:03 PM, Felix Miata wrote:
tech@reachthetribes.org composed on 2016-07-02 22:33 (UTC+0800):
Has anyone else out there popped in a blank dvd or cd in your computer while running Leap, and it doesn't read it?
Using what environment? Every openSUSE release offers multiple choices. Are you using IceWM? Enlightenment? LXDE? Xfce? Cinnamon? Mate? Other?
e.g., I open KDE3's K3B, find the iso I want to burn, stick a blank in, and K3B burns it.
I have tried it in both KDE and Gnome on Leap. I only tried it in KDE in 13.2. Same results. -- George Box: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB Laptop #2: 42.1 | KDE Plasma 5 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-07-02 16:33, tech@reachthetribes.org wrote:
However, in opensuse 13.2, in all 3 drives, the exact same blank cd and dvd did pop up in the device notifier saying that there is a blank in the drive and ready to be burned. It worked here.
Ah, you are waiting for a popup to happen. Why not simply start the burner, and see what it says about the blank? It would be then a different kind of problem. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 07/03/2016 01:16 AM, Carlos E. R. wrote:
On 2016-07-02 16:33, tech@reachthetribes.org wrote:
However, in opensuse 13.2, in all 3 drives, the exact same blank cd and dvd did pop up in the device notifier saying that there is a blank in the drive and ready to be burned. It worked here.
Ah, you are waiting for a popup to happen. Why not simply start the burner, and see what it says about the blank?
It would be then a different kind of problem.
Ok, I put the blank dvd in the drive in kde while running 42.1. No read on the drive as far as the popup is concerned. Running fdisk -l doesn't give anything either. So I started K3B, and nothing pops up. So in K3B I went to the device menu and clicked "Media Info", and here are the results: Type: DVD-R Sequential Media ID: CMC MAG. AM3 Capacity: 510:38:38 min (4.4 GiB) Rewritable: no Appendable: no Empty: yes Layers: 1 Sessions: 0 Supported writing speeds: 6.0x (8310 KB/s) 8.0x (11080 KB/s) 12.0x (16620 KB/s) 16.0x (22160 KB/s) I know the blank dvd is not damaged, because one that I was just using did the same thing yesterday, but I really needed to burn something. So I booted into 13.2 and burned the dvd that I needed, then booted back into 42.1. Even though it says it is not rewritable, I know that it is because it will say the opposite if I load it up in 13.2 Given that I am seeing the exact same effects on 2 different computers with completely different hardware, I am thinking that somebody out there has to have already experienced the same thing. But there aren't even any bugs that I could find on bugzilla for this same problem. How often do people burn cds and dvds nowadays anyways? -- George Box: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB Laptop #2: 42.1 | KDE Plasma 5 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
03.07.2016 11:38, tech@reachthetribes.org пишет:
On 07/03/2016 01:16 AM, Carlos E. R. wrote:
On 2016-07-02 16:33, tech@reachthetribes.org wrote:
However, in opensuse 13.2, in all 3 drives, the exact same blank cd and dvd did pop up in the device notifier saying that there is a blank in the drive and ready to be burned. It worked here.
Ah, you are waiting for a popup to happen. Why not simply start the burner, and see what it says about the blank?
It would be then a different kind of problem.
Ok, I put the blank dvd in the drive in kde while running 42.1. No read on the drive as far as the popup is concerned. Running fdisk -l doesn't give anything either.
What do you expect fdisk to show you about blank disk?
So I started K3B, and nothing pops up. So in K3B I went to the device menu and clicked "Media Info", and here are the results:
Type: DVD-R Sequential ...
I know the blank dvd is not damaged, because one that I was just using did the same thing yesterday, but I really needed to burn something. So I booted into 13.2 and burned the dvd that I needed, then booted back into 42.1. Even though it says it is not rewritable, I know that it is because it will say the opposite if I load it up in 13.2
DVD-R is not rewritable. Can you actually write anything?
Given that I am seeing the exact same effects on 2 different computers with completely different hardware, I am thinking that somebody out there has to have already experienced the same thing. But there aren't even any bugs that I could find on bugzilla for this same problem. How often do people burn cds and dvds nowadays anyways?
Increasing number of notebooks do not even have DVD drive anymore. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-07-03 10:38, tech@reachthetribes.org wrote:
On 07/03/2016 01:16 AM, Carlos E. R. wrote:
Suggestion: Tell your mail program (Thunderbird?) what your name is. Or how do you want to be called, so that it writes the From as: Somebody <mail@someplace.com> That way, the first line above will be changed to something like: "On 2016-07-03 10:38, somebody wrote:" Advantages? We know how to address you, your address is not written that often to the web archive for spammers to collect...
Ah, you are waiting for a popup to happen. Why not simply start the burner, and see what it says about the blank?
It would be then a different kind of problem.
Ok, I put the blank dvd in the drive in kde while running 42.1. No read on the drive as far as the popup is concerned. Running fdisk -l doesn't give anything either.
It never will. It is not formatted, it is blank. Totally blank.
So I started K3B, and nothing pops up.
Correct.
So in K3B I went to the device menu and clicked "Media Info", and here are the results:
Type: DVD-R Sequential Media ID: CMC MAG. AM3 Capacity: 510:38:38 min (4.4 GiB) Rewritable: no Appendable: no Empty: yes Layers: 1 Sessions: 0 Supported writing speeds: 6.0x (8310 KB/s) 8.0x (11080 KB/s) 12.0x (16620 KB/s) 16.0x (22160 KB/s)
Well, it is correct. You can write to it, it is empty. Why didn't you try to burn to it?
I know the blank dvd is not damaged, because one that I was just using did the same thing yesterday, but I really needed to burn something. So I booted into 13.2 and burned the dvd that I needed, then booted back into 42.1. Even though it says it is not rewritable, I know that it is because it will say the opposite if I load it up in 13.2
A DVD-R is NOT re-writeable. It is writeable. There is a difference.
Given that I am seeing the exact same effects on 2 different computers with completely different hardware, I am thinking that somebody out there has to have already experienced the same thing. But there aren't even any bugs that I could find on bugzilla for this same problem. How often do people burn cds and dvds nowadays anyways?
I see no bug. Only that you do not get a popup. Have you yet replaced wodim with cdrecord tools, as suggested? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 07/03/2016 08:10 PM, Carlos E. R. wrote:
On 2016-07-03 10:38, tech@reachthetribes.org wrote:
On 07/03/2016 01:16 AM, Carlos E. R. wrote:
Suggestion:
Tell your mail program (Thunderbird?) what your name is. Or how do you want to be called, so that it writes the From as:
Somebody <mail@someplace.com>
That way, the first line above will be changed to something like:
"On 2016-07-03 10:38, somebody wrote:"
Advantages? We know how to address you, your address is not written that often to the web archive for spammers to collect...
Ok, thanks, I changed it to "George from the tribe..."
Ah, you are waiting for a popup to happen. Why not simply start the burner, and see what it says about the blank?
You know, sometimes the simplest suggestions solve problems. I tried it and it worked! Great! I guess I assumed that because there was no popup, and bringing up k3b didn't automatically look at the blank disc in the drive, it wasn't going to work. I feel slightly foolish on that, but glad to have it solved.
It would be then a different kind of problem.
Ok, I put the blank dvd in the drive in kde while running 42.1. No read on the drive as far as the popup is concerned. Running fdisk -l doesn't give anything either.
It never will. It is not formatted, it is blank. Totally blank.
So I started K3B, and nothing pops up.
Correct.
So in K3B I went to the device menu and clicked "Media Info", and here are the results:
Type: DVD-R Sequential Media ID: CMC MAG. AM3 Capacity: 510:38:38 min (4.4 GiB) Rewritable: no Appendable: no Empty: yes Layers: 1 Sessions: 0 Supported writing speeds: 6.0x (8310 KB/s) 8.0x (11080 KB/s) 12.0x (16620 KB/s) 16.0x (22160 KB/s)
Well, it is correct. You can write to it, it is empty. Why didn't you try to burn to it?
Wish I had tried that before! Glad you suggested it.
I know the blank dvd is not damaged, because one that I was just using did the same thing yesterday, but I really needed to burn something. So I booted into 13.2 and burned the dvd that I needed, then booted back into 42.1. Even though it says it is not rewritable, I know that it is because it will say the opposite if I load it up in 13.2
A DVD-R is NOT re-writeable. It is writeable. There is a difference.
Given that I am seeing the exact same effects on 2 different computers with completely different hardware, I am thinking that somebody out there has to have already experienced the same thing. But there aren't even any bugs that I could find on bugzilla for this same problem. How often do people burn cds and dvds nowadays anyways?
I see no bug. Only that you do not get a popup.
Have you yet replaced wodim with cdrecord tools, as suggested?
I uninstalled wodim, and zypper forced it to also uninstall k3b. So then I installed cdrecord, and then I had to reinstall k3b. But it worked. One kind of quirky thing with k3b is that it says it cannot burn mp3s to audio disc now as the mp3 libraries (called libmad) is missing. I didn't try to troubleshoot this at the moment, except to do a zypper search for libmad, and I found that my system does have libmad0 installed. That should do it for k3b I assume, but it apparently isn't detecting it. For another day. Thank you to all that helped.
-- George Box: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB Laptop #2: 42.1 | KDE Plasma 5 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-07-03 15:27, George from the tribe wrote:
On 07/03/2016 08:10 PM, Carlos E. R. wrote:
On 2016-07-03 10:38, tech@reachthetribes.org wrote:
On 07/03/2016 01:16 AM, Carlos E. R. wrote:
...
Advantages? We know how to address you, your address is not written that often to the web archive for spammers to collect...
Ok, thanks, I changed it to "George from the tribe..."
:-))
Ah, you are waiting for a popup to happen. Why not simply start the burner, and see what it says about the blank?
You know, sometimes the simplest suggestions solve problems. I tried it and it worked! Great! I guess I assumed that because there was no popup, and bringing up k3b didn't automatically look at the blank disc in the drive, it wasn't going to work. I feel slightly foolish on that, but glad to have it solved.
Good! :-)
I see no bug. Only that you do not get a popup.
You could now investigate why you do not get a popup. I don't, but I think I disabled the feature. 13.1 here, and XFCE.
Have you yet replaced wodim with cdrecord tools, as suggested?
I uninstalled wodim, and zypper forced it to also uninstall k3b. So then I installed cdrecord, and then I had to reinstall k3b. But it worked.
Ah, zypper. That's why I prefer YaST, it tells what it is going to do and suggests alternatives.
One kind of quirky thing with k3b is that it says it cannot burn mp3s to audio disc now as the mp3 libraries (called libmad) is missing. I didn't try to troubleshoot this at the moment, except to do a zypper search for libmad, and I found that my system does have libmad0 installed. That should do it for k3b I assume, but it apparently isn't detecting it.
You probably got k3b from the OSS repo, you need the one from packman to get that feature.
For another day.
It is a simple one, I think. :-)
Thank you to all that helped.
Welcome! -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Hello, On Sun, 03 Jul 2016, Carlos E. R. wrote:
On 2016-07-03 15:27, George from the tribe wrote:
On 07/03/2016 08:10 PM, Carlos E. R. wrote: [..]
Have you yet replaced wodim with cdrecord tools, as suggested?
I uninstalled wodim, and zypper forced it to also uninstall k3b. So then I installed cdrecord, and then I had to reinstall k3b. But it worked.
Ah, zypper. That's why I prefer YaST, it tells what it is going to do and suggests alternatives.
JFTR: From the "cdrkit/wodim" changes file: ==== Wed Jul 8 10:56:17 UTC 2015 - dmueller@suse.com - disable source download service, upstream download location is dead ==== http://cdrkit.org/ comes up empty. cdrkit started as a broken fork of cdrecord/cdtools and is dead and rotten. See https://en.wikipedia.org/wiki/Cdrkit ==== Stable release 1.1.11 / October 17, 2010; 5 years ago Development status Unmaintained ==== So, get the original cdrecord/cdrtools. I think cdrkit/wodim should be purged from the distros (well, except Debian, they created the fork). HTH, -dnh -- printk("Churning and Burning -"); linux-2.6.6/drivers/char/lcd.c -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 03/07/2016 20:41, David Haller a écrit :
So, get the original cdrecord/cdrtools.
I think cdrkit/wodim should be purged from the distros (well, except Debian, they created the fork).
I support this very goo idea jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/07/2016 20:41, David Haller wrote:
Hello,
On Sun, 03 Jul 2016, Carlos E. R. wrote:
On 2016-07-03 15:27, George from the tribe wrote:
On 07/03/2016 08:10 PM, Carlos E. R. wrote: [..]
Have you yet replaced wodim with cdrecord tools, as suggested? I uninstalled wodim, and zypper forced it to also uninstall k3b. So then I installed cdrecord, and then I had to reinstall k3b. But it worked. Ah, zypper. That's why I prefer YaST, it tells what it is going to do and suggests alternatives. JFTR: From the "cdrkit/wodim" changes file:
==== Wed Jul 8 10:56:17 UTC 2015 - dmueller@suse.com
- disable source download service, upstream download location is dead ====
http://cdrkit.org/ comes up empty. cdrkit started as a broken fork of cdrecord/cdtools and is dead and rotten.
See https://en.wikipedia.org/wiki/Cdrkit
==== Stable release 1.1.11 / October 17, 2010; 5 years ago Development status Unmaintained ====
So, get the original cdrecord/cdrtools.
I think cdrkit/wodim should be purged from the distros (well, except Debian, they created the fork).
HTH, -dnh
Wodim gets installed by default because of a kiwi dependency. I tried to get patterns-openSUSE changed but cannot until kiwi no longer has the dependency. Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-07-04 11:44, Dave Plater wrote:
Wodim gets installed by default because of a kiwi dependency. I tried to get patterns-openSUSE changed but cannot until kiwi no longer has the dependency.
But Kiwi is not installed by default, is it? :-? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 04/07/2016 12:05, Carlos E. R. wrote:
On 2016-07-04 11:44, Dave Plater wrote:
Wodim gets installed by default because of a kiwi dependency. I tried to get patterns-openSUSE changed but cannot until kiwi no longer has the dependency. But Kiwi is not installed by default, is it? :-?
No it isn't but that was the reason for not accepting my updated patterns-openSUSE. Something to do with kiwi being used to create the installation media. I've opened a bug at http://github.com/openSUSE/kiwi, will see if I can speed things up, looking at the change log an attempt to revert to cdrtools was made last year but it was reverted. This is a list of what still uses wodim. I think I've cleaned up Packman.
osc whatdependson openSUSE:Factory wodim standard x86_64 wodim : bundle-lang-gnome bundle-lang-kde goobox gthumb gtkpod kiwi kiwi-config-openSUSE libguestfs pix rhythmbox sound-juicer When I've got time I'll convert the rest to cdrtools. Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-07-04 14:53, Dave Plater wrote:
On 04/07/2016 12:05, Carlos E. R. wrote:
On 2016-07-04 11:44, Dave Plater wrote:
Wodim gets installed by default because of a kiwi dependency. I tried to get patterns-openSUSE changed but cannot until kiwi no longer has the dependency. But Kiwi is not installed by default, is it? :-?
osc whatdependson openSUSE:Factory wodim standard x86_64 wodim : bundle-lang-gnome bundle-lang-kde goobox gthumb gtkpod kiwi kiwi-config-openSUSE
No it isn't but that was the reason for not accepting my updated patterns-openSUSE. Something to do with kiwi being used to create the installation media. I've opened a bug at http://github.com/openSUSE/kiwi, will see if I can speed things up, looking at the change log an attempt to revert to cdrtools was made last year but it was reverted. This is a list of what still uses wodim. I think I've cleaned up Packman. libguestfs pix rhythmbox sound-juicer When I've got time I'll convert the rest to cdrtools.
Ah, thanks for the headsup. I don't mind having to change things locally on my machine, but it is very nice to know the reason of things :-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Le 04/07/2016 18:33, Carlos E. R. a écrit :
Ah, thanks for the headsup. I don't mind having to change things locally on my machine, but it is very nice to know the reason of things :-)
it's pretty simple to install cdrecord from OBS and this removes wodim (but of course it would be better to have it as default) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/07/2016 15:27, George from the tribe wrote:
I uninstalled wodim, and zypper forced it to also uninstall k3b. So then I installed cdrecord, and then I had to reinstall k3b. But it worked. You should have simply installed cdrtools and wodim would have been removed, k3b would have remained in place. Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/07/2016 16:33, tech@reachthetribes.org wrote:
On 07/02/2016 05:55 PM, Carlos E. R. wrote:
On 2016-07-02 02:45, tech@reachthetribes.org wrote:
# wodim --devices wodim: Overview of accessible drives (1 found) : -------------------------------------------------------------------------
0 dev='/dev/sg4' rwrw-- : 'ATAPI' 'iHAS124 B' -------------------------------------------------------------------------
Uninstall wodim and install cdrecord instead. That for starters.
Ok, I can do that before I actually burn anything.
For now, though, I did a little more experimenting.
3 different CD/DVD read/write drives on 2 different computers - my laptop #1 and my desktop. 2 of the drives are installed, and one is external.
On opensuse LEAP 42.1, in all 3 cases of different drives, the device notifier will not pop up or recognize that a blank cd or dvd is in the drive and ready to be burned.
However, in opensuse 13.2, in all 3 drives, the exact same blank cd and dvd did pop up in the device notifier saying that there is a blank in the drive and ready to be burned. It worked here.
Also in all 3 drives, a data dvd, cd, or dvd movie (or anything that had any kind of data on it) pops up in the device notifier and works, both in 13.2 and in Leap.
Has anyone else out there popped in a blank dvd or cd in your computer while running Leap, and it doesn't read it?
I'm using Leap and when I insert a blank dvd no device notification happens but if I open k3b I have no problem writing to it. I accidentally deleted a source file with weeks of work on it last night so I had to use my 13.2 rescue cd to recover it and when I inserted a blank dvd a pop up came up but I couldn't do anthing until I installed brasero so what's the use of a pop up anyway. I managed to find the source file on the disk and restore it though. Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/01/2016 08:45 PM, tech@reachthetribes.org wrote:
I was going to burn an iso image, and apparently the last time I did it was when I still had 13.2 (that was to burn the iso dvd for installing leap). So this time, while running 42.1, I put in a new blank dvd, and nothing. It won't read. Leap doesn't see anything in the drive.
So I tried to put in a blank cd, and it still doesn't see anything.
Logical. Nothing there to read.
So I put in a cd that has data on it, and no problem, it reads just fine.
Logical. Something to read.
So I booted into 13.2, and put in the same blank dvd to check, and no problem. In 13.2, the system reads that there is a blank dvd in the drive.
You'll have to give a lot more context. The Desktop environment or the programs you are using matters. For example: I run KDE. It doesn’t matter if its KDE3 or KDE4 AFAIK it should matter with KDE5. KDE has a "device notifier". if its loaded it tells you when a dynamic storage device becomes available because of the rules in udev producing kernel events. I don't know of other Desktops have a Device Notifier like that. The issue gets back to udev rules, then. I have my rsyslog set up to watch for such kernel events and I can see by using 'tail -f /var/log/messages' if a USB stick is inserted or a DVD is inserted. I get different messages both at the Device Notifier and in the messages according to whether the device has a file system or is blank. If you don't have a Device Notifier in to Desktop thyen you won't see a desktop level notification of this event. ** If you don't have an appropriate entry in your udev rules than there won't be any processing of the event interrupt, no mounting of file system or notification of blank media. ** -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/03/2016 07:53 PM, Anton Aylward wrote:
On 07/01/2016 08:45 PM, tech@reachthetribes.org wrote:
I was going to burn an iso image, and apparently the last time I did it was when I still had 13.2 (that was to burn the iso dvd for installing leap). So this time, while running 42.1, I put in a new blank dvd, and nothing. It won't read. Leap doesn't see anything in the drive.
So I tried to put in a blank cd, and it still doesn't see anything.
Logical. Nothing there to read.
So I put in a cd that has data on it, and no problem, it reads just fine.
Logical. Something to read.
So I booted into 13.2, and put in the same blank dvd to check, and no problem. In 13.2, the system reads that there is a blank dvd in the drive.
You'll have to give a lot more context. The Desktop environment or the programs you are using matters.
For example:
I run KDE. It doesn’t matter if its KDE3 or KDE4 AFAIK it should matter with KDE5.
KDE has a "device notifier". if its loaded it tells you when a dynamic storage device becomes available because of the rules in udev producing kernel events.
I don't know of other Desktops have a Device Notifier like that.
The issue gets back to udev rules, then.
I have my rsyslog set up to watch for such kernel events and I can see by using 'tail -f /var/log/messages' if a USB stick is inserted or a DVD is inserted. I get different messages both at the Device Notifier and in the messages according to whether the device has a file system or is blank.
If you don't have a Device Notifier in to Desktop thyen you won't see a desktop level notification of this event.
** If you don't have an appropriate entry in your udev rules than there won't be any processing of the event interrupt, no mounting of file system or notification of blank media. **
Ok, thanks. I will definitely have to look into that.
-- George Box: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB Laptop #2: 42.1 | KDE Plasma 5 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (9)
-
Andrei Borzenkov -
Anton Aylward -
Carlos E. R. -
Dave Plater -
David Haller -
Felix Miata -
George from the tribe -
jdd -
tech＠reachthetribes.org