[Bug 1842116] Re: jpegexiforient does not reliably detect EXIF orientation
This issue makes the related, top-level utility `exifautotran` unreliable for auto-rotating images, since that utility depends on the output from `jpegexiforient`. As a workaround, it appears that using `jhead -autorot` works. jhead uses `jpegtran` under the hood. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842116 Title: jpegexiforient does not reliably detect EXIF orientation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg9/+bug/1842116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842116] Re: jpegexiforient does not reliably detect EXIF orientation
For additional context, the image in question was produced by an Epson Perfection V600 Photo scanner. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842116 Title: jpegexiforient does not reliably detect EXIF orientation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg9/+bug/1842116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842116] Re: jpegexiforient does not reliably detect EXIF orientation
I just converted the above original question into a bug report; I was not the original author of the question. I'm seeing similar behavior, but only with some images. I have an image where using ExifTool produces an EXIF Orientation of 3, but jpegexiforient returns nothing: > identify -format '%[EXIF:Orientation]' 00301827_0.jpg && echo && echo 3 > jpegexiforient 00301827_0.jpg (No output) Attached is exiftool's EXIF metadata dump in HTML format. I am guessing that perhaps the EXIF tags are in a different place in the file than `jpegexiforient` is used to? ** Attachment added: "00301827_0_jpg.html" https://bugs.launchpad.net/ubuntu/+source/libjpeg9/+bug/1842116/+attachment/5285842/+files/00301827_0_jpg.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842116 Title: jpegexiforient does not reliably detect EXIF orientation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg9/+bug/1842116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842116] [NEW] jpegexiforient does not reliably detect EXIF orientation
Public bug reported:
It seems this program isn't operative in Ubuntu 18.04, unless I've
overlooked something.
$ md5sum parrots.jpg
1b624b6d36f1c47f17095ae3dd336a92 parrots.jpg
$ jpegexiforient -2 parrots.jpg
$ echo $?
0
$ md5sum parrots.jpg
1b624b6d36f1c47f17095ae3dd336a92 parrots.jpg
$ jpegexiforient -9 parrots.jpg
jpegexiforient reads or writes the Exif Orientation Tag in a JPEG Exif file.
Usage: jpegexiforient [switches] jpegfile
Switches:
--help display this help and exit
--version output version information and exit
-n Do not output the trailing newline
-1 .. -8 Set orientation value 1 .. 8
$ echo $?
1
$ jpegexiforient -3 parrots.jpg
$ echo $?
0
$ md5sum parrots.jpg
1b624b6d36f1c47f17095ae3dd336a92 parrots.jpg
Visually confirmed that the image does not display any differently after
the failed EXIF changes (which would have been an interesting result
considering the hash of the file stayed constant).
I downloaded a sample JPEG file from the following location ("PARROTS")
https://www.fileformat.info/format/jpeg/sample/
** Affects: libjpeg9 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842116
Title:
jpegexiforient does not reliably detect EXIF orientation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg9/+bug/1842116/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687631] Re: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp
I believe I have a solution to my own problem: the VM in question was configured by Vagrant, without "Data Exchange" selected in Hyper-V under "Settings" -> "Integration Services". Once "Data Exchange" is enabled, "/dev/vmbus/hv_kvp" shows up and the "open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory" error stops appearing in the `syslog`. ** Attachment added: "Where to find the setting in question" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+attachment/4870857/+files/Data%20Exchange.png ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687631 Title: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687631] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1687631/+attachment/4870839/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687631 Title: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687631] Re: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp
** Attachment added: "These are the cloud tools installed." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+attachment/4870840/+files/cloud-tools.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687631 Title: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687631] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1687631/+attachment/4870833/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687631 Title: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687631] Re: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp
apport information ** Tags added: apport-collected xenial ** Description changed: When running `linux-image-4.4.0-77-generic` on 16.04 LTS (as installed via the `linux-virtual` package) on Hyper-V, the KVP daemon is unable to start because the /dev/vmbus/hv_kvp device is missing. Consequently, Hyper-V is unable to obtain networking information about the VM (for example, IP addresses for vagrant, etc). Both `syslog` and `ls` indicate that the file is missing: root@dev-app:~# ls /dev/vmbus/ -l total 0 crw--- 1 root root 10, 55 May 2 00:11 hv_fcopy crw--- 1 root root 10, 54 May 2 00:11 hv_vss LSB Release Info: Description:Ubuntu 16.04.2 LTS Release:16.04 + --- + AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.5 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=/dev/mapper/vagrant--vg-swap_1 + InstallationDate: Installed on 2016-08-01 (273 days ago) + InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) + IwConfig: Error: [Errno 2] No such file or directory + Lsusb: Error: command ['lsusb'] failed with exit code 1: + MachineType: Microsoft Corporation Virtual Machine + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + LANGUAGE=en_US: + TERM=xterm + PATH=(custom, no user) + LANG=en_US + SHELL=/bin/bash + ProcFB: 0 hyperv_fb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-77-generic root=/dev/mapper/vagrant--vg-root ro quiet + ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-77-generic N/A + linux-backports-modules-4.4.0-77-generic N/A + linux-firmwareN/A + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial + Uname: Linux 4.4.0-77-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 01/06/2017 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 090006 + dmi.board.name: Virtual Machine + dmi.board.vendor: Microsoft Corporation + dmi.board.version: 7.0 + dmi.chassis.asset.tag: 7648-2779-0271-7579-3784-7264-48 + dmi.chassis.type: 3 + dmi.chassis.vendor: Microsoft Corporation + dmi.chassis.version: 7.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd01/06/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: + dmi.product.name: Virtual Machine + dmi.product.version: 7.0 + dmi.sys.vendor: Microsoft Corporation ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1687631/+attachment/4870832/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687631 Title: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687631] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1687631/+attachment/4870838/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687631 Title: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687631] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1687631/+attachment/4870836/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687631 Title: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687631] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1687631/+attachment/4870837/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687631 Title: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687631] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1687631/+attachment/4870834/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687631 Title: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687631] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1687631/+attachment/4870835/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687631 Title: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687631] [NEW] On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp
Public bug reported: When running `linux-image-4.4.0-77-generic` on 16.04 LTS (as installed via the `linux-virtual` package) on Hyper-V, the KVP daemon is unable to start because the /dev/vmbus/hv_kvp device is missing. Consequently, Hyper-V is unable to obtain networking information about the VM (for example, IP addresses for vagrant, etc). Both `syslog` and `ls` indicate that the file is missing: root@dev-app:~# ls /dev/vmbus/ -l total 0 crw--- 1 root root 10, 55 May 2 00:11 hv_fcopy crw--- 1 root root 10, 54 May 2 00:11 hv_vss LSB Release Info: Description:Ubuntu 16.04.2 LTS Release:16.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "Syslog" https://bugs.launchpad.net/bugs/1687631/+attachment/4870816/+files/syslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687631 Title: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687631] Re: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+attachment/4870817/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687631 Title: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609475] Re: Recovery mode won't allow recovery after manually installing the OS incorrectly
I just ran into this issue with Bento Box's 64-bit image for 16.04. We were trying to boot into recovery mode in order to run `zerofree` prior to packaging up a custom box for internal use (per steps from https://snippets.khromov.se/shrinking-a-virtualbox-linux-image-with- zerofree/). I can confirm this is a systemd-specific issue. We booted normally, followed instructions under "Permanent switch back to upstart" in https://wiki.ubuntu.com/SystemdForUpstartUsers, and rebooted, which successfully removed systemd. We then booted into Recovery Mode and had no interruptions or strange boot behavior (though there was an error about not being able to start "User Service" on the boot after installing Upstart). Prior to removing systemd, the behavior @b-candler described is exactly what we were seeing -- after about 1 to 2 mins, it seems like systemd gets impatient and starts booting the system normally, bringing up networking, etc, AND THEN starts the recovery menu and recovery shell on top of an existing session. After another few minutes, you actually get a third one on top of that. If you can actually brave the storm and get to a prompt, running `init 1` will cause a system hang. Looks like Ubuntu is not alone here: - https://www.reddit.com/r/linuxquestions/comments/5dug3e/linux_mint_recovery_mode_crashingtiming_out/ - https://forums.linuxmint.com/viewtopic.php?t=232329 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609475 Title: Recovery mode won't allow recovery after manually installing the OS incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
