Description of problem: I mounted an ISO image with the loop device and started 'fedup --device' Version-Release number of selected component: fedup-0.7.1-1.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 cmdline: /usr/bin/python /usr/bin/fedup-cli --device kernel: 3.6.7-4.fc17.x86_64 backtrace: :grubby.py:63:get_entry:TypeError: __new__() takes exactly 7 arguments (6 given) : :Traceback (most recent call last): : File "/usr/bin/fedup-cli", line 285, in <module> : main(args) : File "/usr/bin/fedup-cli", line 257, in main : prep_boot(kernel, initrd) : File "/usr/lib/python2.7/site-packages/fedup/download.py", line 373, in prep_boot : modify_bootloader(kernel, initrd) : File "/usr/lib/python2.7/site-packages/fedup/download.py", line 356, in modify_bootloader : for e in bootloader.get_entries(): : File "/usr/lib/python2.7/site-packages/fedup/grubby.py", line 69, in get_entries : ents.append(self.get_entry(n)) : File "/usr/lib/python2.7/site-packages/fedup/grubby.py", line 63, in get_entry : return GrubbyEntry(**info) :TypeError: __new__() takes exactly 7 arguments (6 given) : :Local variables in innermost frame: :info: {'index': 3, 'args': '"rootfstype=ext4 rootflags=data=writeback ro quiet rhgb"', 'root': '/dev/sda3', 'title': 'Linux 3.6.y', 'kernel': '/boot/vmlinuz-3.6.2'} :index: 3 :val: '' :k: '' :line: '' :eq: '' :self: <fedup.grubby.Grubby object at 0x7f8b18b87190> :out: 'index=3\nkernel=/boot/vmlinuz-3.6.2\nargs="rootfstype=ext4 rootflags=data=writeback ro quiet rhgb"\nroot=/dev/sda3\ntitle=Linux 3.6.y\n'
Created attachment 655346 [details] File: executable
Created attachment 655347 [details] File: environ
Created attachment 655348 [details] File: core_backtrace
Created attachment 655349 [details] File: smolt_data
Okay, I could circumvent this problem by commenting out my custom boot entries in grub, which boot my self-compiled kernel. This entries are missing the initrd line, because I boot directly into systemd.
*** This bug has been marked as a duplicate of bug 881338 ***