** Changed in: hal
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/66254
Title:
empty CD not correctly recognized by hal
--
ubuntu-bugs mailing list
ubuntu-bugs@list
** Changed in: hal
Importance: Medium => Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/66254
Title:
empty CD not correctly recognized by hal
--
ubuntu-bugs mailing list
ubuntu-bugs@list
This bug was fixed in the package hal - 0.5.10+git20080301-1ubuntu1
---
hal (0.5.10+git20080301-1ubuntu1) hardy; urgency=low
* Merge with Debian to pull in a current snapshot from upstream git head
(upstream neglects doing a long-overdue 0.5.11 release). This pulls in two
to
** Changed in: hal
Status: Unknown => Fix Released
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
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.ub
** Bug watch added: freedesktop.org Bugzilla #12822
https://bugs.freedesktop.org/show_bug.cgi?id=12822
** Also affects: hal via
https://bugs.freedesktop.org/show_bug.cgi?id=12822
Importance: Unknown
Status: Unknown
--
empty CD not correctly recognized by hal
https://bugs.launchpa
This patch is included in my currently prepared Hardy hal upload. You
can already test it now by installing the packages in my PPA:
https://launchpad.net/~pitti/+archive
** Changed in: hal (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
Status: Triaged => Fix Committed
--
empt
** Changed in: hal (Ubuntu)
Status: Confirmed => Triaged
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
Alberto: just seen that someone has filed a bug report that sounds like
it might be your issue: Bug #158033.
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for U
alberto... this bug report is not related to your problem and should
only be used for things that are related to this bug. please use the
answers section to seek help or file your own bug report.
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
You received this b
I run hald from a shell, as
$ sudo hald --daemon=no --verbose=yes 2>&1 | tee hal.log
I confirm, when i insert a blank disk no debug output is shown, just no
reaction at all.
In hal-device-manager the cd drive is listed as a scsi device, DVDRW
GWA4080MA. All the properties like store.cdrom.cdr, c
This does not look like the problem I addressed with my patch, as it is
unllkely your CD drive is not MMC-2, and the problem would have showed
up in Feisty. Not sure the wiki is quite appropriate, but certainly
check HAL output: as well as using HALD in debug mode you can use the
HAL device manage
Hi all,
I'm having the same problem with Gutsy on a Macbook.
HAL doesn't seem to recognize blank CDs and DVDs.
Used to work just fine with Feisty, though.
Inspected the log output of udev, gnome-volume-manager and hald, as in
https://wiki.ubuntu.com/DebuggingRemovableDevices, but none of them
sho
Thank you David. Your patch worked for me too. My own patches posted on
2007-07-07 and 2007-07-08 don't work. I'm still trying to make them
work.
Unfortunately ubuntu update notifier constantly suggests to replace the
patched version with a more recent version because I applied the patch
to versio
I did it myself.
I have made a patch to HAL that might fix this problem for you.
** Attachment added: "Patch to HAL to fix problem with old drives."
http://launchpadlibrarian.net/8641865/68-disc_identification.patch
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/
Mmm, interesting, I realise others are stumbling around the same problem as I
have, though I had made my comments on https://bugs.launchpad.net/bugs/109763.
As the HAL specification says that volume.disc.capacity is not mandatory, I
guess HAL developers may not accept the idea of including the co
** Attachment added: "Changes uncommented"
http://launchpadlibrarian.net/8335900/get_disc_type
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Hello!
I tried to apply the suggested changes to the source code of hal, but
even before this I didn't manage to compile hal. It always ends up with
an error message like this:
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib/libpci.a(names.o): In
function `pci_load_name_list':
(.text+0x538): u
Hello!
I have the same problem with my Lite-on LTR-12101B CD burner since the
upgrade from ubuntu 6.06 to 6.10.
Interestingly hal under 6.06 didn't recognize inserted media either. So
my first supposition was that a change in the code of nautilus-cd-burner
was responsible for the error. I found o
Thanks a lot Thorsten !
Now I can burn cds with nautilus.
The last problem is that brasero still says "no disc" when I insert a blank cd.
Maybe it's a brasero bug ?
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
You received this bug notification because you ar
Hello Sika,
the .fdi won't work with the new hal from feisty-backports since that version
doesn't support the uint64 data type anymore for whatever reason. If you have
the feisty-backports channel active downgrading hal to the feisty version will
likely do the job.
--
empty CD not correctly re
Here is a full hal debug output (as described on the second half of
https://wiki.ubuntu.com/DebuggingRemovableDevices).
** Attachment added: "hak debug log"
http://launchpadlibrarian.net/8118347/hal.log
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
You rece
I have the same problem.
My burner is a LG CED 8080B.
I've tried to create the .fdi file of Thorsten Schoel but it simply don't work
(volume.disc.type and volume.disc.capacity are not changed).
I've tried to use cdrecord and it seems to work.
If you need some infos just ask.
--
empty CD not corr
** Attachment added: "lshal"
http://librarian.launchpad.net/7582433/lshal
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Hello,
Ubuntu Edgy: 6.10
Serpentine 0.7 doesn't see blank disks for me too.
If you need more info just drop me an email.
** Attachment added: "cddrives"
http://librarian.launchpad.net/7582431/List%20cddrives
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
Thorsten Schoel,
Thank you for the workaround it works perfectly.
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubunt
** Attachment removed: "10-cd-r.fdi"
http://librarian.launchpad.net/7352962/10-cd-r.fdi
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubunt
The file I tried to attach above is a perfect workaround as long as you only
use media of one type and size. The upload was broken though, so I'll attach it
again here.
As I said above it goes to /etc/hal/fdi/information.
** Attachment added: "10-cd-r.fdi"
http://librarian.launchpad.net/75256
Well, I don't know why, but launchpad won't allow me to attach that
file. So here are its contents:
-cut-
cd_r
My workaround was to use X-CD-Roast instead, but the drive recently
failed on me, cdrecord had quit working too. So i replaced the cheap
2001 HP 'R/RW 8x4x32' with a 2002 'CDWRITER IDE2410' and that solved the
pbm for me. But yes, with the old drive before its failure, X-CD-Roast
wasn't giving me a
a workaround would be to use cdrecord
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
Is their anyone still working on this bug or anyone who has found a
workaround?
I am affected by it and it is the only thing keeping me from upgrading
my dapper installation to feisty.
If there is anything I can do to help get this fixed let me know.
--
empty CD not correctly recognized by hal
No it isn't. I have the problem since edgy. Maybe the backend for
nautilus cd-burner changed then to make use of HAL.
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug cont
In thinking about this some more, I am wondering if this problem is
related to the change from PATA to SATA drivers in 2.6.20. I wonder if
the old IDE driver has some special code to handle older drives that
gave bogus data. That is the only reason I can think of to be causing
this sort of problem
the attatched file goes into /etc/hal/fdi/information. This fixes the
problem for me but might not fix it for everyone. The script simply
changes anything that is a volume with a parent that can burn cd-rs and
that has an unknown type and is blank into a cd-r with 700MB. This is
certainly not a rea
Yes, cdrecord does work properly (it says something like "drive reports wrong
startsec of -150 for track 1. assuming startsec 0" though). neither
nautilus-cd-burner nor brasero work though. Last time it worked was on dapper.
btw i tries writing an fdi script to change the values in hal. This made
oddly enough. this used to work fine in edgy & dapper.
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
Thorsten, does cdrecord work properly? In my case, cdrecord works but
CD-Creator does not.
My read of the hal code is that it is at the mercy of the drive firmware
(or device driver). It performs no added value other than issueing the
ioctl and mapping the content appropriately.
--
empty CD not
Well it seems that my drive (which is affected - see dup #72654) does
report the correct size which is 359849 sectors (with 2048 Bytes in each
sector that makes about 700MB), at least according to cdrecord
dev=/dev/hdd -atip. Unfortunately it does report a wrong start sector
(i.e. start of lead in
Both good points. Here is my view/opinion on how to proceed. BTW, this
will have to be fixed upstream in Gnome...
First, cdrecord probably does not check the capacity prior to recording,
and will fail if the eventutal amount of data to be copied to the drive
exceeds the capacity of the cd.
So, it
The drive I am using is a External SCSI HP 9600 (from dup bug 69033).
It is only 5 years old. I would prefer that this bug was investigated
(and hopefully fixed) rather than deffered.
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
You received this bug notifica
Please don't be so hasty to write this one off and advise users to
upgrade: the drive I'm having problems with is in a relative's 6/7 year
old Dell, so probably not an uncommon piece of kit (and certainly not
that old). How come cdrecord functions fine with the drive if there is
some fundamental f
BTW, This drive is a CDWriter IDE 8432. This was a fairly common drive.
Bet that most of these type reports are due to the various rebadged
drives of this type. This one was made by BTC for CDWriter, I think.
Best to defer this bug and recommend that they upgrade to newer hdwe. No
firmware avail fo
I think this may be due to buggy cd rom firmware, if my rusty code
reading skills are still valid. In probe_volume.c, it appears that the
ioctl data back from the driver is bogus for blank media. For sure, the
disc.type field is being marked as unknown. If I put in a non-blank
disk, I get valid siz
I will confirm that this problem is still happening on the RC version of
Feisty. Can pull logs, etc if needed... using cdrecord worked just fine
so no hdwe issue.
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
You received this bug notification because you are a
I believe 69033 and 72654 are duplicates of this one. Don't know if I'm
entitled to simply mark them as such though...
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug con
I also have exactly the same problem with a 'SAMSUNG_CDRW/DVD_SM_308B'.
My IDE controller is a '82801BA IDE U100' according to device manager,
if this is of relevance. I tried a second drive earlier and this also
failed in what seemed to be an identical manner, however I no longer
have access to t
I also have exactly the same problem with a 'SAMSUNG_CDRW/DVD_SM_308B'.
My IDE controller is a '82801BA IDE U100' according to device manager,
if this is of relevance. I tried a second drive earlier and this also
failed in what seemed to be an identical manner, however I no longer
have access to t
I still have this problem with the new feisty beta. Is someone working
to find out the problem or is there a hope for a solution?
--
empty CD not correctly recognized by hal
https://bugs.launchpad.net/bugs/66254
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I have the same problem here using a LG_CD_RW_CED_8120B
WARNING **: No property volume.disc.capacity on device with id
/org/freedesktop/Hal/devices/volume_empty_unknown
when using nautilus-cd-burner or Brasero.
It simply asks to add a support and refuses any CDR. This is very
annoying as I'm no
49 matches
Mail list logo
