Thank you, and I apologise for having missed the critical message that
identifies the problem cause pretty conclusively. Possibly, I was
having a bad day.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Public bug reported:
Automatic update failed.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.7
ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78
Uname: Linux 5.4.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
U
Thank you, once again, Thomas.
I've noticed I omitted to post the command line:
xorrecord dev=/dev/sr0 -v padsize=0 -multi fs=64m blank=format_overwrite
Disc01.iso
I hope I'd followed your recommendation correctly.
I am far from unhappy with the writing speed. Considering it has taken
me a yea
Success, at last!
I burnt a couple of BD-R discs, on Monday, using a USB 2 card, fitted
into the problem PC, as the source external HD connection, and the rate
was roughly 22 GiB in half an hour.
Here's the tail end of the output:
xorriso : UPDATE : 22408 of 22530 MB written (fifo 98%) [buf 96%
Thomas,
I slightly favour the second option as, although I think it is not yet
strictly proven, whereas the first is one of those assertions that
stands until disproven, it does have a reasonable chance of pointing
anyone who suffers a similar issue in the right direction fairly
quickly.
I may ac
My work on verifying that this is genuinely a problem in libburn has
stalled. I apologise for this, but more so for having neglected to
provide a potentially critical interim update (which now follows upon
the prompting of someone having clicked a “me too” button).
Whilst I was in the process of
Hi Thomas,
Thank you very much for all the recommended commands, and your careful
explanations. I'm about to copy these to my own stash of notes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458230
Hi,
Thank your for the answers, and sorry I've been a while in responding.
I am preparing more data for back-up, and my plan is to reinstate my
Windows XP partition and investigate Blue-ray BD-R burning behaviour
with (probably) CDBurnerXP.
I agree that the evidence suggest that Defect Managemen
Sorry, looking back on this, I recognise I burnt only three of the BD-Rs
with libburn, not the four I'd claimed. The exaggeration was entirely
unintentional.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
DVD-RW 2x burning with cdrskin:
INQUIRY:[PIONEER ][BD-RW BDR-209M][1.20]
GET [CURRENT] CONFIGURATION:
Mounted Media: 14h, DVD-RW Sequential
Media ID: JVC_VictorW7
Current Write Speed: 2.0x1385=2770KB/s
Write Speed #0:2.0x1385=2770KB/s
Speed Des
disc06 burnt with xorrecord (xorrecord -v dev=/dev/sr0 speed=26970k
fs=8m -multi --grow_overwriteable_iso blank=as_needed padsize=300k
disc06.iso):
INQUIRY:[PIONEER ][BD-RW BDR-209M][1.20]
GET [CURRENT] CONFIGURATION:
Mounted Media: 41h, BD-R SRM
Media ID:
disc01 burnt with k3b (brandonsnider cdrtools PPA):
INQUIRY:[PIONEER ][BD-RW BDR-209M][1.20]
GET [CURRENT] CONFIGURATION:
Mounted Media: 41h, BD-R SRM
Media ID: CMCMAG/BA5
Current Write Speed: 12.0x4495=53940KB/s
Write Speed #0:12.0x4495=53940KB
Thank you very much for looking into this, and I'll apologise for
having, at best, asymptotically approached the scientific method whilst
attempting to burn a set of back-up discs.
My first burn used the k3b GUI. I had to install the brandonsnider
cdrtools PPA, before it would even start writing
Public bug reported:
Note: libburn 1.3.8 (Ubuntu 15.04 AMD64)
Confident of correctly observing the symptom (in four / four tests with
BD-R 25 GB), but apologise for pointing a finger that may be stabbing in
the dark.
dvd+rw-mediainfo /dev/sr0
INQUIRY:[PIONEER ][BD-RW BDR-209M][
Phillip,
Neat question.
The machine has gone through a few upgrade cycles now. I think it's on
13.10. No problem with the upgrades.
It's not a test rig. So, not practical to try a fresh installation,
sorry.
I suggest either later versions lack the fault or the specific
configuration which it
I am experiencing what is likely the same thing with 11.04 (Natty
Narwhal) i386 (2.6.38-8-generic), having installed Ubuntu on one
particular PC for the first time.
PC has two hard discs: boot disc is IDE and a second hard disc is SATA.
The SATA was in "RAID" mode, in the BIOS, (though not using a
** Description changed:
Binary package hint: ubiquity
I have now tried this twice, in case I'd bungled the selection the first
time around and because I'd know to collect details, the second time.
(Note, although my Ubuntu installation booted the first time, it did not
seem to be reco
** Attachment added: "Screen shot - selection of
/dev/mapper/isw_gcjjjacje_MC-PC001_RAID5 as device for boot loader
installation."
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/732771/+attachment/1899327/+files/Screenshot.png
--
You received this bug notification because you are a
** Attachment added: "Mapping sym links within Live CD session."
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/732771/+attachment/1899325/+files/mapper-symlink.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
** Attachment added: "Mappings within Live CD session."
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/732771/+attachment/1899324/+files/mapper.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Attachment added: "Linux partition (5) "boot sector" all zero."
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/732771/+attachment/1899323/+files/RAID5-bootsector_bin.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
** Attachment added: "MBR created by Ubiquity (hexdump -C)"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/732771/+attachment/1899322/+files/RAID-MBR-446_bin.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Attachment added: "Partman file as requested on Ubiquity bug-reporting page."
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/732771/+attachment/1899317/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
** Attachment added: "syslog"
https://bugs.launchpad.net/bugs/732771/+attachment/1899307/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/732771
Title:
Ubuntu 10.10 (AMD 64) installer
Public bug reported:
Binary package hint: ubiquity
I have now tried this twice, in case I'd bungled the selection the first
time around and because I'd know to collect details, the second time.
(Note, although my Ubuntu installation booted the first time, it did not
seem to be recognising that th
Thank you for following up.
I am very sorry to have nothing to contribute.
I am an infrequent user of the calculator, and have seen no similar
occurrence. I have used both Karmic and Lucid for a few months, recently
switching to Lucid on both PCs (32 bit and 64 bit).
If there is not a clear clu
Same (or similar) problem with ASUS X5DIJ running ubuntu-10.04-desktop-
amd64. Strange, since worked OK with 9.10 64 bit (ubuntu-9.10-desktop-
amd64).
Neither the function keys nor the panel applet actually affects the
brightness. The power management centre also has no effect.
Brightness-chang
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/41781683/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/41781684/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/41781685/ProcStatus.txt
** Attachm
Public bug reported:
Binary package hint: gcalctool
Only sending this in case the debugging information is of more use than
my typed report (i.e. > 0). The app. didn't seem to crash, and has done
nothing of which I need to complain (or would feel I could complain
about, if I wasn't using free so
29 matches
Mail list logo
