A problem in burning cd's in Ubuntu 8.10, brasero and k3b both produce almost the same error.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Brasero |
Invalid
|
Undecided
|
Unassigned | ||
k3b |
Invalid
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
I'm facing a problem when burning a cd in Ubuntu 8.10, I tried both Brasero and K3B, and both fail the same way.
In Brasero, when I tried to burn an .iso image to a cd, it fails with an error that says something like: "Burning failed probably due to overburning the cd.", and when I try to copy a cd, it also fails and gives me an error that says: "Burning failed because the drive is busy".
=======
Affects: Ubuntu Jaunty 9.10
Relevant information:
BraseroWodim stderr: wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/sr0'
BraseroWodim called brasero_
BraseroWodim stderr: devname: '/dev/sr0'
and in the second log file:
BraseroWodim stderr: wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/sr0'
I have Googled around and it appears to be to do with user groups and not being allowed to access the drive correctly unless sudo is used:
Omar S. Hafez (omar-the-pythoner) wrote : | #1 |
- This is a log from k3b, after a failed attempt to burn the Ubunu 8.10 .iso image. Edit (6.0 KiB, text/plain)
Omar S. Hafez (omar-the-pythoner) wrote : | #2 |
- This is the output from Brasero after a failed attempt to burn an .iso image. Edit (60.9 KiB, text/plain)
Changed in brasero: | |
status: | New → Confirmed |
status: | Confirmed → New |
xteejx (xteejx) wrote : | #3 |
Changed in brasero: | |
status: | New → Invalid |
Changed in k3b: | |
status: | New → Invalid |
Omar S. Hafez (omar-the-pythoner) wrote : | #4 |
- Output from the command: uname -a Edit (84 bytes, text/plain)
Thank you for your assistance sir.
Here is the information you've requested.
Omar S. Hafez (omar-the-pythoner) wrote : | #5 |
Omar S. Hafez (omar-the-pythoner) wrote : | #6 |
Omar S. Hafez (omar-the-pythoner) wrote : | #7 |
But like I told you before, sir.
Both programs (K3B and Brasero) have the same problem.
I'm not very sure if it's the same error, or bug, but they both exit with an error during the burning process.
Could be a problem in my CD drive? Also maybe, I'm not sure.
Thanks again sir.
Omar S. Hafez (omar-the-pythoner) wrote : | #8 |
Is there anymore stuff I have to add?
xteejx (xteejx) wrote : | #9 |
Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!
Omar S. Hafez (omar-the-pythoner) wrote : | #10 |
Well, since Ubuntu is my passion, then it's more of a duty to me, to participate in making Ubuntu the most wonderful, reliable and comfortable OS ever! ;-)
david38840 (dridleypto) wrote : | #11 |
I too am having the same problems with both Brasero and K3b. I have been using some cds that I can print on and can't get anywhere with them. I then tried burning to a rewritable cd and no problem. I asked a friend to let me have one of his cd's just to check my batch of 100 aren't the cause and I was told an overburn problem. All my music is mp3.
Good luck and hope there is a solution.
david38840 (dridleypto) wrote : | #12 |
This is my bug report for this problem if anyone is kind enough to be able to help sort out a solutio
104MB of mp3 music to burn to cd..... I am told - no permissions - also overburning!!!!
System
-------
K3b Version: 1.0.5
KDE Version: 3.5.10
QT Version: 3.3.8b
Kernel: 2.6.27-7-generic
Devices
-------
HL-DT-ST DVD-RAM GSA-H54N 1.00 (/dev/scd0, ) [CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL] [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump]
K3bIsoImager
-------
mkisofs print size result: 53284 (109125632 bytes)
Pipe throughput: 13012736 bytes read, 13008384 bytes written.
Used versions
-------
mkisofs: 1.1.8
cdrecord: 1.1.8
cdrecord
-------
/usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/scd0'
devname: '/dev/scd0'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.8
SCSI buffer size: 64512
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
TOC Type: 3 = CD-ROM XA mode 2
Driveropts: 'burnfree'
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'HL-DT-ST'
Identification : 'DVD-RAM GSA-H54N'
Revision : '1.00'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0009 (CD-R)
Profile: 0x0012 (DVD-RAM)
Profile: 0x002B (DVD+R/DL)
Profile: 0x001B (DVD+R)
Profile: 0x001A (DVD+RW)
Profile: 0x0016 (DVD-R/DL layer jump recording)
Profile: 0x0015 (DVD-R/DL sequential recording)
Profile: 0x0014 (DVD-RW sequential recording)
Profile: 0x0013 (DVD-RW restricted overwrite)
Profile: 0x0011 (DVD-R sequential recording)
Profile: 0x0010 (DVD-ROM)
Profile: 0x000A (CD-RW)
Profile: 0x0009 (CD-R) (current)
Profile: 0x0008 (CD-ROM)
Profile: 0x0002 (Removable disk)
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Drive buf size : 1114112 = 1088 KB
Drive DMA Speed: 104051 kB/s 591x CD 75x DVD
FIFO size : 12582912 = 12288 KB
Speed set to 8468 KB/s
Track 01: data 104 MB
Total size: 119 MB (11:50.48) = 53286 sectors
Lout start: 119 MB (11:52/36) = 53286 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 5
Is not unrestricted
Is not erasable
Disk sub type: Medium Type B, low Beta category (B-) (4)
ATIP start of lead in: -11607 (97:27/18)
ATIP start of lead out: 359849 (79:59/74)
Disk type: Short strategy type (Phthalocyanine or similar)
Manuf. index: 18
Manufacturer: Plasmon Data systems Ltd.
Blocks total: 359849 Blocks current: 359849 Blocks remaining: 306563
Starting to write CD/DVD at speed 48.0 in dummy TAO mode for multi session.
Last chance to quit, starting dummy write in 2 second...
David Harmon (dmh-phoenix) wrote : | #13 |
- Uname-a output Edit (82 bytes, text/plain)
I am having a similar problem. I am attaching the requested information, including brasero and k3b logs for trying to burn an Ubuntu 8.10 CD.
Here is my uname-a output
David Harmon (dmh-phoenix) wrote : | #14 |
David Harmon (dmh-phoenix) wrote : | #15 |
David Harmon (dmh-phoenix) wrote : | #16 |
David Harmon (dmh-phoenix) wrote : | #17 |
David Harmon (dmh-phoenix) wrote : | #18 |
Here is the console output from the CD-burning runs, for both programs:
###############
(nautilus-
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Launch helper exited with unknown return code 0
** (nautilus-
(brasero:15254): GLib-GObject-
(brasero:15254): GLib-GObject-
(brasero:15254): GLib-GObject-
(brasero:15254): GLib-GObject-
dmh@destiny:~$ cd Bugreport/
dmh@destiny:
brasero.log brasero-session.log dmesg.out lspci-vvnn.log uname-a.out
dmh@destiny:
System
-------
K3b Version: 1.0.5
KDE Version: 3.5.10
QT Version: 3.3.8b
Kernel: 2.6.27-11-generic
Devices
-------
PHILIPS SPD6004P HP03 (/dev/scd0, ) [CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW
, DVD-R DL, DVD+R, DVD+RW, DVD+R DL] [DVD-ROM, DVD-R Sequential, DVD-R Dual Laye
r Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-R
W Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, R
AW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer
Jump]
Used versions
-------
cdrecord: 1.1.8
cdrecord
-------
/usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK li
dmh@destiny:
dmh@destiny:
#############
I am having similar problems with burning DVD's -- brasero fails early with "cannot lock drive", but
K3B proceeds through the write, then fails on the verify, so it'll take me a little more time to get the logs for that. It's worth noting that DVD burns *occasionally* succeed, but not often. This problem has been progressive since I upgraded to 8.10
David Harmon (dmh-phoenix) wrote : | #19 |
David Harmon (dmh-phoenix) wrote : | #20 |
David Harmon (dmh-phoenix) wrote : | #21 |
Still happening in 9.04, with current updates
David Harmon (dmh-phoenix) wrote : | #22 |
Also, this seems to be the same bug described at http://
Omar S. Hafez (omar-the-pythoner) wrote : Re: [Bug 294480] Re: A problem in burning cd's in Ubuntu 8.10, brasero and k3b both produce almost the same error. | #23 |
@ David
Yeah, that's right, I'm still suffering from it.
I just wonder what exactly is the problem... ?
Could it be a kernel problem?
david38840 (dridleypto) wrote : Re: [Bug 294480] Re: A problem in burning cd's in Ubuntu 8.10, brasero and k3b both produce almost the same error. | #24 |
Hi Omar,
Sorry, but I gave up burning for the moment. I haven't got anywhere with
the problem. I will try again burning with Brasero and see it has
solutionned itself and let you know O.K.?
No idea if its a kernel problem, this is beyond me!
Thks and regards,
David
Omar S. Hafez wrote:
> @ David
>
> Yeah, that's right, I'm still suffering from it.
> I just wonder what exactly is the problem... ?
>
> Could it be a kernel problem?
>
>
David Harmon (dmh-phoenix) wrote : | #25 |
OK, *my* instance turns out to be probably an *&$(#^ hardware problem --
I rolled back to 8.04, and found the DVD-writer didn't work -- but a new
DVD-writer that I just brought in (USB external, HP) did! The older
drive, as it turns out, can read commercial CDs/DVDs and home-burned
CDs, but not home-burned DVDs. Oy vey, but I'm bowing out of this one.
Dave Harmon
xteejx (xteejx) wrote : | #26 |
Marking this as Medium importance - moderate impact on core application.
Also anyone with Jaunty having this problem, can you please run
apport-collect -p linux-image-`uname -r` 294480
Thanks.
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
Mark Logue (mark-logue-bigfoot) wrote : apport-collect data | #27 |
Architecture: amd64
DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=
Lsusb:
Bus 001 Device 002: ID 0c45:62c0 Microdia Pavilion Webcam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Hewlett-Packard HP Pavilion dv2000 (RV323UA#ABA)
NonfreeKernelMo
Package: linux-image-
PackageArchitec
ProcCmdLine: root=UUID=
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersionSign
Uname: Linux 2.6.28-14-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video
Mark Logue (mark-logue-bigfoot) wrote : | #28 |
Mark Logue (mark-logue-bigfoot) wrote : | #29 |
Mark Logue (mark-logue-bigfoot) wrote : | #30 |
Mark Logue (mark-logue-bigfoot) wrote : | #31 |
Mark Logue (mark-logue-bigfoot) wrote : | #32 |
Mark Logue (mark-logue-bigfoot) wrote : | #33 |
Mark Logue (mark-logue-bigfoot) wrote : | #34 |
Mark Logue (mark-logue-bigfoot) wrote : | #35 |
david38840 (dridleypto) wrote : Re: [Bug 294480] Re: A problem in burning cd's in Ubuntu 8.10, brasero and k3b both produce almost the same error. | #36 |
Mark Logue wrote:
> ** Attachment added: "ProcModules.txt"
> http://
>
>
Mark many thanks for your email. Unfortunately I can't understand
anything? I am not a computer expert that's why. Is there a solution to
my problem?
Many thanks once again.
David
david38840 (dridleypto) wrote : | #37 |
I had this problem some time ago and never solutionned it. I went to Linux Mint 6 and the problem was the same. I am now running Linux Mint 7 and still having the same problems. I burned an mp3 music disc on a TDK cd and it said failed, error etc., When I tried the disc it was perfect and no problems. On another cheaper type of disc I always have problems and it just won't burn the disc. I am attaching the log if it is of any help as I think this is quite a regular problem for many people.
Checking session consistency (brasero_
BraseroBurnURI called brasero_
BraseroBurnURI called brasero_
BraseroBurnURI called brasero_
BraseroBurnURI stopping
BraseroBurnURI called brasero_
BraseroBurnURI called brasero_
BraseroBurnURI called brasero_
BraseroBurnURI called brasero_
BraseroBurnURI called brasero_
BraseroBurnURI no burn:// URI found
BraseroBurnURI stopping
BraseroLocalTrack called brasero_
BraseroLocalTrack called brasero_
BraseroLocalTrack called brasero_
BraseroLocalTrack stopping
BraseroLocalTrack called brasero_
BraseroLocalTrack called brasero_
BraseroLocalTrack called brasero_
BraseroLocalTrack called brasero_
BraseroLocalTrack called brasero_
BraseroLocalTrack no remote URIs
BraseroLocalTrack stopping
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroChecksum
BraseroWodim called brasero_
BraseroWodim creating input
BraseroWodim getting varg
BraseroWodim called brasero_
xteejx (xteejx) wrote : | #38 |
The issue that you reported is one that should be reproducible with the development release - Karmic Koala. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://
Changed in linux (Ubuntu): | |
status: | Confirmed → Incomplete |
david38840 (dridleypto) wrote : Re: [Bug 294480] Re: A problem in burning cd's in Ubuntu 8.10, brasero and k3b both produce almost the same error. | #39 |
Hi,
Sorry but I dont really understand, perhaps because I am not an expert.
I am running Linux Mint 7 and just wonder if I can and where to start
with Ubuntu???
I certainly dont mind helping if I possibly can.
Thanks,
David
Teej wrote:
> The issue that you reported is one that should be reproducible with the
> development release - Karmic Koala. It would help us greatly if you
> could test with it so we can work on getting it fixed in the next
> release of Ubuntu. You can find out more about the development release
> at http://
> help.
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
>
xteejx (xteejx) wrote : | #40 |
I'm guessing that this is probably a hardware/medium fault, but because of the workflow process it needs to be tested in the development release of Ubuntu, which is Karmic, and that is now in beta, and released in about 2-3 weeks, so if you could test this problem on there that would be great. You can use the Live Desktop CD to do this to save installing it, assuming you have 2 CD drives, putting the Live CD in the one that isn't causing problems, and burning with the other. You can download the latest daily build at http://
Also is this just happening with one type of media, or is it across all DVD/CD types?
david38840 (dridleypto) wrote : | #41 |
Thanks Teej,
I only have one CD drive!!!!
The problem happens when trying to burn music and films to CD or DVD on
my printable discs. If I use a rewritable disc there is no problem.
I did try using a reputable TDK cd and burnt mp3 music and it said it
failed. However the disc was perfect!!!
Strange one isn't it?
Teej wrote:
> I'm guessing that this is probably a hardware/medium fault, but because of the workflow process it needs to be tested in the development release of Ubuntu, which is Karmic, and that is now in beta, and released in about 2-3 weeks, so if you could test this problem on there that would be great. You can use the Live Desktop CD to do this to save installing it, assuming you have 2 CD drives, putting the Live CD in the one that isn't causing problems, and burning with the other. You can download the latest daily build at http://
> Also is this just happening with one type of media, or is it across all DVD/CD types?
>
>
xteejx (xteejx) wrote : | #42 |
Is is certainly a strange one, I'm not too sure if it's to do with the kernel though, I mena it may well be, but it could be something else, I'll contact the rest of the BugSquad and see what their take is on this :)
xteejx (xteejx) wrote : | #43 |
Are you able to tell us
1) exactly where it fails, does it burn ok and then fail to verify, or something else, and also
2) how big are the files you are trying to burn, have you tried files other than mp3's, perhaps different filenames, filetypes, etc
Thank you.
david38840 (dridleypto) wrote : | #44 |
Teej this is very kind of you to take so much interest.
When I am burning my white printable cd's with mp3 music as a data disc
(I haven't tried audio as I don't use it) using Brasero it doesn't even
write to disc. I am attaching the log with the error as an attachment so
I hope you can open it.
This the one marked Brasero-session1.
With the regards to recording on a burn with a normal TDK cd it burned
ok, but told me it failed. This is the log marked Brasero-session2
If you need anymore information please let me know. As I said before on
a Grundig RW disc I am having no problems at all.
Many many thanks and hope you can get to the bottom of it with the log
report.
Teej wrote:
> Are you able to tell us
> 1) exactly where it fails, does it burn ok and then fail to verify, or something else, and also
> 2) how big are the files you are trying to burn, have you tried files other than mp3's, perhaps different filenames, filetypes, etc
> Thank you.
>
>
david38840 (dridleypto) wrote : | #45 |
- brasero-session1 error white printable cds.log Edit (15.6 KiB, text/x-log; name="brasero-session1 error white printable cds.log")
- brasero-session2 error normal TDK cd .log Edit (390.0 KiB, text/x-log; name="brasero-session2 error normal TDK cd .log")
Sorry Teej I forgot to add the attachments. Here they are:
david ridley wrote:
> Thanks Teej,
> I only have one CD drive!!!!
> The problem happens when trying to burn music and films to CD or DVD
> on my printable discs. If I use a rewritable disc there is no problem.
> I did try using a reputable TDK cd and burnt mp3 music and it said it
> failed. However the disc was perfect!!!
> Strange one isn't it?
>
>
> Teej wrote:
>> I'm guessing that this is probably a hardware/medium fault, but
>> because of the workflow process it needs to be tested in the
>> development release of Ubuntu, which is Karmic, and that is now in
>> beta, and released in about 2-3 weeks, so if you could test this
>> problem on there that would be great. You can use the Live Desktop CD
>> to do this to save installing it, assuming you have 2 CD drives,
>> putting the Live CD in the one that isn't causing problems, and
>> burning with the other. You can download the latest daily build at
>> http://
>> Also is this just happening with one type of media, or is it across
>> all DVD/CD types?
>>
>>
xteejx (xteejx) wrote : | #46 |
Not sure if it's relevant but in the first brasero log with printable CD we get:
BraseroWodim stderr: Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
possibly from the earlier
BraseroWodim stderr: wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/sr0'
BraseroWodim called brasero_
BraseroWodim stderr: devname: '/dev/sr0'
and in the second log file:
BraseroWodim stderr: wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/sr0'
I have Googled around and it appears to be to do with user groups and not being allowed to access the drive correctly unless sudo is used:
http://
I believe there is enough information here for a developer to begin working on it, therefore I am marking this Triaged and will let them handle it from here. Thank you for reporting this and helping to make Ubuntu better, and the best of luck :)
description: | updated |
Changed in linux (Ubuntu): | |
status: | Incomplete → Triaged |
david38840 (dridleypto) wrote : | #47 |
Thanks very much Teej,
I wait anxiously to see if any of the developers can find a solution.
I'm sure this will keep their brains happy for a while!!!
A trick one!
Meanwhile do you think I could try burning using the terminal? If so
what command would I use?
I don't mind at all giving it a try to see if this works.
Kind regards to all the team.
You are doing an excellent job and for this Linux is so good.
Teej wrote:
> Not sure if it's relevant but in the first brasero log with printable CD
> we get:
>
> BraseroWodim stderr: Errno: 5 (Input/output error), write_g1 scsi
> sendcmd: no error
>
> possibly from the earlier
>
> BraseroWodim stderr: wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/sr0'
> BraseroWodim called brasero_
> BraseroWodim stderr: devname: '/dev/sr0'
>
> and in the second log file:
>
> BraseroWodim stderr: wodim: Operation not permitted. Warning: Cannot
> raise RLIMIT_MEMLOCK limits.scsidev: '/dev/sr0'
>
> I have Googled around and it appears to be to do with user groups and
> not being allowed to access the drive correctly unless sudo is used:
>
> http://
>
> I believe there is enough information here for a developer to begin
> working on it, therefore I am marking this Triaged and will let them
> handle it from here. Thank you for reporting this and helping to make
> Ubuntu better, and the best of luck :)
>
> ** Description changed:
>
> I'm facing a problem when burning a cd in Ubuntu 8.10, I tried both
> Brasero and K3B, and both fail the same way.
>
> In Brasero, when I tried to burn an .iso image to a cd, it fails with an
> error that says something like: "Burning failed probably due to
> overburning the cd.", and when I try to copy a cd, it also fails and
> gives me an error that says: "Burning failed because the drive is busy".
> +
> + =======
> +
> + Affects: Ubuntu Jaunty 9.10
> +
> + Relevant information:
> +
> + BraseroWodim stderr: wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/sr0'
> + BraseroWodim called brasero_
> + BraseroWodim stderr: devname: '/dev/sr0'
> +
> + and in the second log file:
> +
> + BraseroWodim stderr: wodim: Operation not permitted. Warning: Cannot
> + raise RLIMIT_MEMLOCK limits.scsidev: '/dev/sr0'
> +
> + I have Googled around and it appears to be to do with user groups and
> + not being allowed to access the drive correctly unless sudo is used:
> +
> + http://
>
> ** Changed in: linux (Ubuntu)
> Status: Incomplete => Triaged
>
>
xteejx (xteejx) wrote : | #48 |
The only thing I can think of would be to go around it and use cdrecord, but that's beyond my knowledge to be honest, but you're very welcome, and I'm glad to have been able to help you :)
david38840 (dridleypto) wrote : | #49 |
Thanks Teej. I will wait and see if the other part of the team can come
up with some solution.
I have checked out cdrecord and see lots of legal problems and all sorts
of bugs and missing forks so will leave this for the moment.
Teej wrote:
> The only thing I can think of would be to go around it and use cdrecord,
> but that's beyond my knowledge to be honest, but you're very welcome,
> and I'm glad to have been able to help you :)
>
>
elias (elias-uxmcc2) wrote : | #50 |
I have the same problem.
Take my comment as a very speculative hypothesis.
In a notebook with intel core2duo 2GHz+2GB ram+ Intel 945GM chipset, with ubuntu 8.10 i386 (32bit)
The dvd/cd/writer is (lshw):
*-cdrom
bus info: scsi@1:0.0.0
Two computers in my university have a different processor Intel Pentium D 3.4GHz and Intel chipset, one has ubuntu 8.10 i386 the other ubuntu 9.10 i386, have the same problem.
I can burn DVD images in an external usb drive attached to the core2duo computer, but some times fail.
I suspect that the problem may reside in a program used in a low layer not necessarily the kernel, if a firmware is used in the process it may be the problem.
Does linux send a firmware to the burner?
May the model be not well identified and failing because the firmware is not adequate?
What test can I do to get the information needed to check this problem?
I can do the test in the core2duo and one of the Pentium D.
geneqew (geneqew-gmail) wrote : | #51 |
Same problem here but i was able to burn one copy by running brasero as sudo ...
case:
unable to burn iso image file on regular cd but i am able to burn to dvd. if brasero is used to burn iso i always get the error:
Please replace the disc with a supported CD or DVD
it is not possible to write with the current set of plugins
i tried it with k3b and gnomebaker but i was not able to burn on that same disk...
so i tried googling this case and ended up in articles regarding goups.. i checked my user group and it is included in the cdrom group(which i think is responsible for cd/dvd related tasks) so i tried to run brasero as a sudoer and i was able to burn the iso...
is there a way to burn image files without running brasero as sudo?
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix". | #52 |
This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.
Changed in linux (Ubuntu): | |
status: | Triaged → Won't Fix |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.
Note: It is highly unlikely that both programs have the same bug, this may be a kernel problem:
Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https:/ /wiki.ubuntu. com/KernelTeamB ugPolicies
Thanks in advance!