https://bugs.kde.org/show_bug.cgi?id=387765
Simon Andric changed:
What|Removed |Added
CC||simonandr...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #38 from Thomas Schmitt ---
Hi,
> I noticed that when the ISO file is not recognizable, "Burn image" window
> shows no info about the file despite burning process is successful
> (screenshot).
Ahum. My olde Debian K3B
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #37 from Dr. Chapatin ---
Created attachment 110020
--> https://bugs.kde.org/attachment.cgi?id=110020=edit
screenshot
Fixing myself: Softwares should not show messages that can cause confusion.
The message shown by
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #36 from Thomas Schmitt ---
Hi,
> Why "invalid"?
Because it is not an ISO 9660 filesystem, regardless of its suffix ".iso".
Insofar the message of K3B is correct.
If i was annoyed by the dialog window about
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #35 from Dr. Chapatin ---
Why "invalid"?
This is a usability issue at least.
Softwares does should show messages that can be cause confusion.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387765
Leslie Zhai changed:
What|Removed |Added
Resolution|--- |INVALID
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #34 from Thomas Schmitt ---
Hi,
> I just burned the ISO from my link in a CD-RW.
So now our changes reached your desktop.
Next try whether it works with blu-ray sized images too.
> But the warning is not correct and it
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #33 from Dr. Chapatin ---
I just burned the ISO from my link in a CD-RW.
Despite the warning "Type of image file is not recognizable. Do you want to
burn it anyway?", if I answer "yes" burning process happens without
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #32 from Leslie Zhai ---
(In reply to Dr. Chapatin from comment #31)
> I use K3b 18.03.70 installed from AUR (k3b-git package) on my laptop and I
> can reproduce the problem.
It is better to provide screenshot step
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #31 from Dr. Chapatin ---
I use K3b 18.03.70 installed from AUR (k3b-git package) on my laptop and I can
reproduce the problem.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #30 from Thomas Schmitt ---
Hi,
just in case somebody wonders: I deleted the uploaded copy of
udf+image+created+with+nero.iso . So the link is now supposed to be dead.
Have a nice day :)
Thomas
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #29 from Thomas Schmitt ---
Hi,
the MD5 checksum matches the one i get here.
Somehow the K3B version of Dr. Chapatin is not the same as the one of Leslie.
The only idea i have is that Leslie instructs Dr. Chapatin how
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #28 from Leslie Zhai ---
(In reply to Thomas Schmitt from comment #27)
> Hi,
>
> i have put a copy of the image at
> http://scdbackup.webframe.org/udf+image+created+with+nero.iso
>
>
> Have a nice day :)
>
>
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #27 from Thomas Schmitt ---
Hi,
i have put a copy of the image at
http://scdbackup.webframe.org/udf+image+created+with+nero.iso
Have a nice day :)
Thomas
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #26 from Leslie Zhai ---
(In reply to Dr. Chapatin from comment #24)
> Hi Leslie
> I just noticed that the problem affects any ISO image created with nero
> using udf file system.
> I created a small ISO file to help
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #25 from Thomas Schmitt ---
Hi,
the given URL seems not to work without Javascript. But i found in
its lengthy HTML this URL
http://download864.mediafire.com/7l3plzb6fzqg/26outwdcybhtzyp/udf+image+created+with+nero.iso
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #24 from Dr. Chapatin ---
Hi Leslie
I just noticed that the problem affects any ISO image created with nero using
udf file system.
I created a small ISO file to help you.
Download it from here
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #23 from Leslie Zhai ---
(In reply to Dr. Chapatin from comment #22)
> You need use "burn image..." option from "tools" menu.
Not easy means blu-ray ISO is not available!
> @Leslie:
> I propose you create some
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #22 from Dr. Chapatin ---
You need use "burn image..." option from "tools" menu.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #21 from Leslie Zhai ---
(In reply to Dr. Chapatin from comment #20)
> Hi Leslie
> Any progress with this problem?
Sorry, I can't reproduce the issue easily
https://bugs.kde.org/show_bug.cgi?id=387765#c18
--
You
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #20 from Dr. Chapatin ---
Hi Leslie
Any progress with this problem?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #19 from Thomas Schmitt ---
Hi,
but mkisofs has no stake in image burning. It _makes_ images.
Are you sure you have chosen the right job in K3B ?
(Normally i'd ask to run the mkisofs command in a shell and to watch for
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #18 from Leslie Zhai ---
mkisofs crashed...
Burned media
---
DVD+R
Devices
---
CDEmu Virt. CD/DVD-ROM 1.10 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R,
DVD+R) [DVD-ROM,
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #17 from Thomas Schmitt ---
Hi,
> Arch Linux, K3b 17.11.90
Google brings me to the page of "k3b 1:17.11.90-1"
https://www.archlinux.org/packages/kde-unstable/x86_64/k3b/
and after some URL manipulation i get to
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #16 from Dr. Chapatin ---
(In reply to Thomas Schmitt from comment #14)
> Hi,
>
> @Dr. Chapatin:
> Did you verify that your K3B source does have these lines in
> in
> src/misc/k3bimagewritingdialog.cpp
> ?
Sorry, can
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #15 from Dr. Chapatin ---
(In reply to Thomas Schmitt from comment #13)
> What do you get from
> mount -o loop -t iso9660 file.iso /mnt/imagemiso
> ?
> If this refuses then we really have such an UDF.
I get this
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #14 from Thomas Schmitt ---
Hi,
@Dr. Chapatin:
Did you verify that your K3B source does have these lines in
in
src/misc/k3bimagewritingdialog.cpp
?
if (d->foundImageType == IMAGE_UNKNOWN) {
if
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #13 from Thomas Schmitt ---
Hi,
the main riddle now is why the image is not copied to medium after
the warning has been accepted and overridden by the user.
@Leslie:
I propose you create some dummy image file and make
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #12 from Dr. Chapatin ---
Sorry, "sudo mount -t udf -o loop file.iso /mnt/imagemiso" previously failed
because kernel update.
The command worked after I restart my computer.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #11 from Dr. Chapatin ---
I have no BD-RE available.
K3b shows "Type of image file is not recognizable. Do you want to burn it
anyway?" immediately after I select the ISO file in "burn image" window. I
don't need to
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #10 from Thomas Schmitt ---
Hi,
regardless of the question why K3B does not recognize the image file as
ISO 9660 there stays the question whether and why it then really refuses
to write.
So please answer the question
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #9 from Dr. Chapatin ---
this inormation appears in terminal when I select the iso file
K3b::Iso9660::openArchive no volume descriptors
(K3b::CloneTocReader) could not open file
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #8 from Dr. Chapatin ---
(In reply to Thomas Schmitt from comment #6)
> the suspicion that you have a .NRG image.
it's not the case. My image is an ISO file.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #7 from Dr. Chapatin ---
(In reply to Thomas Schmitt from comment #6)
> What do you get from command "file" ?
>
> file /path/to/image/file
Hi Thomas
result of "file file.iso" command is "file.iso: data"
--
You
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #6 from Thomas Schmitt ---
Hi,
another interesting point is why your image is not recognized as IMAGE_ISO
by K3B.
What do you get from command "file" ?
file /path/to/image/file
The following code reasoning and your
https://bugs.kde.org/show_bug.cgi?id=387765
Thomas Schmitt changed:
What|Removed |Added
CC||scdbac...@gmx.net
---
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #4 from Dr. Chapatin ---
Well, I can't burn bd25 iso on my computer using K3b...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387765
--- Comment #3 from Leslie Zhai ---
Thomas has already reviewed src/misc/k3bimagewritingdialog.cpp, which produced
the message as you reported, and he introduced a new image type RAW
https://bugs.kde.org/show_bug.cgi?id=387765
Dr. Chapatin changed:
What|Removed |Added
Status|RESOLVED|REOPENED
https://bugs.kde.org/show_bug.cgi?id=387765
Leslie Zhai changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
40 matches
Mail list logo