Hide Forgot
Description of problem: Inserted a microSD containing a Raspbian image Version-Release number of selected component: e2fsprogs-1.43.5-2.fc27 Additional info: reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: dumpe2fs -h /dev/sdc2 crash_function: e2p_is_null_uuid executable: /usr/sbin/dumpe2fs journald_cursor: s=b50f04b5f1fc4d75bb8869b6b131470e;i=a39dc;b=7848dee73d02475f9e3c70753cc9d7fe;m=34a612a92;t=56983b61db9a6;x=1bda6a920cb71746 kernel: 4.15.14-300.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (4 frames) #0 e2p_is_null_uuid at uuid.c:32 #1 e2p_uuid2str at uuid.c:80 #2 e2p_list_journal_super at ljs.c:105 #3 print_inline_journal_information at dumpe2fs.c:395
Created attachment 1420052 [details] File: backtrace
Created attachment 1420053 [details] File: cgroup
Created attachment 1420054 [details] File: core_backtrace
Created attachment 1420055 [details] File: cpuinfo
Created attachment 1420056 [details] File: dso_list
Created attachment 1420057 [details] File: environ
Created attachment 1420058 [details] File: exploitable
Created attachment 1420059 [details] File: limits
Created attachment 1420060 [details] File: maps
Created attachment 1420061 [details] File: mountinfo
Created attachment 1420062 [details] File: open_fds
Created attachment 1420063 [details] File: proc_pid_status
Hi, thanks for the report. Can you provide a link to the Raspbian image that you can reproduce it with ? If not available online can you please attach e2image ? e2image -r /dev/sdc2 - | bzip2 > sdc2.e2i.bz2 Thanks! -Lukas
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.