[Lucid Xubuntu] lshw corrupt lastmountpoint

[CSkau]

Binary package hint: lshw

I'm experiencing some weird behavior in lshw on my newly installed Xubuntu Lucid.
I noticed the other day that specificly the lastmountpoint value of my disk volumes are corrupted:

              *-volume:1
                   description: EXT4 volume
                   vendor: Linux
                   physical id: 2
                   bus info: scsi@0:0.0.0,2
                   logical name: /dev/sda2
                   logical name: /
                   version: 1.0
                   serial: 61537e63-b69b-4628-b222-6cd38facc856
                   size: 74GiB
                   capacity: 74GiB
                   capabilities: primary journaled extended_attributes large_files huge_files dir_nlink recover extents ext4 ext2 initialized
                   configuration: created=2010-01-24 20:48:59 filesystem=ext4 lastmountpoint=/���jߜ�8E���\���ݲ��[�a��a��ߜ��ݲ��ݲ�5^�ߜ�0�%�� modified=2010-01-24 20:49:43 mount.fstype=ext4 mount.options=rw,relatime,errors=remount-ro,barrier=1,data=ordered mounted=2010-01-25 08:55:42 state=mounted

Further more - in a possibly unrelated bug - I experience running the command caused the screen to go funny. When printing out the list of entries the screen would suddenly change colors to look very strange. However simply switching to another tty and back would solve the problem, and the screen image was back to normal.
I've recently installed a possibly bugged device driver which might have been the cause of this, since after removing it yesterday I can't replicate this step this morning.
But I'll keep this info here just in case..

[Charlie Kravetz (cjkgeek)]

Thank you for reporting this bug. I can confirm this corruption. It happens on the root partition when formatted using ext4. It does not happen on other partitions, and does not happen to those partitions formatted using ext3.

I am not sure lshw is the correct package, but I am unsure what will be correct.

[Jason J. Herne (hernejj)]

I can confirm this corruption, but I cannot reproduce the terminal changing colors.
I can also confirm that it is possible to get lastmountpoint corruption with more than just the root partition.

Also, the following bug appears to be a duplicate of this one:
https://bugs.launchpad.net/ubuntu/lucid/+source/lshw/+bug/527369

It specifically mentions the terminal changing colors. My theory is that the corrupt characters are being interpreted as control characters in some cases thereby changing the terminal parameters.
Just in case I am wrong and they are separate issues I am not going to mark 527369 as a duplicate just yet.

[Jason J. Herne (hernejj)]

This seems to have an upstream bug report. It seems to have been fixed upstream in the current development release. I downloaded the code and confirmed the the problem was indeed fixed.

Lucid currently has lshw B.02.14.
This fix will go into lshw B.02.15 which has not yet been released.
According to their schedule (http://ezix.org/project/milestone/lshw%20B.02.15) B.02.15 was supposed to be done at the beginning on March but it is only 56% done. So it is doubtful that this fix will make it into Lucid unless we backport the fix OR we grab the current development version.

[Jason J. Herne (hernejj)]

According to comment 25 in bug 527369... the latest development version of lshw does NOT fix the color problem that 527369 reports. This certainly leads me to believe that they are separate issues.

It does however appear to fix the corrupt lastmountpoint issue.

[Mike (mike-redhat-bugs)]

Description of problem:
Lshw reports trailing garbage on ext4 lastmountpoint attribute.

Version-Release number of selected component (if applicable):
lshw-B.02.14

How reproducible:
100% of the time with ext4 file systems.

Steps to Reproduce:
1. lshw | grep lastmountpoint
2.
3.

Actual results:
[root@edge ~]# tune2fs -l LABEL=F12-/ | grep 'Last mounted on'
Last mounted on: /
[root@edge ~]# tune2fs -l LABEL=F12-/boot | grep 'Last mounted on'
Last mounted on: /boot
[root@edge ~]# lshw | grep lastmountpoint
                   configuration: created=2010-01-03 13:20:45 filesystem=ext4 label=F12-/boot lastmountpoint=/boot�~���������`�����C�M�ܡ���`�@���_��@����������������� modified=2010-07-13 19:07:44 mount.fstype=ext4 mount.options=rw,seclabel,relatime,barrier=1,data=ordered mounted=2010-07-13 19:07:44 state=mounted
                   configuration: created=2010-01-03 13:20:47 filesystem=ext4 label=F12-/ lastmountpoint=/�S������H%L�����C�M�pJ�H%L�p�D����p�D�����̞����M��� modified=2010-07-05 17:29:03 mount.fstype=ext4 mount.options=rw,seclabel,relatime,barrier=1,data=ordered mounted=2010-07-13 19:07:43 state=mounted

Expected results:
No trailing garbage characters at the end of the lastmountpoint attribute.

Additional info:
This bug is known and fixed up stream, but not yet included in a release.
* bug - http://ezix.org/project/ticket/498
* fix - http://ezix.org/project/changeset/2144

Attaching patch (exactly upstream changeset 2144). Tested patch with released lshw-B.02.14 successfully. Generated patch with:
svn diff http://ezix.org/source/packages/lshw/development@2143 http://ezix.org/source/packages/lshw/development@2144 > lshw-B.02.14-lastmountpoint.patch

[Mike (mike-redhat-bugs)]

Created attachment 431602
Upstream fix, changeset 2144

[Terje (terje-redhat-bugs)]

Thanks for the report, will push a updated package soon.

[Fedora (fedora-redhat-bugs)]

lshw-B.02.14-5.fc13 has been submitted as an update for Fedora 13.
https://admin.fedoraproject.org/updates/lshw-B.02.14-5.fc13

[Fedora (fedora-redhat-bugs)]

lshw-B.02.14-5.fc12 has been submitted as an update for Fedora 12.
https://admin.fedoraproject.org/updates/lshw-B.02.14-5.fc12

[Fedora (fedora-redhat-bugs)]

lshw-B.02.14-5.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/lshw-B.02.14-5.fc14

[Fedora (fedora-redhat-bugs)]

lshw-B.02.14-5.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with
 su -c 'yum --enablerepo=updates-testing update lshw'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/lshw-B.02.14-5.fc14

[David Rahrer (david-rahrer)]

I'm getting the corrupt mountpoint line on Lucid 10.04.1, but no terminal color issues. I seem to have a vague memory of dealing with this before and it having been marked as a bug, etc. Is the fix supposed to have already been sent out in updates or are we still waiting for that? Thanks.

[David Rahrer (david-rahrer)]

If lshw version 2.15 is what we are waiting on, it looks like it might be a while: http://ezix.org/project/ticket/498

[Fedora (fedora-redhat-bugs)]

lshw-B.02.14-5.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.

[Fedora (fedora-redhat-bugs)]

lshw-B.02.14-5.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.

[Fedora (fedora-redhat-bugs)]

lshw-B.02.14-5.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.

[Jason J. Herne (hernejj)]

I'm adding a patch that fixes this issue. This is merely a backport of the code that fixes this bug upstream.
http://ezix.org/project/changeset/2144

I created the patch using lshw 02.14-1build1 as found in the Maverick repository. I've tested it and it fixes the problem.

lshw version B.02.15 is released but since it is not in Maverick it looks like a backport is the only way we're to be free of this bug before the next Ubunutu release.

[Savvas Radevic (medigeek)]

Can we get a backport please? It causes problems with python parsing of "sudo lshw -xml":

Traceback (most recent call last):
  File "test.py", line 203, in <module>
    main()
  File "test.py", line 200, in main
    core()
  File "test.py", line 78, in __init__
    self.lshw()
  File "test.py", line 153, in lshw
    doc = xml.dom.minidom.parseString(self.lshwxml)
  File "/usr/lib/python2.6/xml/dom/minidom.py", line 1928, in parseString
    return expatbuilder.parseString(string)
  File "/usr/lib/python2.6/xml/dom/expatbuilder.py", line 940, in parseString
    return builder.parseString(string)
  File "/usr/lib/python2.6/xml/dom/expatbuilder.py", line 223, in parseString
    parser.Parse(string, True)
xml.parsers.expat.ExpatError: not well-formed (invalid token): line 943, column 61

Line #943 matches a lastmountpoint line

[Rui Lapa (rui-lapa)]

This issue is still open and 02.15 is out.

Can we get LTS package rebuilt (Y/N)?

[Bryce Harrington (bryce)]

Natty includes version 02.15-1 which as per recent comments contains this fix.

Opening tasks for the backports for lucid and maverick.