This is still a problem. Burner apps like k3b does detect the drive. And I can also burn standard stuff with command line burner tools like wodim and the likes.
The all of these tools doesn't identify my Blu-ray burner as a Blu-ray burner. Even when inserting a Blu-ray disc, they all think it's just a DVD, and thus complains there isn't enough room. ImgBurn (via Wine) says it can't detect the drive. I need to use ImgBurn because it's my only way of getting UDF 2.5 since there's no UDF 2.5 available for Linux. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737671 Title: Blu-ray burner no longer detected Status in linux package in Ubuntu: Expired Bug description: Linux Kernel 97 is the last kernel in which my Blu-ray burner is still detected. Booting with all following kernels makes it undetectable, and I can't use it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-103-generic 4.4.0-103.126 ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98 Uname: Linux 4.4.0-103-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: misthalu 1913 F.... pulseaudio CurrentDesktop: Unity Date: Tue Dec 12 08:00:12 2017 HibernationDevice: RESUME=UUID=d22d1aa7-36b9-44ab-936e-f713d1f79a40 InstallationDate: Installed on 2016-05-19 (571 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lo no wireless extensions. enp8s0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z170X-Gaming 3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic root=UUID=9b2e1b7a-2bbd-4a36-990f-6ba56f567b2d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-103-generic N/A linux-backports-modules-4.4.0-103-generic N/A linux-firmware 1.157.14 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170X-Gaming 3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z170X-Gaming 3 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
