[Bug 512251] Re: [Lucid Xubuntu] lshw corrupt lastmountpoint

[dann frazier]

** Changed in: lshw (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to lshw in Ubuntu.
https://bugs.launchpad.net/bugs/512251

Title:
  [Lucid Xubuntu] lshw corrupt lastmountpoint

Status in lshw:
  Fix Released
Status in lshw package in Ubuntu:
  Fix Released
Status in lshw source package in Natty:
  Fix Released
Status in lshw package in Fedora:
  Unknown

Bug description:
  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 at 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..

To manage notifications about this bug go to:
https://bugs.launchpad.net/lshw/+bug/512251/+subscriptions