** Package changed: cdrkit (Ubuntu) => brasero (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/149076
Title:
I can't write a cd
To manage notifications about this bug go to:
https://bugs.lau
You may add the cdrtools repo mentioned in the first comment by issuing the
following command:
sudo add-apt-repository ppa:brandonsnider/cdrtools
be warned, saucy packages are still missing. so this won't work on Ubuntu Saucy
13.10
I manually added
deb http://ppa.launchpad.net/brandonsnider/cd
Same problem in Ubuntu 13.10, Brasero works ok
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/149076
Title:
I can't write a cd
To manage notifications about this bug go to:
https://bugs.launchpad.ne
Workaround to solve / pass this bug:
- Go to Preferences / Congiure K3B / Advanced
- Enable "Show advanced GUI elements"
- Accept
- Open the burn dialog
- At right, there is a "Writing app" selector
- Choose "growisofs"
- Burn it!
The next time this selector will be in "auto", but it will use th
Uh... This seems to be interrelated to how Ubuntu chose to automount
the CD/DVD device. Problem occurs in more than just k3b/wodim.
AcetoneISO doesn't work right. Other burning programs don't seem to
work right. PSXE can't see legitimate PSX discs with this problem.
Didn't occur with initial ro
Kubuntu 12.04 KDE 4.8.4
3.2.0-26-generic-pae #41-Ubuntu SMP Thu Jun 14 16:45:14 UTC 2012 i686 i686 i386
GNU/Linux
ii k3b 2.0.2-3ubuntu4
Sophisticated CD/DVD burning application
ii k3b-data2.0.2-3ubu
Sorry, and my system is 12.04 Beta 2...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/149076
Title:
I can't write a cd
To manage notifications about this bug go to:
https://bugs.launchpad.net/pywod
** Attachment added: "After setting suid bit"
https://bugs.launchpad.net/ubuntu/+source/cdrkit/+bug/149076/+attachment/3045099/+files/bad3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/149076
Titl
Hi!
Wodim broke +-20 DVDs for me. Sorry, but this is a crapware.
I have set the suid bit on it, but this did not help. Please see attached devug
outputs.
** Attachment added: "bad"
https://bugs.launchpad.net/ubuntu/+source/cdrkit/+bug/149076/+attachment/3045098/+files/bad
--
You received
4 years and this is not solved, it's a shame i have to install
imgburn on wine to burn an iso.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/149076
Title:
I can't write a cd
To manage notificat
** Summary changed:
- [SOLVED] I can't write a cd
+ I can't write a cd
** Package changed: k3b (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to k3b in Ubuntu.
https://bugs.launchpad.net/bugs/149076
Title:
I can't write
Hello again,
Sorry the previous log was incorrect (i have canceled the burn process).
The one I always get is :
Devices
---
HL-DT-ST DVD-RW GCA-4080N 0G34 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R,
DVD-RW, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-RW Restr
Hello,
I have the same problem on Ubuntu 10.10. I have tried K3B, GnomeBaker
and Brasero without any success. I get the following debug output from
K3B. Could you please help me ? Thanks :
Devices
---
HL-DT-ST DVD-RW GCA-4080N 0G34 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-
I can confirm the bug in Lucid Linx using Brasero, K3B and cdrecord from
CL (without -raw96r). Two days ago had been released Maverik Meerkat
and this bug is since 2007 with no fix. I understand (according to
Schily) that this is all about "a defective fork called "wodim" " and
hope that this not
You are not using cdrecord but a defective fork called "wodim".
wodim is a dead fork from a 5 year old version of cdrecord with
bugs added that never have been in the original.
The device or resource busy message is a result from such a bug.
Note that you also do not use mkisofs but "genisoimage
I installed the cdrecord from for lucid and I still can't continue a
multisession cd.
K3b failed writing multisession project - kubuntu 10.04 with kde 4.4.3
Writing DVD-R in incremental mode
Using wodim 1.1.10
Unmounting medium
Starting incremental sequential writing at 16x speed
cdrecord has no
I use dao and still cannot burn a CD. I can burn DVD without problem.
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to k3b in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-b...@lists.u
It seems that cdrecord from
https://launchpad.net/~brandonsnider/+archive/cdrtools/+packages works
better than wodim with DVD-DL disks. Thanks to Schily.
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Kubuntu
Bugs, which
Same error here. My output:
Devices
---
PBDS DS-8A1P CF12 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R
dwuwarstwowa, DVD+R, DVD+RW, DVD+R dwuwarstwowa) [DVD-ROM, DVD-R sekwencyjna,
DVD-R dwuwarstwowa sekwencyjna, DVD+R dwuwarstwowa, DVD-RAM, DVD-RW w trybie
I've registered some failures in writing dvd dl after setting the ulimit "max
locked memory" so probably this limit is not the reason of failures.
So I'l try Schily's advice, and may be :
"This problem is caused by the fact that I am not using the real cdrecord"
10x
--
I can't write a cd
https
This problem is caused by the fact that you are not using the real cdrecord
but a defective fork.
In special, there is absolutely no support for DVD Dual layer media in
the fork.
Get the real program:
ftp://ftp.berlios.de/pub/cdrecord/alpha/
http://cdrecord.berlios.de
or as a ubuntu package
I've corrupted 2 disks with output:
"--
K3b Version: 1.90.0
KDE Version: 4.3.4 (KDE 4.3.4)
QT Version: 4.5.3
Kernel: 2.6.32-4-686
Used versions
---
mkisofs: 1.1.10
cdrecord: 1.1.10
cdrecord
---
/usr/bin/wodim: Operation not permit
At least in some cases, I suspect the errors might reflect an actual hardware
problem (e.g. comment 19 from cosmix had a similar error to the one I
encountered). I had a "samsung SH-S223" SATA DVD writer (showed up as "TSSTcorp
CDDVDW SH-S223F SB00" in wodim), and it could read all media fine, b
Devices
---
PBDS DS-8A1P CF12 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R
dwuwarstwowa, DVD+R, DVD+RW, DVD+R dwuwarstwowa) [DVD-ROM, DVD-R sekwencyjna,
DVD-R dwuwarstwowa sekwencyjna, DVD+R dwuwarstwowa, DVD-RAM, DVD-RW w trybie
ograniczonego zastępowania, D
If you have problems writing CDs that are a result of a missbehaving hald, it
usually
helps to use "cdrecord -v -raw96r ..."
If you write in raw mode, even the drive does not know what's happening and the
wrong algorithm in hald does not get the trigger that is otherwise usually
missinterprete
I've been using Kubuntu Hardy 8.04 on this laptop for about two years
now. I never had any trouble burning CDs with K3b until recently. Sure
enough, not using "auto" mode fixes the problem.
Why did this suddenly start happening? There must have been a
regression in one of the upgrades somewhere
After trying #41 and #38 (thanks) and cdrskin I realised that I need to
add the current user to the group:
disk:x:6:username
in
/etc/group
hope this helps someone.
Kelvin
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of
One more thing I choose ISO9960 when burning an image or iso.
Just quit using any AUTO settings and the discs will burn ok. Kerry
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
I use MEPIS Linux. It is debian based. A lot like kubuntu but I like
MEPIS better than any other system. Been using MEPIS since 2004. I like
KDE.
Recently I had troubles with K3b completing burns, getting the same
errors as everyone else. I thought it was possibly a 'lemon' Lg
burner... although
i have got same problem. ican't write cdrom with k3b and asus drw2014s1t
and ubuntu 8.04.
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to k3b in ubuntu.
--
kubuntu-bugs mailing list
Thank you for verifying that hald still is a major problem.
You could reduce the problems that appearh while writing by opening the
devices with O_EXCL but this does not fix all problems with hald and please
note that cdrecord calls libscg for the SCSI command transport. The same library
is used
@Schily
using cdrecord with -raw96r works for me, it seems as if you have diagnosed the
problem correctly
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
Did you conduct your tests with the same brand of CD-R while writing to
them under different permission/ownership? If you google for "MATSHITA"
and "verbatim" then you get many results about burning failures in
windows and mac os too.
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
Y
Thank you, Schily. That's excellent advice.
This might not be the proper place to discuss this, but I'd thought that
Karmic dropped hald for a lot of things. From the technical overview
(http://www.ubuntu.com/testing/karmic/beta#hal%20deprecation)
hal deprecation
Ubuntu 9.10 Beta's underlying te
If the owner/permissionms change while writing, this may be a hint
that the problem is caused by the well known non-cooperative behavior
from "hald" that interrupts the write process on Linux. Hald implements
in incorrect method for detecting a media change on Linux and in turn
tries to read from
I thought it relevant to point out that after the first burn, the
permissions of the drive used (in this case, /dev/sr1) changed without
any deliberate command from me.
Prior to burning:
ragna...@stirling:~$ ls -l /dev/sr*
brw-rw-rw-+ 1 ragnarok cdrom 11, 0 2009-10-13 10:49 /dev/sr0
brw-rw-rw-+ 1
I moved to Karmic beta. Run I type "k3b" into the KDE run dialog
(alt+F2), there are two options: "k3b" and "k3bsetup". I ran the setup
and it asked for authentication to set up the correct permissions on all
my optical drives. Essentially, the only change it made was move
everything to user and cd
Some notes to the report that has been made with the original cdrecord.
While the OP did make a report that had a problem caused by wodim, the
problem posted with cdrecord is different.
I would asume that the problem with cdrecord was caused by "hald" that
interrupts CD writing make in -sao/-dao
I have to agree with Derek. After trying all sugestions (except that one about
medibuntu which is nonsense) along this bug comments and destroying dozens of
cds, the only one that worked was getting rid of wodim and restoring cdrecord.
- Notebook HP DV 2240BR
- Kubuntu 8.04
- K3b Version: 1.0.4
Regarding comment #77 - whether or not the kernel was involved in this I
think it is clear for many people on this bug, including me, that
getting rid of wodim and restoring cdrecord solved their problem.
Whether this is because wodim is poorly supporting new kernel changes or
simply cdrecord is be
The best way to check seems to be to first try the official software
from:
ftp://ftp.berlios.de/pub/cdrecord/alpha/
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
I had suggested a while back that the problem lies not within the actual
crdkit (or whatever flavor you decide to use) but that the problem lies
in the kernel level interactions. If you think back to when the original
bug was posted it was around time that there was a significant shift in
the handl
The help page is vague for cdrskin but adding 14 or so "-v" gave me
this:
Track 11: 14 of 14 MB written (fifo 100%) [buf 99%] 32.3x.
cdrskin: DEBUG : SCSI error condition on command 2Ah : key=5h asc=30h ascq=06h
cdrskin: DEBUG : "Failure. See mmc3r10g.pdf: Sense Key 5 ASC 30 ASCQ 06"
cdr
Is this with maximum verbosity? Nothing else get printed out?
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to k3b in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.co
cdrskin fails at a different spot but unfortunately without a meaningful
error (yay, another coaster).
Track 11: Total bytes read/written: 14815248/14798784 (6292 sectors).
Writing time: 278.612s
Cdrskin: fifo had 10189 puts and 10189 gets.
Cdrskin: fifo was 0 times empty and 727 times full, min
How about you try cdrskin?
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/u
I am not convinced this is a case of cdrkit versus cdrtools. I have
installed the latest cdrtools and see the same issue occurring.
Perhaps this is a lower level scsi issue with newer kernels (and / or 64
bit)?
** Attachment added: "k3b_error_log2.txt"
http://launchpadlibrarian.net/28181877/k3
It is no wonder that you see that same problem. CDRkit is not maintained
and is extremely broken, yet nobody actually wants to admit it even if
there is a viable working alternative that I've been working on for the
last three years. Life goes on.
--
I can't write a cd
https://bugs.launchpad.net/
Well, two years since the initial bug was posted and I am seeing what
appears to be the same issue under Jaunty 64 bit. Logfile attached.
Symptoms are that disk writes fail after an arbitrary length of time,
generally at the same spot in the burn. This log file shows wodim
stalling out in the mid
@hpp3: ... if it works, then it's still just a workaround, and not a
fix. It won't impress anyone I try to recommend Kubuntu to. I realize
it's not your fault; I'm just getting frustrated that no-one seems to be
taking responsibility for bugs like this and bug #24234, for example.
--
I can't writ
@Tim McKenzie: Sorry that didn't work.
Setting the UID for wodim has also worked:
sudo chmod u+s /usr/bin/wodim
This might introduce a slight security risk, but if it works...
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a memb
cdrtools of course have no problem with writing CDs and DVDs.
older k3b versions however do not use cdrtools for writing DVDs.
Did you verify that k3b uses cdrecord for writing?
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a mem
Same here. Confirming this issue. I can read CD & DVD but I can't write.
Comment #38 removing the wodim fork and restoring cdrtools didn't worked
for me.
Using Ubuntu 8.04.2 desktop 32bits.
DVD writer ASUS DRW-2014S1T internal
Tried changing DVD writer jumper to Slave, Master or Cable but without
Out of curiosity, had you tried ditching wodim? :)
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
As I mentioned above, I was having the same issue, and the workarounds I
tried didn't help. I had been using an external DVD, plugged into a USB2
card.
After I installed an internal DVD, the problem disappeared completely,
and now works for me.
--
I can't write a cd
https://bugs.launchpad.net/bu
Thanks Derek. I might try cdrtools when I have some spare time.
In case anyone with any authority is still watching this thread: I'm
brave enough to compile from source if I need to, but this is still a
workaround, not a fix. How can I credibly recommend Kubuntu to anyone
else, when there are bugs
Hey Tim. In my opinion you should just ditch this wodim nonsense and try
cdrtools. Worked great for me on both machines, just like it always has.
Appears more reliable than the fork. Forks can be good or bad, but this one
doesn't seem to have worked out too well - I hope ubuntu had a darn good
hpp3's suggested change to /etc/security/limits.conf didn't work for me.
My attached fail log mentions burnfree. K3B consistently gets 43MB
through burning the Kubuntu Jaunty desktop i386 image. I'm getting bored
of making coasters out of someone else's blank CDs.
** Attachment added: "kubuntu-9.0
The cdrkit package provides wodim, it should however provide cdrtools
(confusing?)
However, cdrkit depends on brasero, or the other way round. i now removed
wodim, which in turn removed brasero.
So. there is a ppa which provides deb packages for cdrtools and mkisofs,
because is's not to up to
Oh, and FWIW, running as root and/or the IDE boot param from comment #41 didn't
help at all.
nor did running wodim from cli.
cdrtools required no changes whatsoever.
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Ubuntu
Removing the wodim fork and restoring cdrtools solved for me.
Thanks to IgnorantGuru in comment #38 for the suggestion.
https://bugs.launchpad.net/ubuntu/+source/cdrkit/+bug/149076/comments/38
The cdrtools website, as well as having some interesting info that explains to
me how ubuntu ended up d
After some research, I have come to the conclusion that this is a FEATURE, NOT
a BUG, of WODIM.
>From the wodim man page, concerning Process Scheduling Priority:
"Wodim tries to get higher process priority using different methods.
This is important because the burn process is usually a realtime
To: dpmacdon...@gmail.com
Subject: [Bug 149076] Re: I can't write a cd
dpmacdonald,
What version of ubuntu are you currently using?
Thanks,
Chris C.
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a direct subscriber
dpmacdonald,
What version of ubuntu are you currently using?
Thanks,
Chris C.
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to k3b in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-b
I have the same issue.
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubunt
Solved by upgrading cdrkit (in Gentoo, for Ubuntu check the package
which contains wodim)
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
I had this issue on my T42 laptop.
I solved the issue by cleaning dust from the optic lens ! :-)
Only took me 3 month to figure out
Maybe dust in the drive is the problem for some of you too!
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification b
I've the same problem, I can't burn CD's. When I tried the Intrepid Beta
Version I could burn DVD+RW, but only this kind of type in a LG DVD RW.
** Attachment added: "brasero-session.log"
http://launchpadlibrarian.net/19147624/brasero-session.log
--
I can't write a cd
https://bugs.launchpad.n
Issue confirmed in the backends => invalid for k3b itself.
** Changed in: k3b (Ubuntu)
Status: New => Invalid
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
Get NeroLinux..it's not free, but it works. I waited and tried to
solve the wodim issue for over a year before installing Nero.
Fred Hermanns wrote:
> I am having the same isuue with both HH and II. Have treid FireMans and
> IgnorantGuru's solutions.
> None was successfull.
>
>
--
I can't
I am having the same isuue with both HH and II. Have treid FireMans and
IgnorantGuru's solutions.
None was successfull.
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
As a followup, several people have reported that the workaround above
for replacing wodim does correct this, although in my case I had a
physically bad drive that had to be replaced (which confusingly produced
the same error). Step-by step-instructions are in this post...
http://ubuntuforums.org/s
Agreed, the bug description is really bad, please change.
And don't paste k3b error logs in comments, it's hard to read, that's what for
attachments are.
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks FireMan300. It's working fine here. But I am not sure the error
will happen again.
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed to k3b in ubuntu.
--
kubuntu-bugs mailing list
same problem here
with nero burning rom everything is fine
quite sad that a propretary program can do what opensource can't
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
this bug's importance should be set to critical. With a fresh Hardy
install, and the most prominent linux burning application K3B (as well
as other apps), the users can't burn any cd.
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a
I confirm this bug using the Brasero front end on Hardy 64, kernel 2-6-24-19.
Below is my Brasero error log.
** Attachment added: "brasero-session.log"
http://launchpadlibrarian.net/16955649/brasero-session.log
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug
I've been using a work around here for a few weeks to test and it seems
to be working. BONUS - no symlinks and you can try it without any
permanent changes.
1. When Grub loads hit the key to edit the commands "e", this should bring up a
series of lines "root", "kernel", and "initrd".
2. You want
Also FWIW, I've been speaking with the maintainer of libburnia and
xfburn, and he says libburn and cdrskin are replacements for wodim and
cdrecord and are built on a fresh codebase. He wrote: "Cdrskin can
replace cdrecord (even for k3b, just make a symlink from cdrecord ->
cdrskin) [or really from
I've just posted a different workaround using Wine and ImgBurn, which (for me,
anyway) was a lot less fussy:
http://ubuntuforums.org/showthread.php?t=884700
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Ubuntu
Bugs, wh
My suggestion: change broken fork wodim to the original cdrtools...
here is what worked for me. Use at your own risk.
Replacing wodim with the genuine cdrtools (tested on Kubuntu hardy)
The issue:
http://cdrecord.berlios.de/private/linux-dist.html
"If you are not running the original software, g
That's what I've been saying for over a year.
Johannes Hessellund wrote:
> Its not k3b, but the backend. Wodim!
>
> ** Changed in: cdrkit (Ubuntu)
> Sourcepackagename: k3b => cdrkit
>
>
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you ar
Its not k3b, but the backend. Wodim!
** Changed in: cdrkit (Ubuntu)
Sourcepackagename: k3b => cdrkit
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
I just did a fresh 8.04.1 install. I dont use kde or k3b for that
matter.
Brasero and nautilus failed on fresh install. No medibuntu packages were
installed.
Any devs working on this?
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are
Regarding K3B error: "Cdrecord has no permission to open the device."
Hello,
Perhaps my experience can provide some clues to the development team.
K3B was working beautifully until this week. The difference between
this week and last week is that I installed a bunch of extra stuff to be
able to
since an update und using Brasero, I did burn a couple of cd without
problem.
on another machine I had the same problem but I exchanged 1 drive to a
cd burner and now it works there too.
It is about time, they come up with a software solution.
odin schrieb:
> I've had as problem for me since ear
I gave up trying a long time ago. It's useless trying until someone
fixes wodim.
Johannes Hessellund wrote:
> Another observation...
>
> Simulation finishes succesfully on brasero, but burning fails.
> Log file shows the RLIMIT_MEMLOCK error also present when simulating, but
> doesn't stop the
Another observation...
Simulation finishes succesfully on brasero, but burning fails.
Log file shows the RLIMIT_MEMLOCK error also present when simulating, but
doesn't stop the simulation.
The real burning dies with the OPC failing.
Performing OPC...
/usr/bin/wodim: WARNING: Drive returns w
I've had as problem for me since early Gutsy. I'm so sick of it that
I'm considering going back to FreeBSD.
Johannes Hessellund wrote:
> This bug just appeared for me today!
>
> I dont burn cd's often. Last time I burned a cd was 2 weeks ago. Today i
> wasn't able to burn either audio or data c
This bug just appeared for me today!
I dont burn cd's often. Last time I burned a cd was 2 weeks ago. Today i
wasn't able to burn either audio or data cd's. Tried Brasero,
Gnomebaker, Serpentine, Nautilus-cd-burner.
Any of the resent updates causing this? I'm not really sure what has
been updated
All I know is that this issue hasn't been solved and I haven't been able
to burn a CD since early Gutsy. I've been using ZenWalk on my laptop
and am thinking about migrating to it on everything but my servers.
MacKinnon wrote:
> I have the same/similar problem and I DO have 2 drives (the second
I have the same/similar problem and I DO have 2 drives (the second/slave
one is my CD writable one).
I had a similar problem in Gutsy but upon freshly installing Hardy I
could burn iso's easily. The problem seems to have happened after an
update.
RLIMIT_MEMLOCK...is that part of the problem? Wha
Confirmed. Its in Hardy too.
This is from Gnomebaker
wodim: No write mode specified.
wodim: Asuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK
limits.scsidev: '/dev/sr1'
devname: '/d
Same problem in 8.04. combined_mode=ide did the trick.
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
Package should be set to cdrkit.
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
using gutsy and having the same problem, here the K3b log
System
---
K3b Version: 1.0.4
KDE Version: 3.5.8
QT Version: 3.3.7
Kernel: 2.6.22-14-generic
Devices
---
HL-DT-ST DVD-RAM GSA-H55L 1.02 (/dev/hdc, ) [CD-R, CD-RW, CD-ROM, DVD-ROM,
DVD-R, DVD-R
using gutsy and having the same problem, here the K3b log
System
---
K3b Version: 1.0.4
KDE Version: 3.5.8
QT Version: 3.3.7
Kernel: 2.6.22-14-generic
Devices
---
HL-DT-ST DVD-RAM GSA-H55L 1.02 (/dev/hdc, ) [CD-R, CD-RW, CD-ROM, DVD-ROM,
DVD-R, DVD-R
using gutsy and having the same problem, here the K3b log
System
---
K3b Version: 1.0.4
KDE Version: 3.5.8
QT Version: 3.3.7
Kernel: 2.6.22-14-generic
Devices
---
HL-DT-ST DVD-RAM GSA-H55L 1.02 (/dev/hdc, ) [CD-R, CD-RW, CD-ROM, DVD-ROM,
DVD-R, DVD-R
Forgot to mention: the above produces a 'coaster'.
--
I can't write a cd
https://bugs.launchpad.net/bugs/149076
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
This bug exists on Ubuntu (GNOME) 8.04 too.
Applications using wodim cannot burn any CD-R (multiple brands). The
drive is an Optiarc AD5170A (IDE), the kernel is 2.6.24 (default 32bit
shipping kernel).
There is no hardware problem with this machine. It works fine with Gutsy
or Windows. This seems
1 - 100 of 119 matches
Mail list logo
