On 01.08.2015 13:33, Alchemist wrote:
2015-08-01 14:21 GMT+03:00 Joachim Backes <joachim.backes@rhrk.uni-kl.de mailto:joachim.backes@rhrk.uni-kl.de>:
On 01.08.2015 12:25, Alchemist wrote: > > > 2015-08-01 12:47 GMT+03:00 Joachim Backes <joachim.backes@rhrk.uni-kl.de <mailto:joachim.backes@rhrk.uni-kl.de> > <mailto:joachim.backes@rhrk.uni-kl.de <mailto:joachim.backes@rhrk.uni-kl.de>>>: > > Hi all, > > seems, LINUX is full of sound: Trying to write /boot/vmlinuz... to a > data CD with k3b. If I drag such a file to the "Data Project" subwindow > of k3b, it is identified as audio file, and the CD burning is rejected. > Same with files like initramfs... > > This happens at least with k3b-2.0.3-3.fc22.x86_64. > > Kind regards > > -- > > > Perhaps because vmlinuz signature header (1byte+1nibble) is similar to > MIDI format header, in case if k3b parses headers for files without > extensions. > > > Fedora release 22 (Twenty Two) > Kernel-4.1.3-201.fc22.x86_64 > > > Joachim Backes <joachim.backes@rhrk.uni-kl.de <mailto:joachim.backes@rhrk.uni-kl.de> > <mailto:joachim.backes@rhrk.uni-kl.de <mailto:joachim.backes@rhrk.uni-kl.de>>> > https://www-user.rhrk.uni-kl.de/~backes > -- > users mailing list > users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> <mailto:users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org>> > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org > > Starting k3b directly by "k3b --data /boot/vmlinuz*", then k3b marks these kernel files correctly as data files, and I can burn that data CD, so I guess it's a drag/drop problem. Kind regardsOk if you really don't see valid file types mentioned by Ed, your MIME db may be altered. Check for valid filetypes
xdg-mime query filetype /boot/initramfs* xdg-mime query filetype /boot/vmlinuz*
and for default apps for theese valid types also
xdg-mime query default application/x-raw-disk-image xdg-mime query default application/x-ms-dos-executable
Not sure as I can't test it now, but check if k3b stores somewhere local filetype cache, so reset could be useful.
.kde4/share .config .local/share .cache
Hi alchemist,
Another point: clicking first on the "New Data Project" button, and then dragging /boot/vmlinuz... to the Data project window, no error happens, and I can burn flawlessly. It seems that the direct drag/drop process selects the wrong target action.
Joachim Backes
On 08/01/15 19:35, Joachim Backes wrote:
Another point: clicking first on the "New Data Project" button, and then dragging /boot/vmlinuz... to the Data project window, no error happens, and I can burn flawlessly. It seems that the direct drag/drop process selects the wrong target action.
It seems to be a "where you drop it" issue.
If I start k3b but don't click on one of the 4 options in the lower window....but drop one of those files on the area showing "new data project" "new audio project" "copy medium" then everything is fine....
If I drop the file outside of that area, like on the color background, sometimes I see what you see. Not 100% reproducible.
I guess it is annoying.... :-)